April 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Steve Carney

I've run into an XEmacs-20.4 etags.el buglet, where it gets into an nconc infinite loop when generating a (probably circular) list of files for tag tables. Below is a simple fix. If there are any follow-ups, please include me on the list because I'm not on the beta list. Thanks, Steve --- /local/xemacs/xemacs-20.4/lib/xemacs-20.4/lisp/packages/etags.el Sat Oct 18 09:04:11 1997 +++ ./etags.el Thu Apr 8 18:52:10 1999 ＠＠ -391,7 +391,7 ＠＠ (defun buffer-tag-table-files () "Returns a list of all files referenced by all TAGS tables that this buffer uses." - (apply #'nconc + (apply #'append (mapcar #'tag-table-files (buffer-tag-table-list))))

1 participants
0 comments

Xpromacs 26 years

SL Baur

Is anyone familiar with this? http://www-poleia.lip6.fr/~baillie/xpromacs.html Xpromacs 1.02 Jean-Christophe BAILLIE - March 29th 1999, 09:35 EST Xpromacs is a project manager running under X11. It uses xemacs as an editor. You can create a project consisting of different programs, modules or shared code, display the structure of this project and directly access xemacs buffers from this structure, generate makefiles, directory structure or archive files. Changes: This new release now compiles under RedHat 5.2, an INSTALL file has been added to help people installing and configuring xpromacs and some small bugs have been resolved. [ details (0) ] License: GPL Category: Development/Tools download-[IMAGE] homepage-[IMAGE] appindex record-[IMAGE]

1 participants
0 comments

Re: Behaviour of call-process 26 years

Enrico Scholz

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > [...] > > That works! Both FASYNC and FIOASYNC clauses cure the problem. Because > > the tracefiles created by this cases looks very similar, I can not say > > which is better. > > I think somebody should write an autoconf test to check which of > these actually works. What would nice to find out is why glibc > defines these ioctl when it doesn't support them? I don't know how to classify the I_GETSIG/I_SETSIG ioctl's. The header says ------------------------------- #define I_SETSIG 6 /* Inform the STREAM head that the process wants the SIGPOLL signal issued. */ #define I_GETSIG 7 /* Return the events for which the calling process is currently registered to be sent a SIGPOLL signal. */ ------------------------------- and libc.info ------------------------------- - Macro: int SIGIO This signal is sent when a file descriptor is ready to perform input or output. On most operating systems, terminals and sockets are the only kinds of files that can generate `SIGIO'; other kinds, including ordinary files, never generate `SIGIO' even if you ask them to. In the GNU system `SIGIO' will always be generated properly if you successfully set asynchronous mode with `fcntl'. - Macro: int SIGPOLL This is a System V signal name, more or less similar to `SIGIO'. It is defined only for compatibility. ------------------------------- Because of the comment at I_SETSIG (*STREAM*), I guess it can be used just with streams but not with sockets. You can read in the SIGIO description, the prefered way to generate the signal is setting asynchronous mode with 'fcntl' > Do you have the glibc info files? Yes, but I have not found much information about the usage of signals in conjunction with sockets. > Do they say something about these settings? I have grep'ed all my info-files and man-pages but have not found anything about I_[SG]ETSIG. Enrico -- eMail: enrico.scholz(a)wirtschaft.tu-chemnitz.de talk: ensc(a)ultra.csn.tu-chemnitz.de

1 participants
0 comments

Re: Mule and obsolescence 26 years

SL Baur

Olivier Galibert <galibert(a)pobox.com> writes in xemacs-beta(a)xemacs.org: > I want to mark some mule functions as obsolete aliases. Where should > I do that? obsolete.el while protected by boundp mule ? Some > mule-obsolete.el ? Do it in the file where the symbols currently are defined. When you mark them obsolete, put the date in a comment so we know when we should start thinking about removing it altogether.

2 participants
1 comments

Re: Add Vietnamese, Ethiopic and Thai support; fix Shift_JIS, BIG5, etc. 26 years

Jan Vroonhof

tomo(a)etl.go.jp (守岡知彦 / MORIOKA Tomohiko) writes: > - modifies koi8-r to decode non Cyrillic symbols not included in ISO > 8859-5 Does this fix the crashes I reported just a few days ago? Then I can just say, wow! > - deletes mule-coding.c and mule-coding.h because they are not used > > Notice that if you apply the patch please delete 0 byte garbages of > mule-coding.c and mule-coding.h. Use patch -E Jan

1 participants
0 comments

Re: Behaviour of call-process 26 years

Jan Vroonhof

Enrico Scholz <enrico.scholz(a)wirtschaft.tu-chemnitz.de> writes: > > Could you patch sysdep.c such that it doens't use these ioctl's but > > instead uses one of the other methods. Searching some manpage on the > > net seems to indicate FIOASYNC should work, > > That works! Both FASYNC and FIOASYNC clauses cure the problem. Because > the tracefiles created by this cases looks very similar, I can not say > which is better. I think somebody should write an autoconf test to check which of these actually works. What would nice to find out is why glibc defines these ioctl when it doesn't support them? Do you have the glibc info files? Do they say something about these settings? Jan -- Jan Vroonhof http://www.math.ethz.ch/~vroonhof/ Mathematik, vroonhof ＠ math.ethz.ch HG E16, ETH-Zentrum, Tel: +41-1-6325456/25154 Raemistrasse 101, CH-8092 Zuerich. Fax: +41-1-6321085

1 participants
0 comments

Re: Applying patches using patch-xemacs.sh ? 26 years

SL Baur

Holger Schauer <Holger.Schauer(a)gmx.de> writes in xemacs-beta(a)xemacs.org: > Hi ! > Please, excuse my ignorance, but how does one apply patches to the > current xemacs-directory ? Change directory to the top level XEmacs source directory. $ gunzip -c xemacs-21.0.66-21.0.67.patch.gz | patch -p2

1 participants
0 comments

Re: Behaviour of call-process 26 years

Enrico Scholz

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > [...] > > > ioctl (filedesc, I_GETSIG, &events); > > > ioctl (filedesc, I_SETSIG, events | S_INPUT); > [...] > Could you patch sysdep.c such that it doens't use these ioctl's but > instead uses one of the other methods. Searching some manpage on the > net seems to indicate FIOASYNC should work, That works! Both FASYNC and FIOASYNC clauses cure the problem. Because the tracefiles created by this cases looks very similar, I can not say which is better. Btw: in unrequest_sigio_on_device() the same I_GETSIG/I_SETSIG stuff will be done and should be fixed there too. Enrico -- eMail: enrico.scholz(a)wirtschaft.tu-chemnitz.de talk: ensc(a)ultra.csn.tu-chemnitz.de

1 participants
0 comments

Re: XEmacs and its multiuser roots (was Re: change \C-m binding to newline-and-indent) 26 years

Matt Curtin

>>>>> In article <m23e2dlchv.fsf(a)demeter.xemacs.org>, SL Baur <steve(a)xemacs.org> writes: sb> Two things, one of which you've already discounted. Since late sb> 1996, the most popular binary kits downloaded from ftp.xemacs.og sb> have been for Linux. The second is based on the number of Linux sb> CD ROM distributions XEmacs appears on. Admittedly, I also have sb> no hard numbers on how many people have installed XEmacs off of sb> Linux CD ROMs. Downloads isn't really a good measurement of users, though. I recognize that this is a Hard Problem, but consider that in my case, I will download the source distribution, build it and install it for something like 4500 potential users. I can't comment on the number of actual users with more granularity than saying "thousands".[1] Making things single-user at the expense of multi-user ease of administration can very easily reduce XEmacs' viability in this environment. Not something I'm really interested in seeing, given that I just fought the fight to migrate from GNU Emacs to XEmacs. Footnote: 1 Good grief. I think I'm starting to understand where all my time is gone. I feel like Mr. Support Man(tm) instead of Mr. Hacker around here. Oddly enough, it wasn't until just now that I could figure out why. -- Matt Curtin cmcurtin(a)interhack.net http://www.interhack.net/people/cmcurtin/

1 participants
0 comments

Re: Applying patches using patch-xemacs.sh ? 26 years

Adrian Aichner

>>>>> "Holger" == Holger Schauer <Holger.Schauer(a)gmx.de> writes: Holger> Hi ! Holger> Please, excuse my ignorance, but how does one apply Holger> patches to the current xemacs-directory ? Don't know as I'm using CVS. Holger> After reading patch-xemacs.sh I came to the conclusion Holger> that in my case "./patch-xemacs.sh xemacs-21.0.66 ." would Holger> do it (with the patch correctly named) but the patch Holger> failed - it couldn't determine the file to patch. Holger> So, I gunzip'ed the patch, and did a patch -p1 < patch and Holger> obtained the same result: for each file patch would ask me Holger> which file to patch :-( The filenames used in the patches Holger> all follow the pattern "XEmacs/xemacs/<filename>" Holger> i.e. CHANGES-beta as <filename>. Well, XEmacs/xemacs does Holger> not exist here (I'm using src/xemacs-<version>), so how Holger> can I apply such a patch ? In directory src/xemacs-<version> you should be able to do this: patch -p2 < patch Here's the relevant bit from the man page: -p num For all path names in the patch file that indicate the names of files to be patched, delete num path name components from the beginning of each path name. If the path name in the patch file is absolute, any lead- ing slashes are considered the first com- ponent (that is, -p 1 removes the leading slashes). Specifying -p 0 causes the full path name to be used. If -p is not speci- fied, only the basename (the final path name component) is used. Good luck, Adrian Holger> TIA, Holger> Holger Holger> -- Holger> --- http://www.coling.uni-freiburg.de/~schauer/ --- Holger> "Welche Linux-Distribution soll ich nehmen?" Holger> -- Aus "Wie starte ich einen Endlosthread ?", Teil 1171 -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

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