April 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: uniquify and custom 24 years, 7 months

Jan Vroonhof

"John A. Turner" <turner(a)blueskystudios.com> writes: > so should I send mail to the guy listed as author or does someone just make > the change in the XEmacs package containing it or what? It would be nice if you would make it "official", i.e. add ChangeLog. Normally. you would send it to both xemacs-patches and the original maintainer. However a quick glance shows that the FSF version of uniquify.el already has the require. Maybe you should sync against the version in FSF 20.5 (and/or ask the maintainer whether he has an even newer version and whether he would be willing to send his changes to xemacs-patches in the future?). Jan

1 participants
0 comments

Re: Enable clash detection (was Re: ) 24 years, 7 months

Jan Vroonhof

Yoshiki Hayashi <yoshiki(a)xemacs.org> writes: > +test "$with_clash_detection" != "no" && \ > echo " Clash detection will use \"$lockdir\" for locking files." Clash detection doesn't use lockdir anymore, so we probably should get rid of this. Jan

1 participants
0 comments

Milestone 1 submission... 24 years, 7 months

William M. Perry

Here is the official submission of milestone one. All documents will also be available at http://www.cs.indiana.edu/elisp/gui-xemacs/ If anyone has feedback on style / structure / etc (especially my impressions of either toolkit) please let me or the list know. It looks like the front-runner right now is Gtk / Gnome. Next document will detail the implementation plans and what the language bindings will actually look like. I am wrestling with how the bindings should actually look right now. I personally prefer a very lispy interface using 'put' and 'get' generically, and something similar to libglade so that the GUI can be changed very easily. The first code milestone will be May 20th. I will be on vacation from my 'real' job from now until then. The main work will be in getting the XEmacs event loop and redisplay to cooperate with Gtk. The language binding should be fairly simple. -Bill P.

3 participants
2 comments

Re: efs and custom 24 years, 7 months

Michael Sperber

>>>>> "Ben" == Ben Wing <ben(a)666.com> writes: Ben> michael, doesn't this mean you need a :require efs in your defgroup? Ben> john really is right that you shouldn't have to manually load. I guess so. I'm a customize dummy, and I put in customize support pretty much blind, so I'm grateful for the input. I'll put this in the EFS release and try to zip it up this weekend. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: 24 years, 7 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > > It would be really nice to have clash detection back. I remember > > somebody (you?) mentioning an algorithm how clash detection could be > > implemented to work reliably. > > Whatever happened to that project? > > Its in 21.2 since January 1999 or so (I implemented it in September > 1998, just after the feature freeze). Oops. Let's enable it by default, then. Why is it disabled at all? It's a very useful feature IMHO.

2 participants
1 comments

Re: [FAIL] latest CVS 24 years, 7 months

Michael Harnois

Same error here as Norbert reports. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois(a)home.com aa0bt(a)aa0bt.ampr.org A dying people tolerates the present, rejects the future, and finds its satisfactions in past greatness and half remembered glory. -- John Steinbeck

4 participants
3 comments

Re: efs and custom 24 years, 7 months

Michael Sperber

>>>>> "John" == John A Turner <turner(a)blueskystudios.com> writes: John> are these msgs about customize appropriate for xemacs-beta or should I be John> posting them to comp.emacs.xemacs? it seems I may have stumbled upon some John> things that qualify as bugs, but I'm never sure if it's that or just mere John> user ignorance John> this one in particular may very well be in the latter category... John> how does one customize efs? I see this in efs.el: John> (defgroup efs nil John> "Transparent ftp access." John> :group 'files) John> but it doesn't appear under the Files menu or when doing M-x customize John> files John> ? Have you actually *loaded* the thing? -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

3 participants
3 comments

something is wrong with latest beta 24 years, 7 months

Jeff Miller

did a cvs a hour or so ago.... now when i start vm, my buffer is truncated. I won't guarantee it but i think it is truncatating at the first message to send it into the "buffer to large to font lock" situation. the last msg i see is dated march 10 or so.... when i know for a fact there are messages there which have arrived today. i tried compiling with out widgets bug still get the same error...... i think it's been roughtly a week or so since i updated at tried running with changes...... if that helps. i realize this is a crappy erro message but i have been up way too long.......... jeff

1 participants
1 comments

Re: uniquify and custom 24 years, 7 months

Jan Vroonhof

"John A. Turner" <turner(a)blueskystudios.com> writes: > I'm not sure what the main enabling variable is - I tried adding :require > to the defcustom for uniquify-buffer-name-style, but that didn't do it - > I may not have done it correctly, though, since obviously I don't > understand custom very well... You need something like this diff -u /scratch/vroonhof/xemacs/debug/xemacs-packages/lisp/edit-utils/uniquify.el~ /scratch/vroonhof/xemacs/debug/xemacs-packages/lisp/edit-utils/uniquify.el --- /scratch/vroonhof/xemacs/debug/xemacs-packages/lisp/edit-utils/uniquify.el~ Wed Apr 12 17:11:34 2000 +++ /scratch/vroonhof/xemacs/debug/xemacs-packages/lisp/edit-utils/uniquify.el Wed Apr 12 17:11:34 2000 ＠＠ -111,7 +111,8 ＠＠ (const post-forward) (const post-forward-angle-brackets) (const :tag "standard Emacs behavior (nil)" nil)) - :group 'uniquify) + :group 'uniquify + :require 'uniquify) (defcustom uniquify-after-kill-buffer-p nil "*If non-nil, rerationalize buffer names after a buffer has been killed. Then bytecompile, Quit XEmacs and customize the variable again.. Save changes, Quit XEmacs and it should work. The custom-set-variable line should now have an extra argument require on it. Jan

2 participants
1 comments

Re: [FAIL] latest CVS 24 years, 7 months

Michael Harnois

Lovely, thanks so much ... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois(a)home.com aa0bt(a)aa0bt.ampr.org There are three steps in the revelation of any truth: in the first, it is ridiculed; in the second, resisted; in the third, it is considered self-evident. -- Arthur Schopenhauer

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta April 2000