July 1999 - XEmacs-Beta - XEmacs Mailing List Archives

[PATCH] protect symbols when writing 24 years, 9 months

Didier Verna

OK, same places as before, plus another one. Must use prin1 instead of princ when outputting symbols, in order to protect special characters. I'm not going to apply it myself, since I'm off for one week in a few minutes. Please, another reviewer, do it if it's ok. 1999-07-30 Didier Verna <verna(a)inf.enst.fr> * cus-edit.el (custom-save-variables): I said, use prin1 instead of princ to output symbols. (custom-save-face-internal): ditto. (custom-save-resets): ditto. Index: lisp/cus-edit.el =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/cus-edit.el,v retrieving revision 1.8.2.6 diff -u -u -r1.8.2.6 cus-edit.el --- cus-edit.el 1999/07/23 20:30:42 1.8.2.6 +++ cus-edit.el 1999/07/30 13:43:33 ＠＠ -3280,7 +3280,7 ＠＠ (when (or (and spec (eq (car spec) 'user) (eq (second spec) 'set)) comment) (princ "\n '(") - (princ symbol) + (prin1 symbol) (princ " ") ;; This comment stuf is in the way #### ;; Is (eq (third spec) (car saved-value)) ???? ＠＠ -3313,7 +3313,7 ＠＠ (eq (car theme-spec) 'user) (eq (second theme-spec) 'set)) comment) (princ "\n '(") - (princ symbol) + (prin1 symbol) (princ " ") (prin1 (get symbol 'saved-face)) (if (or comment now) ＠＠ -3358,7 +3358,7 ＠＠ (princ "(") (princ (quote ,setter)) (princ "\n '(") - (princ object) + (prin1 object) (princ " ") (prin1 (third spec)) (princ ")"))))))) -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Re: (b19) I can't use custom anymore (because of themes) 24 years, 9 months

Didier Verna

I <verna(a)inf.enst.fr> write: > I keep getting "invalid read syntax: #" error messages when trying to > save options.el. The origin seems to be in the use of # in functions like > custom-load-themes. I don't know what this syntax means. I'm wrong. It's a bug that I fixed some time ago, but seems to have reappeared with the themes stuff: custom doesn't protect symbols with special characters in them when writing the custom file. It's a matter of using print1-to-string instead of print1 somewhere. I haven't found out where yet. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

makeinfo fails on 21.2b19 24 years, 9 months

Neal D. Becker

./internals.texi:130: Menu reference to nonexistent node `Faces and Glyphs'. ./internals.texi:7878: warning: unreferenced node `Widget-Glyphs in the MS-WIndows Environment'. ./internals.texi:7883: warning: unreferenced node `Widget-Glyphs in the X Environment'. makeinfo: Removing output file `../../info/internals.info' due to errors; use --force to preserve. make[2]: *** [../../info/internals.info] Error 2

1 participants
0 comments

Stuff Your Mailbox With $600 Checks... 24 years, 9 months

secure＠deal.zzn.com

Inc. 500 environmental company has grown 5,000% in last 24 months! We need NEW dealers, company will train at home. Automatic marketing system in place, no selling. Earn $12,000 in just 120 days! Contact Dr. Steve Roti at 1-888-889-0908

1 participants
0 comments

(b19) I can't use custom anymore (because of themes) 24 years, 9 months

Didier Verna

I keep getting "invalid read syntax: #" error messages when trying to save options.el. The origin seems to be in the use of # in functions like custom-load-themes. I don't know what this syntax means. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Re: backward-word: WTF? 24 years, 9 months

Hrvoje Niksic

Didier Verna <verna(a)inf.enst.fr> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > But I would appreciate it if you threw them in a separate thread, > > not to confuse them with bug reports. > > ?! C'mon, I think you made yourself perfectly clear. And if you want > to avoid confusing people, start sticking `[BUG]' at the beginning > of your Subject line instead of `WTF' at the end. And the same to YOU, mac! Okay, just kidding. The [bug] thing is actually a good suggestion. I used to do that before, when functions other than `backward-word' got buggy.

1 participants
0 comments

Re: backward-word: WTF? 24 years, 9 months

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > But I would appreciate it if you threw them in a separate thread, not > to confuse them with bug reports. ?! C'mon, I think you made yourself perfectly clear. And if you want to avoid confusing people, start sticking `[BUG]' at the beginning of your Subject line instead of `WTF' at the end. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Re: backward-word: WTF? 24 years, 9 months

Hrvoje Niksic

Didier Verna <verna(a)inf.enst.fr> writes: > > > Wouldn't it be more logical to put it after the space ? > > > > No? :-) What XEmacs does currently is often confusing to beginners, > > but I find that it works very well once you get used to it. > > "Once you get used to it" as you say... Is this an argument? That's > exactly because we're all "used to XEmacs" that I'm throwing out > this kind of questions from time to time. :-) But I would appreciate it if you threw them in a separate thread, not to confuse them with bug reports.

1 participants
0 comments

Re: backward-word: WTF? 24 years, 9 months

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > > In a similar vein, when you're at the beginning of the line and type > > M-f the point is put after the "a". > > Er... That's the way Emacs has behaved since forever. :-) I know :-) > > Wouldn't it be more logical to put it after the space ? > > No? :-) What XEmacs does currently is often confusing to beginners, > but I find that it works very well once you get used to it. "Once you get used to it" as you say... Is this an argument? That's exactly because we're all "used to XEmacs" that I'm throwing out this kind of questions from time to time. :-) -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Re: backward-word: WTF? 24 years, 9 months

Hrvoje Niksic

Didier Verna <verna(a)inf.enst.fr> writes: > In a similar vein, when you're at the beginning of the line and type > M-f the point is put after the "a". Er... That's the way Emacs has behaved since forever. :-) > Wouldn't it be more logical to put it after the space ? No? :-) What XEmacs does currently is often confusing to beginners, but I find that it works very well once you get used to it. What I reported was, however, a *bug*, plain and simple. And a very dangerous one because a lot of parsing code in language modes, Gnus, the internals, simply everywhere, expects scan_words() to work unchanged.

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 July 1999