August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Jan Vroonhof

"Seiichi Ikiuo" <ikiuo(a)polyphony.co.jp> writes: > --- xemacs-21.2.19/src/syntax.c Fri Jun 25 15:01:08 1999 > +++ xemacs-21.2.19/src/syntax.c.new Fri Aug 20 15:25:21 1999 > ＠＠ -424,7 +424,7 ＠＠ Yes, this is a bug. It is already fixed in the CVS version. Jan

1 participants
0 comments

Is this a bug ? 26 years

Seiichi Ikiuo

I am poor at the Engligh writting. Because an explanation sentence can't be described well, I want it to think that the following one for the difference is seen. --- xemacs-21.2.19/src/syntax.c Fri Jun 25 15:01:08 1999 +++ xemacs-21.2.19/src/syntax.c.new Fri Aug 20 15:25:21 1999 ＠＠ -424,7 +424,7 ＠＠ #endif from--; #ifdef MULE - ch1 = BUF_FETCH_CHAR (buf, from - 1); + ch1 = BUF_FETCH_CHAR (buf, from /* - 1 */); code = SYNTAX_UNSAFE (mirrortab, ch1); if (words_include_escapes && (code == Sescape || code == Scharquote))

1 participants
0 comments

eicq package 26 years

Stephen Tse

SL Baur <steve(a)xemacs.org> writes: > Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > > > Stephen Tse <stephent(a)sfu.ca> writes: > >> Should I send the package to xemacs-patch, or is package now truly > >> independently of xemacs such that I just have to upload to a certian > >> ftp area? > > > The latter. > > Make sure it gets to me somehow. We can put it into CVS, we can put > -pkg tarballs on the FTP site retrievable via the package UI interface > in XEmacs, but it won't go into the Sumo until 21.2 become official. Does 21.1 use packaging system and sumo tarball as well? > > > When XEmacs 21.2 is released we can think about putting it in the > > official package list, but currently we cannot because the packages > > have to work with 21.1. > > Not quite. We may distribute 21.2-only packages if they are bytecompilable > with XEmacs 21.1. If you follow good coding guidelines, your package will > be bytecompilable by an XEmacs that does not have the underlying > support. Can you be more specific? Where can I find the guidelines you are talking about? I have read all those in info already. > See the LDAP package as an excellent example of this. Where can I find this package?

1 participants
0 comments

Re: Yeah! Using instructions missing from the README, xemacs ins talled! (was Re: How can xemacs have been made so hard to install? Do th e developers have any clue it is needlessly hard/undocumented?) 26 years

SL Baur

Bless Terje <link(a)rito.no> writes in xemacs-beta(a)xemacs.org: I wrote: >> I am leery of separating CVS components and we do not have a CVS >> server running on www.xemacs.org. Maybe the thing to do is move the >> webpages to cvs.xemacs.org and automatically mirror a checked out copy >> to the webserver. Anyone interested in putting the scripts together >> to do this? > As in a cron job on www.xemacs.org that does "cd /html; cvs update"? :-) It's not quite that simple. > Or, if you dislike CVS client/server (can't that be tunneled over ssh, > BTW?), Yes, it almost must be according to how Jareth-san set up cvs.xemacs.org. I was thinking more of a periodic script on cvs.xemacs.org to checkout whatever was most current into an ftp-able area and firing off via email or whatever a script on www.xemacs.org to mirror from that area. > you can keep a live site on cvs.xemacs.org and use one of the > gazillion HTTP and/or FTP mirror utilities available. I do not wish to advertise any accessibility from cvs.xemacs.org. That would be wrong.

1 participants
0 comments

Re: [Jan Vroonhof <vroonhof@math.ethz.ch>] Re: constantly crashing in Gnus 26 years

Jan Vroonhof

Karl Kleinpaste <karl(a)justresearch.com> writes: > Nonetheless, the trouble seems to occur much less often. Jan > wondered/worried whether update_frame_window_mirror was being misused > elsewhere -- perhaps there are simply more cantankerous occurrences of > the same problem elsewhere? It is not really misused. It just a real race condition. There are loads of legitimate uses for update_frame_window_mirror and I am not sure none of them can occur when a keypress event is in the que. We'll just have to make x_any_window_to_frame smarter. Either by changing the scrollbar check to also check non-current maps or by doing the parent check, like I originally intended. Does anybody know how expensive XtWindowToWidget is? Jan

2 participants
1 comments

Re: [Jan Vroonhof <vroonhof@math.ethz.ch>] Re: constantly crashing in Gnus 26 years

Ulrich Drepper

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > This patch will (or should, because I didn't test it) make the crash > go away while I ponder on how fix x_any_window_to_frame. If you get > the message could please lookup the window id in the output of > 'xwininfo -tree' Once I replaced STDERR by stderr I was able to compile it and will use it from now on. I'll let you know when I see the message. -- ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Cygnus Solutions `--' drepper at cygnus.com `------------------------

1 participants
0 comments

Re: kde-xemacs or gnome-xemacs? 26 years

Jan Vroonhof

Bless Terje <link(a)rito.no> writes: > But GTK is GPL... :-) > > BTW, how the hell does this harmonize with the Windoze "native" port? GTK would probably be easier there because it has a more of the widgets that also exist on Windows. Let's port the Unix version to winelib :-) Jan

1 participants
0 comments

Re: [Jan Vroonhof <vroonhof@math.ethz.ch>] Re: constantly crashing in Gnus 26 years

Karl Kleinpaste

Ulrich Drepper <drepper(a)cygnus.com> writes: > The C backtrace is unusable as always Start attaching a gdb to xemacs. As xemacs dies, it will get stuck in gdb purgatory for you. The stack will be usable there.

1 participants
0 comments

Re: [Jan Vroonhof <vroonhof@math.ethz.ch>] Re: constantly crashing in Gnus 26 years

Karl Kleinpaste

I wrote: > I want to observe that I applied this patch as well and have been > running for 2 days with no more of this type of crash... _/Murphy was an optimist/_ Not 20 minutes after writing this, xemacs choked on me again. Same symptoms, same stack trace, same type of "xwininfo -tree" output. The kbd event that induced the trouble was a measly Control_R key (keycode 66, from x_event->xkey.keycode). Nonetheless, the trouble seems to occur much less often. Jan wondered/worried whether update_frame_window_mirror was being misused elsewhere -- perhaps there are simply more cantankerous occurrences of the same problem elsewhere?

1 participants
0 comments

Re: kde-xemacs or gnome-xemacs? 26 years

Jan Vroonhof

wmperry(a)aventail.com (William M. Perry) writes: > > And the fact that your are never going to get RMS's permissions for that > > all important "as a special exception you are allowed to link with the QT > > 2.00, free edition". > > Who cares? :) > > And Qt 2.x is now under the 'QPL', which is an officially 'liked' license > and approved by all the open source goody-goodies. :) I think it is GPL > compliant now. Maybe it changed since I last looked because I thought it was not. 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 August 1999