January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [XEmacs-21.0-bug:] Current forms.el relies on concat with numeric argument 25 years, 10 months

Holger Schauer

>>>>"JV" == Johan Vromans schrieb am Mon, 11 Jan 1999 20:51:44 +0100 (MET): JV> [Quoting Holger Schauer, on January 11 1999, 18:36, in JV> "[XEmacs-21.0-bug:] C"] >> (error (concat "Forms format error: " "field number %d out of >> range 1..%d") el forms-number-of-fields)) >> >> forms.el is cluttered with such calls, also in forms--show-record. JV> As pointed out already, the above call is perfectly okay. As far JV> as I can see, there is only one place where numerics are passed JV> to concat, the last statement in forms--show-record (line 1548 in JV> my version): JV> This line would require a (trivial) modification. Did you spot JV> other places? I just scanned again through forms.el. You are correct, the last statement in forms--show-record is the only one needing a modification. Sorry for my strong wording ("cluttered") and choosing an obviously wrong example (man, I must have been really tired). I will write down a hundred times: "I won't send bug reports before having them re-examined the next morning." Holger -- --- http://www.coling.uni-freiburg.de/~schauer/ --- " Well you reach the point where you know It's only your second skin" -- Chameleons, "Second skin"

1 participants
0 comments

Re: rssh.el interactions with ange-ftp/efs 25 years, 10 months

David Maslen

kifer(a)cs.sunysb.edu (Michael Kifer) writes: > >>>>> "WMP" == William M Perry <of 11 Jan 1999 13:55:35 EST> writes: > > WMP> Why not just start using URLs? Once upon a time I had the stuff for > WMP> Emacs/W3 to do this for files like http://blah/blah/blah > > WMP> Ange-ftp/efs could grab ftp:// stuff, xsh://user:password＠hostname/ would > WMP> work, yadda yadda yadda. > > I agree. ange-ftp/efs should stop using the old syntax (except possibly for > backward compatibility) and switch to URLs. Using URL's sounds like a good idea, but it involves more keystrokes, and that's a bad thing, when you're already used to a shorter version. /david(a)zen/home/david/file.txt file://david＠zen/home/david/file.txt On second thoughts. What am I complain about, especially if by default xemacs would write file://localhost/ on the line for c-x c-f. -- Binary Bar - Australia's first free access internet bar/cafe/gallery. 243 Brunswick Street, Fitzroy, Melbourne, Australia. 3pm - 1am http://www.binary.net.au/ Running on Debian/GNU Linux

2 participants
1 comments

21.2-b8: advice + vhdl-mode + font-lock-mode 25 years, 10 months

Steve Haslam

Hello XEmacs people... I'm having trouble getting font-lock-mode and vhdl-mode to work together, and have discovered that this "works" fine: bash$ xemacs-21.2-b8 -vanilla -batch \ -eval "(progn (vhdl-mode) (font-lock-mode))" and this fails: bash$ xemacs-21.2-b8 -vanilla -batch \ -eval "(progn (require 'advice) (vhdl-mode) (font-lock-mode))" Symbol's value as variable is void: font-lock-use-default-minimal-decoration xemacs exiting. Apart from that, it seems fine for me except that the native Linux sound code corrupting sound... which I'm going to look into when I have time. uname -a: Linux arise 2.2.0-pre6 #1 Sat Jan 9 21:56:10 GMT 1999 i586 unknown ./configure '--prefix=/usr' '--gung-ho' '--with-sound=both' '--statedir=/var/lib' '--with-clash-detection' '--lockdir=/var/lib/emacs/lock' '--infopath=/usr/info' '--datadir=\${prefix}/share' '--package-path=/usr/share/xemacs21/packages' '--with-site-lisp' '--without-mule' XEmacs 21.2-b8 "Artemis" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs21/xemacs-21.2.8 What installation prefix should install use? /usr What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in both network and native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. Clash detection will use "/var/lib/emacs/lock" for locking files. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- SRH -- almost called it today, turned to face the void along with the suffering and the question- "Why am I?" [queensrÿche]

1 participants
0 comments

21.2-b8: patch for new module code 25 years, 10 months

Damon Lipparelli

I had to apply the following patch to get things compiling under Solaris 2.5.1 and EGCS 1.1.1: 1999-01-11 Damon Lipparelli <lipp(a)primus.com> * Makefile.in.in: use ellcc (not ellc) everywhere --- Makefile.in.in 1999/01/12 01:37:59 1.36.2.4 +++ Makefile.in.in 1999/01/12 08:37:59 ＠＠ -76,9 +76,9 ＠＠ INSTALLABLE_SCRIPTS = rcs-checkin pstogif gnudoit gnuattach #ifdef HAVE_SHLIB #ifdef HAVE_MS_WINDOWS -INSTALLABLES = $(INSTALLABLES_BASE) runxemacs rungnuclient ellc +INSTALLABLES = $(INSTALLABLES_BASE) runxemacs rungnuclient ellcc #else -INSTALLABLES = $(INSTALLABLES_BASE) ellc +INSTALLABLES = $(INSTALLABLES_BASE) ellcc #endif #else #ifdef HAVE_MS_WINDOWS ＠＠ -240,7 +240,7 ＠＠ clean: mostlyclean $(RM) ${INSTALLABLES} ${UTILITIES} *.exe distclean: clean - $(RM) DOC *.tab.c *.tab.h aixcc.c TAGS ellc.h + $(RM) DOC *.tab.c *.tab.h aixcc.c TAGS ellcc.h $(RM) GNUmakefile Makefile Makefile.in blessmail config.values realclean: distclean extraclean: distclean

1 participants
0 comments

Re: set-text-properties question 25 years, 10 months

Hrvoje Niksic

Colin Rafferty <craffert(a)ms.com> writes: > That's a very good idea. However, I'm getting the string in one > place, and handling it in a different place. All that `b-s-n-p' > does is call the blasphemous `set-text-properties', so I don't feel > that bad. :-) Actually, `buffer-substring-no-properties' is a built-in function in the latest XEmacs.

1 participants
0 comments

[XEmacs-21.0-bug:] Current forms.el relies on concat with numeric argument 25 years, 10 months

Holger Schauer

In XEmacs 21.0 "Poitou" [Lucid] (sparc-sun-solaris2.6) of Wed Sep 30 1998 on streetlife.coling.uni-freiburg.de Please describe exactly what actions triggered the bug and the precise symptoms of the bug: The current forms relies on the use of concat with numeric arguments. Could somebody with access to the CVS repository create a patch and apply it? Here is one of the relevant points: (error (concat "Forms format error: " "field number %d out of range 1..%d") el forms-number-of-fields)) forms.el is cluttered with such calls, also in forms--show-record. This should be fixed: ---- `concat' is a built-in function Documentation: Concatenate all the arguments and make the result a string. The result is a string whose elements are the elements of all the arguments. Each argument may be a string or a list or vector of characters. As of XEmacs 21.0, this function does NOT accept individual integers as arguments. Old code that relies on, for example, (concat "foo" 50) returning "foo50" will fail. To fix such code, either apply `int-to-string' to the integer argument, or use `format'. ---- If nobody else volunteers for this, I could create a patch and submit it to xemacs-patches. This would take some time (I'm pretty busy currently), about a week, I guess. Holger -- --- http://www.coling.uni-freiburg.de/~schauer/ --- " Well you reach the point where you know It's only your second skin" -- Chameleons, "Second skin"

3 participants
2 comments

Re: rssh.el interactions with ange-ftp/efs 25 years, 10 months

Alan Shutko

>>>>> "J" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: J> :-( Then we need some other convention. However I still think my J> original idea has merit. What about J> /:user＠host＠method:path J> for a specific method? My point was that /:anything is treated as quoting the rest of the pathname against any further processing, and that something other than /: should be used for this purpose. -- Alan Shutko <ats(a)acm.org> - By consent of the corrupted ** MAXIMUM TERMINALS ACTIVE. TRY AGAIN LATER **

2 participants
1 comments

Re: rssh.el interactions with ange-ftp/efs 25 years, 10 months

Jan Vroonhof

Alan Shutko <ats(a)acm.org> writes: > J> /::xsh:user＠host:path > > This is a bad idea. As of Emacs 20.1: > > ** You can "quote" a file name to inhibit special significance of > special syntax, by adding `/:' to the beginning. Thus, if you have a > directory named `/foo:', you can prevent it from being treated as a > reference to a remote host named `foo' by writing it as `/:/foo:'. :-( Then we need some other convention. However I still think my original idea has merit. What about /:user＠host＠method:path for a specific method? and then /:user＠host:path is handled by the general code to figure out the appropriate method. /:＠host＠method:path is handled by the method the find the appropriate default for user. /:host:path is is handled by the general code to figure out the appropriate method and then by the method the find the appropriate default for user. This is just slightly less compatible. Or is the extra ＠ in use too? Jan

1 participants
0 comments

gnus-tut.txt not being installed 25 years, 10 months

Charles G Waldman

The Gnus command "G h" fails because the datafile gnus-tut.txt is not getting installed. ChangeLog for comm/gnus 1999-01-11 Charles G Waldman <cgw(a)pgt.com> *Makefile: install gnus-tut.txt Index: Makefile =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-packages/comm/gnus/Makefile,v retrieving revision 1.38 diff -u -r1.38 Makefile --- Makefile 1998/12/10 13:15:12 1.38 +++ Makefile 1999/01/12 01:20:13 ＠＠ -73,6 +73,8 ＠＠ DATA_3_DEST = $(PACKAGE) DATA_4_FILES = $(wildcard etc/gnusrefcard/[MRbgmqr]*) DATA_4_DEST = gnusrefcard +DATA_5_FILES = gnus/etc/gnus-tut.txt +DATA_5_DEST = . INFO_FILES = gnus/texi/message.info* gnus/texi/gnus.info* TEXI_FILES = gnus/texi/message.texi gnus/texi/gnus.texi gnus/texi/gnus-faq.texi

1 participants
0 comments

Re: rssh.el interactions with ange-ftp/efs 25 years, 10 months

Alan Shutko

>>>>> "J" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: J> So after inspecting the regexps used I suggest you use something J> like J> /::xsh:user＠host:path This is a bad idea. As of Emacs 20.1: ** You can "quote" a file name to inhibit special significance of special syntax, by adding `/:' to the beginning. Thus, if you have a directory named `/foo:', you can prevent it from being treated as a reference to a remote host named `foo' by writing it as `/:/foo:'. -- Alan Shutko <ats(a)acm.org> - By consent of the corrupted A fool must now and then be right by chance.

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