December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Package structure stable? 25 years, 11 months

Didier Verna

Christoph Wedler writes: CW> Can we expect the structure of the package system to be stable? * You mean for 21.0 ? Hmmm. CW> I hope the base will stay at `~/.xemacs' since most people are now CW> accustomed to it -- and becoming accustomed to the package system was hard CW> enough since there are no real decent docs about it... (Thanks to Jan for CW> having given essential info for package authors.) I will surely move to ~/.xemacs/packages/ and it is a Good Thing. For the rest, you're very right. It's a pity that people are "accustomed to it". CW> Don't understand me wrong: the packaging system is very cool. But please CW> consider that non-full-time beta testers want to spend their time on other CW> XEmacs aspects than the package system... I.e., don't change the package CW> structure. Thanks, It will change because it's not optimal. The conclusion we had some time ago about this for 21.0 is that we should probably tell the minimum about packages: were to retrieve the tarballs and how to install it. I think that's all if we don't want to make people scream[1]. Footnotes: [1] sounds like a certain flamewar is going to start again. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: 21.0 "Poitou60" IRIX6.2 compilation warning 25 years, 11 months

Paul Bibilo

Colin Rafferty writes: > Paul Bibilo writes: > > > I succesfully built the latest 21.0 on IRIX6.2, and got just a single > > warning message during the compilation which somebody might be > > interested in. > > > cc -c -g -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -xansi /tmp_mnt/devdisk/d54man/gnu/xemacs-beta/xemacs-21/src/event-stream.c > > cfe: Warning 851: /tmp_mnt/devdisk/d54man/gnu/xemacs-beta/xemacs-21/src/event-stream.c, line 3786: constant initializer expression is invalid (refers to automatic variables). > > struct Lisp_Event terminal_copy = *error_check_event (terminal) ; > > ----------^ > > I built it on IRIX 6.4, and I didn't get an error. > > Anyway, as far as I can understand the code, to see if it is actually > a bug, type the following key sequence (make sure that is a capital Y): > > C-x 5 Y > > You should get the following error (capital y): > > C-x 5 Y not defined. > This is what I get. -- Paul

1 participants
0 comments

Package structure stable? 25 years, 11 months

Christoph Wedler

Can we expect the structure of the package system to be stable? * Currently, the base of early packages is `~/.xemacs'. So is the explanation in info node `(XEmacs)Startup Paths'. * In etc/NEWS, there is a treat that this will change to `~/.xemacs/packages'. * In info node `(XEmacs)Using Packages', this threat already became true. I hope the base will stay at `~/.xemacs' since most people are now accustomed to it -- and becoming accustomed to the package system was hard enough since there are no real decent docs about it... (Thanks to Jan for having given essential info for package authors.) Don't understand me wrong: the packaging system is very cool. But please consider that non-full-time beta testers want to spend their time on other XEmacs aspects than the package system... I.e., don't change the package structure. Thanks, - Christoph

1 participants
0 comments

Re: 21.0 "Poitou60" IRIX6.2 compilation warning 25 years, 11 months

Colin Rafferty

Paul Bibilo writes: > I succesfully built the latest 21.0 on IRIX6.2, and got just a single > warning message during the compilation which somebody might be > interested in. > cc -c -g -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -xansi /tmp_mnt/devdisk/d54man/gnu/xemacs-beta/xemacs-21/src/event-stream.c > cfe: Warning 851: /tmp_mnt/devdisk/d54man/gnu/xemacs-beta/xemacs-21/src/event-stream.c, line 3786: constant initializer expression is invalid (refers to automatic variables). > struct Lisp_Event terminal_copy = *error_check_event (terminal) ; > ----------^ I built it on IRIX 6.4, and I didn't get an error. Anyway, as far as I can understand the code, to see if it is actually a bug, type the following key sequence (make sure that is a capital Y): C-x 5 Y You should get the following error (capital y): C-x 5 Y not defined. If you get this one instead (lowercase y), then it's a bug: C-x 5 y not defined. -- Colin

1 participants
0 comments

Re: B DEL in XEmacs 21.2 b4/Gnus 5.6.45 25 years, 11 months

Jan Vroonhof

Kristian Ellingsen <kellings(a)online.no> writes: > I'm running Red Hat Linux 5.1, XEmacs 21.2 beta 4, Gnus 5.6.45. In > console mode, B DEL in Gnus (article deletion) gives B BS undefined. In > Is there something wrong with my console tty configuration? How do I > change it? What does C-h v tty-erase-char give in your case? I think this setting is correct however as backspace gives BS for you. The question is therefore, why does delete not give DEL. (It works on my debian install). linux.el thinks the delete key should generate "\e[3~" You can test this by typing "cat >testfile" in a shell on a console and typing delete, RET, C-d and then lookin at that file. Jan

3 participants
3 comments

B DEL in XEmacs 21.2 b4/Gnus 5.6.45 25 years, 11 months

Kristian Ellingsen

I'm running Red Hat Linux 5.1, XEmacs 21.2 beta 4, Gnus 5.6.45. In console mode, B DEL in Gnus (article deletion) gives B BS undefined. In X, it works great, so does B DEL in XEmacs 20.4 (both in console and in X11). It seems like XEmacs thinks DEL and BS is all BS. I tried 'xemacs -vanilla', but DEL still behaves as BS (BackSlash). Is there something wrong with my console tty configuration? How do I change it? -- KRISTIAN ELLINGSEN, +47 905 13 552 http://ellingsen.home.ml.org/ http://home.telia.no/~kellings/ mailto:kellings＠online.no --We don't care. We don't have to. We're the Phone Company--

1 participants
1 comments

Re: XEmacs 21.0.60 is released 25 years, 11 months

Hrvoje Niksic

Did my cus-dep bugfix make it to 21.0.60? I think it should be in 21.0 because it's package-related, and without it many packages cannot be built properly.

1 participants
0 comments

Re: [Failure, Patch filelock.c] XEmacs 21.0-b60 "Poitou60", i386-pc-win32 25 years, 11 months

Jan Vroonhof

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > On Windows NT, nt/config.h no longer defines CLASH_DETECTION, since NT > does not support symbolic links, which are the bread and butter of > CLASH_DETECTION today. > > However, src\filelock.c causes the build to fail because of this: > > #ifndef CLASH_DETECTION > #error CLASH_DETECTION is not defined?? > #endif > > How about this patch? > > 1998-12-11 Adrian Aichner <aichner(a)ecf.teradyne.com> > > * filelock.c: It is not an error under native WINDOWSNT for > CLASH_DETECTION to be undefined, since NT does not support > symbolic links. If CLASH_DETECTION is undefined that this file should not be compiled [this is what this message is all about]. So I think this should be fixed elsewhere. Jan

1 participants
0 comments

Re: XEmacs 21.0.60 is released 25 years, 11 months

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > The only technical detail lacking for release is a working PGP and > we're working on that. Note that mailcrypt/package-get also fails badly if you have never used pgp before (i.e. the user never ran pgp -kg). Then pgp gives a different error message and mailcrypt never offers to fetch the key from the pgp server. You just get an (error "Package index failed to verify") and you cannot continue. Even after I had ran "pgp -kg" I had some problems as mailcrypts default keyserver (pgp.ai.mit.edu) is too slow and mailcrypt times out. Jan

1 participants
0 comments

save-options-file, save-options-init-file meaningful in 21.0? 25 years, 11 months

Adrian Aichner

Should these still be around in 21.0, now that Options->Save Options misc-user runs `customize-save-customized' `customize-save-customized' is an interactive autoloaded Lisp function -- autoloads from "cus-edit" Documentation: Save all user options which have been set in this session. saves to custom-file? Adrian Apropos search for: "save-options" * = command (M-x) or user-variable. a = autoloaded, b = byte-compiled, i = internal, l = lambda, m = macro. Functions and Macros: Variables and Constants: save-options-file - File to save options into. save-options-init-file - File into which to save forms to load the options file (nil for .emacs).

1 participants
0 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 December 1998