April 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: todo-mode , xemacs, palm-pilot 26 years, 1 month

John Mignault

>>>>> "Ian" == Ian MacKinnon <IMacKinnon(a)TELIA.CO.UK> writes: Ian> I beleive that there is a lisp package for the Pilot, there Ian> was also the rumour of a Linux kernel :) There is a lisp interpreter for the Pilot, called LispMe: http://www.geocities.com/SiliconValley/Lab/9981/ j -- #!/usr/bin/perl $dot="\x2e";$lt="\x3c";$gt="\x3e";$at="\x40"; print "J Mignault ${lt}jbm${at}panix${dot}com${gt}\n"; $wright = qq(I played a blank tape on full volume. The mime who lives next door complained.);

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?2 and 0) 26 years, 1 month

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > Practically, I think use of preceding-char in this way is bad > practice in code that tries to be portable between XEmacs and the > FSF's version, since 0 is an ASCII character in the FSF's version. Yes, but most of the offending code originates from FSF in the first place. While their typical usage happens to result in correct behaviour in XEmacs 20, I agree that following/preceding-char are bad style in both Emacsen. > I only ask that consideration be given to maintaining the code in > case someone wants the facility, as I do. I propose simply defaulting `debug_issue_ebola_notices' to 0. Then you can put `(setq debug-issue-ebola-notices t)' to your .emacs and be a happy man. Leaving the code in by default is OK with me -- debug builds are not destined to be lightning-fast anyway, and most debugging features are changeable at run-time. > I have no idea what that would cost in maintenance though. I think the maintenance cost should be minimal if we remove the "abracadabra" hacks which were introduced in order to make the use of XEmacs with these warnings more palatable. We might also want to remove some uses of EQ_WITH_EBOLA_NOTICE, such as in the _no_quit functions.

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?2 and 0) 26 years, 1 month

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > This is not true for me. Of the two Ebola warnings I remember > seeing in the last 6 months, the one in AUC-TeX is due to use of > `previous-char' instead of `char-before' (a distant cousin of > Ebola), You mean `char-before', right? BTW, are you aware that this one is totally bogus? Code that compares (eq (char-before) 0) will work just fine for any character *because* of character/integer distinction. As Kyle put it, ebola warnings were a part of the "transition phase", to ensure that hundreds of such bugs get fixed in time. The warnings no longer serve a useful purpose to the vast majority of developers, and they should be off by default now, even in debugging builds.

2 participants
1 comments

Re: Properties and readonly objects 26 years, 1 month

Michael Sperber

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> BTW, why do we want Lisp-level readonly objects in the first place? The most obvious is that, with the right dumper and OS support, you can put them in shareable/read-only/EPROM memory. Another is that you can optimize GC with this kind of knowledge. It seems that, since reachability is affected by mutable plists, you want the plists of immutable objects to be immutable as well. Hrvoje> Do other Lisp flavors (such as CL) have them? Scheme has. I've written a portable dumper for Scheme 48 which exploits this, as well, with noticeable gains in efficiency. I'm pretty sure CL has, too. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?2 and 0) 26 years, 1 month

Hrvoje Niksic

Hrvoje Niksic <hniksic(a)srce.hr> writes: > "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > > > This is not true for me. Of the two Ebola warnings I remember > > seeing in the last 6 months, the one in AUC-TeX is due to use of > > `previous-char' instead of `char-before' (a distant cousin of > > Ebola), > > You mean `char-before', right? ^^^^^^^^^^^ <--- this was supposed to say `preceding-char' > Code that compares (eq (char-before) 0) will work just preceding-char

1 participants
0 comments

Re: Patches to split the Options/Font menu based on the first char 26 years, 1 month

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Didier Verna <verna(a)inf.enst.fr> writes: > > > Just to add another argument to what Glynn said, Motif for instance, > > is a toolkit that we support and that is shipped with some machines > > No we don't. Motif scrollbars and menubars have been broken for ages. All right. We don't support it, we have some support for it. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: Patches to split the Options/Font menu based on the first char 26 years, 1 month

Hrvoje Niksic

Didier Verna <verna(a)inf.enst.fr> writes: > Just to add another argument to what Glynn said, Motif for instance, > is a toolkit that we support and that is shipped with some machines No we don't. Motif scrollbars and menubars have been broken for ages. (This is not an argument for ditching Xt, simply a correction of misstatment.)

1 participants
0 comments

Majordomo Slurpage 26 years, 1 month

Jason R Mastaler

I believe this problem is now fixed. As usual, please report any mailing list problems to <list-manager(a)xemacs.org>. Thanks. Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Colin Rafferty writes: > > Tor Arntsen writes: > > > On Apr 6, 20:07, Colin Rafferty wrote: > > > > >> User-Agent: Gnus/5.07008 (Pterodactyl Gnus v0.80) XEmacs/21.0(beta67) (20 minutes to Nikko) > > >> Sender: owner-xemacs-beta(a)xemacs.org > > >> X-Mailing-List: <xemacs-beta(a)xemacs.org> > > >> Hello Didier, this should be in the header. > > > > > It did end up in the heaader.. it should have been a blank line in between > > > there, right? > > > > You bet! The problem is certainly on xemacs.org's side. > > Known crockage. If the first line in the body of a message > begins with whitespace, majordomo slurps that lines and some > number of others into the headers. Sucks. Since we're > freeloaders at xemacs.org, I can only suggest that you not > start your messages with whitespace. >

1 participants
0 comments

Re: Crash in XEmacs 21.0 "20 minutes to Nikko" with gnuserv/gnuclient 26 years, 1 month

Colin Rafferty

Jan Vroonhof writes: > Colin Rafferty <craffert(a)ms.com> writes: >> (defun delete-frame-or-save-buffers-kill-emacs (&optional frame) >> "If there is only one frame, `save-buffers-kill-emacs', else `delete-frame'." >> (interactive) >> (delete-frame frame t)) >> >> (global-set-key [(control x) (5) (0)] 'delete-frame-or-save-buffers-kill-emacs) > (setq allow-deletion-of-last-visible-frame t) Okay, so I should have been more careful with checking conditions. I could have checked `(length (frame-list))', but I figured that obscurity wouldn't setq that. Maybe I just felt like using an obscure capability. -- Colin

1 participants
0 comments

Re: Crash in XEmacs 21.0 "20 minutes to Nikko" with gnuserv/gnuclient 26 years, 1 month

Jan Vroonhof

Colin Rafferty <craffert(a)ms.com> writes: > (defun delete-frame-or-save-buffers-kill-emacs (&optional frame) > "If there is only one frame, `save-buffers-kill-emacs', else `delete-frame'." > (interactive) > (delete-frame frame t)) > > (global-set-key [(control x) (5) (0)] 'delete-frame-or-save-buffers-kill-emacs) (setq allow-deletion-of-last-visible-frame t) Jan

1 participants
0 comments

2025

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 1999