December 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: New Athena widget configuration (was Re: Problem with `configure --with-sound') 25 years, 11 months

Jan Vroonhof

Daniel Pittman <daniel(a)danann.net> writes: > Of course, I have been wrong before. Getting dynamic paths for the > Athena stuff is actually quite a PITA. Isn't it much easier to just have the athena include directory in cflags with -I and then change all the files that include stuff to not use the X11/Xaw prefix? Jan

1 participants
0 comments

Re: New Athena widget configuration (was Re: Problem with `configure --with-sound') 25 years, 11 months

Jan Vroonhof

Daniel Pittman <daniel(a)danann.net> writes: > What's the standard for posting patches to xemacs-patches? You folk > prefer unified diffs, as plain text attachments, yes? Yes, relative to the toplevel src directory and with ChangeLogs to be precise :-) Jan

1 participants
0 comments

Re: New Athena widget configuration (was Re: Problem with `configure --with-sound') 25 years, 11 months

Daniel Pittman

On 10 Dec 1999, Daniel Pittman <daniel(a)danann.net> wrote: [...] > Um, it's actually working for `configure' now. I don't think that > `lwlib' hacking will take that long. Of course, I have been wrong before. Getting dynamic paths for the Athena stuff is actually quite a PITA. I can do it by putting all the dynamic stuff into a single header and then adding that to AC_OUTPUT, but that's a pain. Is there some good way to do dynamic include paths out of the configure script? I can't claim to actually know autoconf -- or couldn't when I started this thing yesterday, anyway. So, any autoconf (or lwlib) guru out there want to advise me about the best way to deal with this issue? I would rather be able to build this before I post patches and all :) Daniel -- Sometimes a scream is better than a thesis. -- Ralph Waldo Emerson

1 participants
0 comments

tex-latin1.el in XEmacs 20.4 25 years, 11 months

Gunnar Evermann

In XEmacs 20.4 we had a file named packages/tex-latin1.el. I can't seem to find that in the 21.x core lisp or the SUMO. Is this intentional or did we lose it? >From the header of tex-latin1.el: ;; gm-lingo.el ;; Translate to ISO from/to net/TeX conventions ... ;; Copyright 1993 Michael Gschwind (mike(a)vlsivie.tuwien.ac.at) ;; Keywords: tex, iso, latin, 8bit ;; From: mike(a)vlsivie.tuwien.ac.at (Michael Gschwind) ;; Newsgroups: gnu.emacs.sources ;; Subject: tex sequence to ISO latin conversions (and back) ;; Date: 13 Oct 1993 12:12:35 GMT ;; Gunnar

1 participants
0 comments

Re: History of Gosling Emacs/FSF Emacs/LEmacs/XEmacs 25 years, 11 months

Hrvoje Niksic

Olivier Galibert <galibert(a)pobox.com> writes: > Do we have some good documents about that? The links on our web > page are mostly broken... Our Internals manual contains some history. You can also search for Jamie's "Emacs time-line" on DejaNews.

1 participants
0 comments

Re: Jobs assignments 25 years, 11 months

Didier Verna

Hrvoje Niksic wrote: > Customize should include me and Didier Verna as secondary. You can also add me as secondary for configure stuff. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠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

1 participants
0 comments

Re: New Athena widget configuration (was Re: Problem with `configure --with-sound') 25 years, 11 months

Daniel Pittman

On 10 Dec 1999, Jan Vroonhof <vroonhof(a)math.ethz.ch> wrote: > "Daniel Pittman" <daniel(a)danann.net> writes: > >> The option `--with-athena' is available to specify the preferred >> Athena widget set. This takes a range of values such as `flat' or >> `3d' or `next' that specify what libraries to prefer. > > Perfect. But please make it clear in the docs that you must set one of > the other options to athena for this to be usefull. As per usual with development, doco comes last[1] in the development cycle. >> Without this option being specified, the user gets libXaw.so >> preferred, with the flat or 3d headers according to the 3d-ness of >> libXaw.so. This retains the current behavior of >> `--with-widgets=athena' -- no surprises to people who don't pay >> attention. > > Actually I would prefer to have one of the sexier ones be the default > <big>IF</big> we can detect them reliably. *grin* Well, I need to actually grab the source and (more importantly) the headers for the Xaw variants and make sure that I can reliably detect them. Then I would be happy to implement a thing of `look for sexy widgets, use them if found'. At the moment it prefers -lXaw3d to -lXaw, even if -lXaw is a 3D Athena library. It will refuse to use a non-3d -lXaw if you asked for something 3d. If you told it to use a 3d library, it can't find the long name version, and -lXaw is a 3d library, I assume that you know what you are doing and that you have installed /that/ 3d Xaw over the top of the normal Xaw library. >> In this vein, `--with-widgets=athena3d' would be the same as the new >> `--with-athena=3d' and `--with-widgets=athena' for backward >> compatibility. > > Is it really needed to be backwards compatible with a few betas? I don't know. At the moment I have backward compatible configuration in there, including the blind assumptions that it made about what and where the Athena libraries were. This is actually much easier than I had though to achieve. I also have an instinct that says not breaking peoples assumptions is nice, at least for a while. I can drop the backward-compatibility stuff if that's desirable though. That will break `./configure --with-widgets=athena3d' though. Um, it's actually working for `configure' now. I don't think that `lwlib' hacking will take that long. What's the standard for posting patches to xemacs-patches? You folk prefer unified diffs, as plain text attachments, yes? Daniel Footnotes: [1] Actually, I wanted to make sure that the configure stuff passed muster here before writing helpful documentation about it since that's what I find hardest :) -- Increasing numbers of private-sector companies are discovering the efficiency of hiring bright undergraduates or recent graduates and paying them next to nothing. -- Washingtonian magazine

1 participants
0 comments

History of Gosling Emacs/FSF Emacs/LEmacs/XEmacs 25 years, 11 months

Olivier Galibert

Do we have some good documents about that? The links on our web page are mostly broken... OG.

1 participants
0 comments

Re: [Bug 7694] Changed - docstrings broken in xemacs-mule and other binaries 25 years, 11 months

Jan Vroonhof

[Meta question: Is timp(a)redhat.com the person to contact about the Redhat XEmacs packages. It would be nice to have a liason with each distributor. I occasionally contact the Debian maintainer when have a critical linux bugfix.] > the JRPM60 xemacs packages to get their feed back too. I guess one > solution would be to allow separate DOC files for each xemacs > executable: this would require some (I think) minor changes to the > xemacs sources and "src/Makefile", something like an option to add a > given suffix to the xemacs executable name and the corresponding "DOC" > and "config.values" files. I think we already support this (on request of the Debian maintainer, to fix the same problem), you can use the --docdir argument to configure to make XEmacs put its docfile where you want. Jan

1 participants
0 comments

Re: Drag-N-Drop 25 years, 11 months

Jan Vroonhof

rossini(a)biostat.washington.edu (A.J. Rossini) writes: > I've been away from development here for a while, but what's the > current situation with respect to XEmacs and either GNOME or KDE > drag-n-drop? Olivier Graf is supposed to be working on Xdnd support (which is the standard GNOME and KDE agreed on). His ideas can be found on http://www.m17n.org/mule/m17n99/papers/Graf/m17n99-dnd.html However we haven't heard from in 6 months or so. If you want to work on it I suggest you try to contact him first. If he is to busy it would be nice if somebody could take over. The major difficulty is integrating it cleanly into the event system. You may wish to discuss that with Ben. 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 December 1999