April 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Michael Sperber

>>>>> "Gunnar" == Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: Gunnar> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: >> So I finally broke down, took Charles Waldman's fixes, applied what's >> left to PCL-CVS 2.9.8, and made a package from it. Gunnar> excellent! Just yesterday I was considering doing the same. Let's Gunnar> *finally* get around to releasing a new version! >> (Including a gross hack to make it work with our diff.el.) It's >> ready to go in, only I'm waiting for a bugfix release Stefan Monnier >> has promised me RSN. Gunnar> didn't he just announce 2.9.9 yesterday on gnu.emacs.sources? Yup. Gunnar> let me know if you want me to test your package. That would be nice. I've now checked it in. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: gtk status update.... 24 years

William M. Perry

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > wmperry(a)aventail.com (William M. Perry) writes: > > > I got tired of writing spec documents and started hacking some code for the > > really basic integration, and I've got a (tty-only right now) XEmacs that > > is using the Gtk / Gdk event loop to drive it. I didn't trust it quite > > enough to write this email message, but it does appear to work. There is > > something weird with the QUIT macro stuff, but... baby steps. :) > > Which reminds me. Do you want a branch on cvs.xemacs.org to publish your > stuff? Hmmm... I could do it from there or I could just maintain a set of patches in cvs on gnu.org or libre.aventail.com. How big a pain is it to set up on xemacs.org? I lost my SSH key that I sent martin a while ago in a machine reorg (didn't have it on the laptop like I thought). I think I've decided to just bite the bullet and pull some serious all-nighters next week and do the native Gtk/Gdk port. It doesn't look like it will be horribly difficult, and there is a lot of Xt cruft lying around in all the *-x.c files, and instead of cluttering them up with ifdefs for Gtk, I'll just suffer some pain. :) This will also make it easier to bring it up to the 21.2 branch and do andy's widget work eventually. -Bill P.

1 participants
0 comments

Re: gtk status update.... 24 years

Jan Vroonhof

wmperry(a)aventail.com (William M. Perry) writes: > I got tired of writing spec documents and started hacking some code for the > really basic integration, and I've got a (tty-only right now) XEmacs that > is using the Gtk / Gdk event loop to drive it. I didn't trust it quite > enough to write this email message, but it does appear to work. There is > something weird with the QUIT macro stuff, but... baby steps. :) Which reminds me. Do you want a branch on cvs.xemacs.org to publish your stuff? Jan

1 participants
0 comments

Re: efs and custom 24 years

Jan Vroonhof

Ben Wing <ben(a)666.com> writes: > > That is because I happen to like the base structure of customize and > > because actually prefer using customize for the more non-trivial stuff > > such as reftex-label-alist > > > > I do agree the UI needs a lot of work. > > unfortunately this is a standard problem with free software hackers. they tend > to be very theoretical types with the attitude of "i've proved it's solvable, > that's enough". While I agree with that comment (and being a mathematician I have an even stronger tendency to do that) I fail to see what you mean here. I can see that customize is working in some cases (i.e. for an XEmacs hacker like me needing to edit alists of plists) which convinces me that it is worthwhile to try to make it work. However I do not consider the original problem "How to make Emacs easy to configure for newbies" solved at all. In fact now that Per has made the first few steps we can finally begin see clearly where the real problems lie. Jan

1 participants
0 comments

Re: proposed Eistring interface 24 years

Didier Verna

Cosmetics only. All of this looks nice to me, except for one thing: the "Eistring (name);" syntax to declare a new variable. The need for parentheses in this context looks disturbing. I'd prefer another name to the macro, something like "DECLARE_EISTRING (name);" which looks more like a function call, but still clearly states that this is a declaration. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠lrde.epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

2 participants
1 comments

Re: set-window-display-table 24 years

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > >>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > Hrvoje> James LewisMoss <jimdres(a)mindspring.com> writes: > >> This function is used by rot13 (in misc-games) and used as the > >> value in a defsetf in cl-macs, but doesn't seem to be defined > >> anywhere. > > Hrvoje> set-window-display-table is an FSF Emacs function. > > So we need to fix "misc-games" Yup. > and cl-macs. It's only a harmless defsetf, declaring how to handle things like: (setf (window-display-table foo) bar) There's no harm having it in, except for potentially causing confusion. We could comment it out as an FSF-ism.

1 participants
0 comments

Re: set-window-display-table 24 years

Hrvoje Niksic

James LewisMoss <jimdres(a)mindspring.com> writes: > This function is used by rot13 (in misc-games) and used as the value > in a defsetf in cl-macs, but doesn't seem to be defined anywhere. > Are these elisp files just old and broken or is something missing? > (This is from a debian bug report.) set-window-display-table is an FSF Emacs function. XEmacs uses the `display-table' specifier which can be generalized to any combination of window, frame, and buffer specification. For instance, instead of this: (set-window-display-table (selected-window) table) one would write: (set-specifier current-display-table table (selected-window))

2 participants
1 comments

set-window-display-table 24 years

James LewisMoss

This function is used by rot13 (in misc-games) and used as the value in a defsetf in cl-macs, but doesn't seem to be defined anywhere. Are these elisp files just old and broken or is something missing? (This is from a debian bug report.) Thanks Jim -- ＠James LewisMoss <dres(a)ioa.com> | Blessed Be! ＠ http://www.ioa.com/~dres | Linux is kewl! ＠"Argue for your limitations and sure enough, they're yours." Bach

1 participants
0 comments

Future work on XEmacs 24 years

Martin Buchholz

I am quite likely to be moving to Japan over the next couple of months. If this happens, I will probably be doing quite a bit of XEmacs hacking while I'm in Japan. However, during the transition I will likely have less free time for hacking. Martin

1 participants
0 comments

Re: proposed Eistring interface 24 years

Hrvoje Niksic

Ben Wing <ben(a)666.com> writes: > i've created a new api for simplifying mule-correct string > operations. I don't understand the motive for creating this. What's wrong with the existing API's, as described in Internals->Coding for Mule? In other words, do we really need another string manipulation layer besides Lisp strings and buffers? The current developers seem to find the existing API comfortable. On the other hand, new developers might find a string layer more intimidating than useful.

3 participants
3 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 April 2000