February 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: rssh.el interactions with ange-ftp/efs 26 years, 1 month

Jan Vroonhof

Sandy Rutherford <sandy(a)math.ubc.ca> writes: > Fair enough. So all that is required is for rssh.el to put it's own > entry in the file-name-handler-alist. For file names matching its > syntax, rssh.el will run. It is already doing that. However if ange-ftp/efs gets loaded after that EFS complains it is not a valid EFS remote file name. > so a syntax of the form > > /USER＠HOST#ssh:FILE Doesn't that have the same problem? We really need to have either a convention that filenames that do not completely match the syntax are always passed on or we need to move to one singe file handler that dispatches to the right backend. Or even both. > There seem to be a lot of discussions going on, with a lot of cross > CC'ing. I know that it's central to at least one of the discussions. As the one who wrote the origional messages and who picked the subject I can say that this is the matter I wanted to address. Jan

2 participants
1 comments

file-regular-p not implemented in efs 26 years, 1 month

Carsten Leonhardt

>>>>> "Me" == Carsten Leonhardt <leo(a)arioch.oche.de> writes: [Quoted for the people on efs-bugs] Me> Today I was wondering why a function wouldn't work when given a remote Me> directory. The function essentially looks for (regular) files in the Me> directory, which it then moves to another location. After some debugging, I now found out that file-regular-p isn't implemented in efs, although all other in my view (for remote files) sensible file-*-p functions are. Is that on purpose? This is efs-version "1.17/1.57".

2 participants
1 comments

21.2-b9 success 26 years, 1 month

Neal D. Becker

21.2 \"Athena\" XEmacs Lucid (beta9)" Shadows: /usr/local/lib/xemacs/xemacs-packages/lisp/gnus/pop3 hides /usr/local/lib/xemacs/xemacs-packages/lisp/mail-lib/pop3 /usr/local/lib/xemacs/xemacs-packages/lisp/elib/elib-node hides /usr/local/lib/xemacs/xemacs-packages/lisp/pcl-cvs/elib-node /usr/local/lib/xemacs/xemacs-packages/lisp/elib/dll hides /usr/local/lib/xemacs/xemacs-packages/lisp/pcl-cvs/dll /usr/local/lib/xemacs/xemacs-packages/lisp/elib/dll-debug hides /usr/local/lib/xemacs/xemacs-packages/lisp/pcl-cvs/dll-debug /usr/local/lib/xemacs/xemacs-packages/lisp/elib/cookie hides /usr/local/lib/xemacs/xemacs-packages/lisp/pcl-cvs/cookie 5 Emacs Lisp load-path shadowings were found uname -a: Linux nbeckerpc.hns.com 2.2.1 #7 Mon Feb 1 14:00:59 EST 1999 i686 unknown ../../xemacs-21/configure '--gung-ho' XEmacs 21.2-b9 "Athena" configured for `i686-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21 What installation prefix should install use? /usr/local 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 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. 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: ---------------------------------------------------------

1 participants
0 comments

Re: extent-data in BBDB 26 years, 1 month

Colin Rafferty

Gleb Arshinov writes: > extent-data is obsoleted in 21.0 and is not available in 21.2. I'd > get error when trying to pop-up BBDB pop-up menu. How about the > following: You have an old version of BBDB. If you get the latest, you will see that this has already been fixed. -- Colin

2 participants
1 comments

Re: XEmacs 21.0.63 on AIX 4.3.1??? 26 years, 1 month

Michael Sperber

>>>>> "Derek" == Derek Scherger <derek(a)echologic.com> writes: Derek> Ooops, I previously posted this to the xemacs list, perhaps this is a Derek> better place for it! Derek> I've just tried to build and run XEmacs 21.0.63 on an RS/6000 recently Derek> upgraged to AIX 4.3.1 and it seems to be somewhat broken. Did you read the PROBLEMS file? -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: 21.0.63 build fails 26 years, 1 month

Kai Haberzettl

SL Baur <steve(a)xemacs.org> writes: > Kai Haberzettl <khaberz(a)synnet.de> writes in xemacs-beta(a)xemacs.org: > > > I am clueless as to what is happening here... > ... > > xemacs exiting.Opening doc string file: No such file or directory, ../lib-src/DOC > > This generally means something failed earlier in the build probably > when the DOC file was being built. Thank you. After a 'make clean' the build went fine. Kai -- "We had it tough ... I had to get up at 9 o'clock at night, half an hour before I went to bed, eat a lump of dry poison, work 29 hours down mill, and when we came home our Dad would kill us, and dance about on our grave singing Haleleuia ..." -- Monty Python

1 participants
0 comments

Re: 21.0.63 build fails 26 years, 1 month

SL Baur

Kai Haberzettl <khaberz(a)synnet.de> writes in xemacs-beta(a)xemacs.org: > I am clueless as to what is happening here... ... > xemacs exiting.Opening doc string file: No such file or directory, ../lib-src/DOC This generally means something failed earlier in the build probably when the DOC file was being built.

1 participants
0 comments

XEmacs 21.0.63/21.2.9 are released 26 years, 1 month

SL Baur

[XEmacs crashed last night when I tried to post this, one O/S upgrade[1] later I'm ready to give it another shot ...] Get them from the usual places: ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.0/ ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.2/ http://cvs.xemacs.org/ The lisp packages have been rebuilt and new SUMO tarballs are available. ftp://ftp.xemacs.org/pub/xemacs/packages/ to 21.0 "Pyrenean63" -- miscellaneous bug fixes to 21.2 beta9 "Athena" -- parameterize replace-match function from Didier Verna -- X-Face support under mswindows from Andy Piper -- doc fixes from Adrian Aichner -- about patchlet from Marcus Thiessel -- isearch doc fixes from Didier Verna -- interlaced gif fix from Gunnar Evermann -- isearch improvements from Didier Verna -- eldap connection fix from William Perry -- package-get site fix from Robert Pluim -- loadable modules fix from Damon Lipparelli -- ldap fixes from Oscar Figueiredo -- loadable modules from J. Kean Johnston -- runwhatever from Charles Wilson -- redisplay fixes for glyphs from Andy Piper -- progress gauge widgets implentation from Andy Piper -- W3 works again due to font.el being fixed -- Another mule xemacs crash fixed -- Images in widgets, warning fixes and gui_item cleanup from Andy Piper -- package admin fixes under mswindows from Charles Waldman -- miscellaneous mswindows build fixes from Jonathan Harris -- help-echo fix from Hrvoje Niksic -- x font path support from Jim Radford -- MSVC compile fixes from Damon Lipparelli Footnotes: [1] DEC OSF 4.0B to 4.0E for the curious.

2 participants
1 comments

Re: Bug or feature? - file-regular-p 26 years, 1 month

Carsten Leonhardt

I'll resume mumbling to myself... I definitely should have read the documentation for the pertaining libc functions earlier. The patch below makes (file-regular-p "/symlink") return nil on glibc2 systems, however I don't know about compatibility with other libc's. Can anybody tell? *** src/fileio.c 1999/02/03 23:24:46 1.1 --- src/fileio.c 1999/02/04 00:01:22 *************** *** 2495,2501 **** if (!NILP (handler)) return call2 (handler, Qfile_regular_p, abspath); ! if (stat ((char *) XSTRING_DATA (abspath), &st) < 0) return Qnil; return (st.st_mode & S_IFMT) == S_IFREG ? Qt : Qnil; } --- 2495,2501 ---- if (!NILP (handler)) return call2 (handler, Qfile_regular_p, abspath); ! if (lstat ((char *) XSTRING_DATA (abspath), &st) < 0) return Qnil; return (st.st_mode & S_IFMT) == S_IFREG ? Qt : Qnil; }

1 participants
0 comments

Re: Bug or feature? - file-regular-p 26 years, 1 month

Carsten Leonhardt

>>>>> Meself writes: leo> Considering the fact that file-directory-p and file-symlink-p work leo> correctly with remote locations, I'd say that file-regular-p is leo> broken. Further down is what I believe to be another example of it's leo> brokenness ("/vmlinuz" *is* a symlink). I have dug a bit further, and now think that there are two things that are broken. One of them would be the glibc, which accounts for the symlink that is reported as regular file (hence the error on all the emacs flavors). Interestingly enough, ange-ftp (on emacs 19.34) doesn't even need a password to say that "/leo＠localhost:/etc/passwd" is not a regular file, while efs does require one. leo

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