November 1999 - XEmacs-Beta - XEmacs Mailing List Archives

XEmacs 21.2.19 "Sneaky Bastard 19991102" not released 26 years

Jan Vroonhof

It has been a long time since their has been an 21.2 release. To allow people without CVS access to enjoy the delights of the portable dumper and other goodies added since July, I have made http://www.math.ethz.ch/~vroonhof/emacs/xemacs-sneaky-19991102.tar.gz This a CVS snapshot of the CVS as of to day. The only things I did are - cvs checkout -r release-21-2 - change the code name to "Sneaky Bastard 19991102" to allow identification. - renamed toplevel directory - tar xzf xemacs-sneaky-19991102.tar.gz Nothing else. This is not a real beta release, in particular - It is not test compiled at all. - It is still called 21.1.19 and will overwrite older versions of 21.1.19 on install - CHANGES.beta and other readme's have not been updated. - The codename is not a part of Tokyo. Jan

1 participants
0 comments

Re: Building xemacs-packages from the top. Possible? 26 years

Jan Vroonhof

Mats Lidell <Mats.Lidell(a)contactor.se> writes: > When it comes to the packages I fail to find any decent way to build > them all from the top. The best I have found is to go around in leaf > directories and "make" like this: > > "make STAGING=/... bindist" > > Now this is not what you want to do after a cvs update. I would want > to be able to build it all from the top. You are supposed to be able to just type "make" in the toplevel directory. >From the toplevel Makefile all: for dir in $(SUBDIRS); do \ $(MAKE) $(MFLAGS) -C $${dir} autoloads; \ done for dir in $(SUBDIRS); do \ $(MAKE) $(MFLAGS) -C $${dir} bytecompile; \ done Jan

1 participants
0 comments

Re: Support for /usr/share/info 26 years

Jan Vroonhof

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > Lateish Debian systems enforce placing Info pages to /usr/share/info > rather than /usr/info. XEmacs doesn't seem to recognize this. Of > course, I can add this to Info-directory-list, but I don't know > off-hand how to fix this correctly (in the source). Add it to (defvar paths-default-info-directories (list (paths-construct-path '("usr" "local" "info") (char-to-string directory-sep-char)) (paths-construct-path '("usr" "info") (char-to-string directory-sep-char))) "Directories appended to the end of the info path by default.") Jan

1 participants
0 comments

Re: applying patches 26 years

Andreas Jaeger

>>>>> Jan Vroonhof writes: Jan> Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: >> How are patches sent to xemacs-patches handled at the moment? Jan> Extremely ad-hoc. AFAICS nobody is applying patches to the packages at Jan> the moment. >> Is anyone applying the patches sent there by people without cvs-write >> access? Jan> Andy and Michael have applied most them. Normally Steve applies all Jan> that were left out, just before a new beta releases. >> We should really make sure we do not lose any patches and that >> everything that is applied to 21.1 is also applied to 21.2! Jan> Yes. We need some explicit tracker system (that is what xemacs-review Jan> is meant for but I am not sure it is working properly). There is a Jan> whole lot of patches to the packages that are "in the queue" for two Jan> months now. I would love it if there were some system in there Jan> somewhere. For instance there is a patch from _February_ about esound Jan> support that I still want look at (I didn't have esound at the time). Hi, can I help out? After considering this for some time, I'm volunteering to help. I should have enough time to keep the CVS archive for the packages uptodate. For those who don't know me, let me introduce myself briefly. I'm one of the glibc developers and XEmacs is one of my favorite programs. In mid 1997 I helped to get XEmacs running with glibc2 - and since I'm always using glibc testreleases, XEmacs still works with glibc;-). I'm currently employed by the Linux distributor SuSE and have spent some time during the last weeks to get a mule enabled XEmacs 21.1.7 on our next distribution. Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.rhein-neckar.de

1 participants
0 comments

Re: Q: warn_when_safe vs. stderr_out 26 years

Jan Vroonhof

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > Are there any rules how to pick the correct level amongst these: > > The recognized warning levels, in decreasing order of priority, are > 'emergency, 'alert, 'critical, 'error, 'warning, 'notice, 'info, and > 'debug. Not really I think. I think the most important would be their value relative to the default display-warning-minimum level (which IMHO is currently too low).

1 participants
0 comments

Re: Q: warn_when_safe vs. stderr_out 26 years

Adrian Aichner

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)iskon.hr> writes: Hrvoje> Adrian Aichner <aichner(a)ecf.teradyne.com> writes: >> Can someone here give me a hint where to start looking for >> documentation on usage of warn_when_safe vs. stderr_out in XEmacs >> source? Hrvoje> Use warn_when_safe() as you would use the Lisp function Hrvoje> `display-warning', except that warn_when_safe() accepts format Hrvoje> parameters a la `message'. Ah, that gets me started. Thanks! >> I wasn't able to find anything on either of them in 21.1 or 21.2 CVS >> xemacs/man sources. Hrvoje> Huh? `grep warn_when_safe *.c' will give you tens of Hrvoje> examples of usage. This is true. I still find it hard though to deduce correct usage from examples. I used stderr_out because I found examples of its usage in the first place :-) Are there any rules how to pick the correct level amongst these: The recognized warning levels, in decreasing order of priority, are 'emergency, 'alert, 'critical, 'error, 'warning, 'notice, 'info, and 'debug. Thanks, Adrian

1 participants
0 comments

Building xemacs-packages from the top. Possible? 26 years

Mats Lidell

Hi, I'm trying to catch up on beta testing xemacs by picking the sources from CVS. Works fine. When it comes to the packages I fail to find any decent way to build them all from the top. The best I have found is to go around in leaf directories and "make" like this: "make STAGING=/... bindist" Now this is not what you want to do after a cvs update. I would want to be able to build it all from the top. I have really tried to look for documentation both in xemacs and xemacs-packages module but failed to find anything. Since this is beta test stuff I don't know what to expect either but to be frank I was expecting something a bit more polished and I'm sure there is. So how to do it? Yours -- %% Mats

1 participants
0 comments

verilog-mode.el 3.37 released 26 years

Neal D. Becker

Note: I have not personally tested this code. ;;; You can get step by step help in installing this file by going to ;;; <http://www.surefirev.com/emacs_install.html>

1 participants
0 comments

Ethiopic in 21.1.7++ 26 years

Vin Shelton

I'm working on the candidate for 21.1.8 (everything checked in to CVS), and when I try to: Mule -> Set Language Environment -> Ethiopic I get the following error and backtrace: Symbol's function definition is void: setup-ethiopic-environment-internal Signaling: (void-function setup-ethiopic-environment-internal) setup-ethiopic-environment-internal() set-language-environment("Ethiopic") eval((set-language-environment "Ethiopic")) I'd like to get this working before I release 21.1.8 (tonight, I hope). Can anyone offer a patch? - vin

1 participants
0 comments

Support for /usr/share/info 26 years

Hrvoje Niksic

Lateish Debian systems enforce placing Info pages to /usr/share/info rather than /usr/info. XEmacs doesn't seem to recognize this. Of course, I can add this to Info-directory-list, but I don't know off-hand how to fix this correctly (in the source). Any ideas?

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 November 1999