January 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: athena 3d, there it goes again. 24 years, 10 months

Daniel Pittman

On Sat, 29 Jan 2000, Stef Epardaud <stef(a)lunatech.com> wrote: > i compiled xemacs latest cvs with: ./configure --with-mule > --with-athena=3d --with-widgets=athena --with-dialogs=athena Erk. This is a result of a not-applied patch adding HAVE_ATHENA_3D to src/config.h.in. This causes the check to happen if either flat or 3D Athena widgets are used. I have resent the patch to -patchs, please apply soonest. Daniel -- Remember that under the skin you fondle lie the bones, waiting to reveal themselves. -- Ikkyu

2 participants
1 comments

Re: Use DEFAULT argument to completing-read 24 years, 10 months

Jan Vroonhof

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > My opinion: the XEmacs audience is largely computer professionals > who will have no problem using 'tar' (or similar) and installing > the packages they need to get work done. Note that I think that "computer professionals" don't even are the majority of our users. > So I think providing a fancy interface over the package system is > largely a waste of time. I count myself under "computer professional" but I still prefer the computer to do the handy work of fetching and upgrading. Jan

1 participants
0 comments

Re: Use DEFAULT argument to completing-read 24 years, 10 months

Jan Vroonhof

Martin Buchholz <martin(a)xemacs.org> writes: > The biggest problem of all is that the stable xemacs-21.1 doesn't > really exist anymore. Nobody can get a version of xemacs-21.1 with > all the packages that existed at that time (except by grovelling > through CVS and rebuilding, perhaps). At what "time"? Note that we had multiple 21.1.x releases. > Suppose your friend wanted a version of XEmacs that `Just Works'. > What do you recommend? If he can spare the download volume and is not using IRIX: XEmacs 21.1.8+sumo. The packages are not nearly in such a awful state as you describe. > Certainly not xemacs-21.2.27, even though you > use it... Most of my production work is done on XEmacs 21.1.8+pui installed latest packages. As I am using AucTeX+reftex heavily that exactly the ideal situation (20.4 shipped with a broken reftex). > btw, you'll have to get the packages separately. Hmmm, someone who > hasn't used xemacs-21.1 for years has just done major upgrades to the > base packages - not all the bugs have been shaken out yet. And no one > seems interested in `back-porting' to xemacs-21.1. And why should > they? Surely you are talking hypotheticals here. The current system allows stupid packaging mistakes to slip through sometimes, but Andreas response time is quick enough to not let this be a problem. This situation must be improved, but I don't see it as that bad. Note that the traditional model also can have brown-bag release mistakes (21.0 comes to mind). Note that the most major breakage in the packages too date has not come from 21.2 stuff leaking in but from Mule stuff leaking in the non-mule version. You want to away with the Mule/non-mule builds too? > One simple rule: if the package developer is primarily a user of the > development version of the xemacs core, then that package should never > make it by default into the `stable' release (I count packages in the > stable release). ``There is no such thing as portable software, only > software that has been ported.'' Note that a lot of the packages that have been upgraded (in fact ALL the stuff that has non-bugfix upgrades) have their own testing period. One the things that packages are good at is coping with elisp that has its of own release cycle. All the problems you bring up are on the fringe between the core and packages where the coupling is tightest (and where there is definitely stuff that we maintain). IMHO is a mistake to think that bringing everything back into the core will magically solve all problems and will require no time. Jan

1 participants
0 comments

Re: tab loses track of which buffer is associated 24 years, 10 months

Karl Kleinpaste

Andy Piper <andy(a)xemacs.org> writes: > This should fix: Yup, it does; thanx.

1 participants
0 comments

Re: Tabs' name strings are not font-switched with the rest of XEmacs 24 years, 10 months

Karl Kleinpaste

Karl Kleinpaste wrote: >> reacts to this by smallifying as the text reduces to the "nil2" >> font, the font used in the tabs continues to be original size. Andy Piper <andy(a)xemacs.org> writes: > Does this work for you now? Since 21.2.27, yes.

1 participants
0 comments

Re: [PATCH] Last assault on binary-process-output 24 years, 10 months

Hrvoje Niksic

"Kirill 'Big K' Katsnelson" <kkm(a)dtmx.com> writes: > Some time ago, Hrvoje Niksic wrote... > >"Kirill 'Big K' Katsnelson" <kkm(a)dtmx.com> writes: > > > > > One correction, I am going to remove this variable by release time, > > > not obsolete it. > > > >Are you sure that's a good idea? Do you think there's code that > >depends on it? > > Code cannot depend on it: This variable is to be bound, not set by > design. I know; what I meant was: Do you think there's code that depends on binding that variable to non-nil actually doing something?

2 participants
1 comments

Re: gnuclient's immediate exit 24 years, 10 months

Michael Sperber

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> At 11:37 AM 1/26/00 +0100, Michael Sperber [Mr. Preprocessor] wrote: >> But gnuclient -nw also exits immediately, albeit for a different >> reason: >> >> (1) (error/warning) Error in process filter: (error Image instantiator Andy> format is invalid in this locale. [tab-control :descriptor Buffers :face Andy> buffers-tab :orientation top :properties (:items ([*scratch* Andy> (buffers-tab-switch-to-buffer *scratch*)]))]) >> >> This bug has been in there for quite a while, and was reported >> previously. It really needs to be fixed. Andy> This works for me - maybe I am misunderstanding. What's to misunderstand? Also, I'm not the only one seeing it. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

athena 3d, there it goes again. 24 years, 10 months

Stef Epardaud

i compiled xemacs latest cvs with: ./configure --with-mule --with-athena=3d --with-widgets=athena --with-dialogs=athena and Installation tells me: Athena library to link: Xaw3d Athena header include path: X11/Xaw3d so i assume i have Xaw3d linked. as says ldd /usr/local/bin/xemacs-21.2 libXaw3d.so.6 => /usr/X11R6/lib/libXaw3d.so.6 (0x40019000) ... but when i start it up, it complains and says: (1) (device/error) It seems that XEmacs is built dynamically linked to the flat Athena widget library but it finds a 3D Athena variant with the same name at runtime. This WILL cause your XEmacs process to dump core at some point. You should not continue to use this binary without resolving this issue. This can be solved with the xaw-wrappers package under Debian (register XEmacs as incompatible with all 3d widget sets, see update-xaw-wrappers(8) and .../doc/xaw-wrappers/README.packagers). It can be verified by checking the runtime path in /etc/ld.so.conf and by using `ldd /path/to/xemacs' under other Linux distributions. One solution is to use LD_PRELOAD or LD_LIBRARY_PATH to force ld.so to load the flat Athena widget library instead of the aliased 3D widget library (see ld.so(8) for use of these environment variables). this seems weird, as i do want Xaw3d and i thought i did every thing to have it. more /etc/ld.so.conf /usr/X11R6/lib/Xaw3d /usr/X11R6/lib /usr/lib/libc5-compat /lib/libc5-compat really, i don't get that warning, what does it mean. did i do something wrong ? sorry to post this as i know it has been discussed quite some times, but i don't recall someone pointing to this message. -- # Stef Epardaud, # There is no limit to the power of computing ... # Java Defeater # ... except men maybe ? # Earth # Lunatech Research, # Solar System # soon we will quit researching and start finding...

1 participants
0 comments

Re: ispell vs gutter tabs 24 years, 10 months

Hrvoje Niksic

Andy Piper <andy(a)xemacs.org> writes: > At 03:28 PM 1/28/00 -0500, Raymond Toy wrote: > > > >Sorry if this is been brought before. I don't follow the lists as > >closely has as I used to. > > > >If I run ispell on a word that's misspelled, ispell puts up a window > >with possible corrections. With gutter tabs on, that window ends up > >being under the gutter tabs and therefore unreadable. > > > >A known bug? Known solutions? > > Can you find out what function is being used to popup the frame - > make-dialog-frame doesn't have this problem. It doesn't pop up a frame, but a *window*. For instance, start `xemacs -q', and type `burek M-$'. What I get is: That is, the choices window with the "(0) Burke" choice is apparently hidden beneath the gutter. If I turn off the gutter, the choices show up.

1 participants
0 comments

tab loses track of which buffer is associated 24 years, 10 months

Karl Kleinpaste

21.2.27. Start XEmacs. `C-x C-f' /tmp/thisisaveryveryveryverylongfilename RET Type a few characters into it. `C-x C-f' /var/tmp/thisisaveryveryveryverylongfilename RET Type a few characters into it. Note that the filenames are the same, so the second buffer has "<2>" appended to it. Try selecting the buffers by mousing the tabs. Only the second can be reached; both tabs bring up the same buffer (the 2nd, as I see it).

2 participants
2 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 2000