February 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: 21.2.9: etc/PACKAGES out of date 25 years, 2 months

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > Right. This patch removes the language regarding dumped-lisp.el, but > the file still needs some sanity checking for other updates. > -This data is up-to-date as of 13 January 1998. > +This data is up-to-date as of 10 February 1999. So not it is NOT up-to-date. There a some packages missing for instance. Jan

1 participants
0 comments

Re: XEmacs 21.2.10 "Boreas" is released 25 years, 2 months

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > It should have been. Or do you mean the package-index file on the FTP > site? I mean the copy on the FTP site. For me (and a lot of others) packages that are not in ftp://ftp.xemacs.org/pub/pacakges/package-index.LATEST.pgp do not exist. I am intentionally stubborn here because I want to strictly act a somebody not familiar with the package system would do. > States at present. I won't sign with the `international' version of > PGP 2.6, so perhaps I should start signing with gpg and be done with > it. That would be OK with me. gpg signatures are compatible with PGP 5 aren't they? I can bear not been able to verify (I have neither of the two installed) just as long as people who need/want to can. It is however not "simply starting" starting signing. We need to do something for that too a. Upgrade mailcrypt and make sure it handles PGP 5 and gpg correctly. b. [IMPORTANT] Make sure a package upgrade has a graceful failure mode when the index is gpg signed but you have (prepared for use) neither PGP nor gpg. It should not put out an alarming (error "Package index signature failed). Jan

1 participants
0 comments

Re: 21.2-b9 success 25 years, 2 months

SL Baur

nbecker <nbecker(a)fred.net> writes in xemacs-beta(a)xemacs.org: > 21.2 \"Athena\" XEmacs Lucid (beta9)" > Shadows: > /usr/local/lib/xemacs/xemacs-packages/lisp/gnus/pop3 hides /usr/local/lib/xemacs/xemacs-packages/lisp/mail-lib/pop3 Andy? Does the pop3.el in Gnus need to go away? > /usr/local/lib/xemacs/xemacs-packages/lisp/elib/elib-node hides /usr/local/lib/xemacs/xemacs-packages/lisp/pcl-cvs/elib-node > /usr/local/lib/xemacs/xemacs-packages/lisp/elib/dll hides /usr/local/lib/xemacs/xemacs-packages/lisp/pcl-cvs/dll > /usr/local/lib/xemacs/xemacs-packages/lisp/elib/dll-debug hides /usr/local/lib/xemacs/xemacs-packages/lisp/pcl-cvs/dll-debug > /usr/local/lib/xemacs/xemacs-packages/lisp/elib/cookie hides /usr/local/lib/xemacs/xemacs-packages/lisp/pcl-cvs/cookie Grab a new pcl-cvs package. The elib stuffs have been extracted to their own package. > 5 Emacs Lisp load-path shadowings were found

2 participants
1 comments

Re: packages status: JDE, VM,W3 25 years, 2 months

SL Baur

Andreas Jaeger <aj(a)arthur.rhein-neckar.de> writes in xemacs-beta(a)xemacs.org: ... > I also noticed that VM and W3 also have released newer versions than > are in the CVS archive. Shouldn't these packages updated? O.K. Where does the VM source live now? Where does the W3 source live now? I appear to have out-of-date information.

2 participants
2 comments

Re: XEmacs 21.2.10 "Boreas" is released 25 years, 2 months

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > SL Baur <steve(a)xemacs.org> writes: >> Fixed versions of hm--html-menus and jde have also been uploaded to >> the package area: >> ftp://ftp.xemacs.org/pub/xemacs/packages > Please update the package index too! It should have been. Or do you mean the package-index file on the FTP site? > P.S. Is it intentional that the package indices are now no longer > signed? Unfortunately, yes. I have no idea what I'm going to do, or what I'm allowed to do since I'm not physically located inside the United States at present. I won't sign with the `international' version of PGP 2.6, so perhaps I should start signing with gpg and be done with it. I think we finally got a clean BSDi build with gpg.

1 participants
0 comments

Re: shrink-window-if-larger-than-buffer stopped working 25 years, 2 months

SL Baur

Marc Aurel <4-tea-2(a)bong.saar.de> writes in xemacs-beta(a)xemacs.org: > In XEmacs 21.2 "Boreas" [Lucid] (i386-bong-linux, Mule) of Sun Feb 7 1999 on bong > configured using `configure i386-bong-linux --debug=no --error-checking=none --memory-usage-stats=no '--cflags=-g -O4 -malign-jumps=2 -malign-loops=2 -malign-functions=2 -finline-functions' --with-mule=yes' > Please describe exactly what actions triggered the bug > and the precise symptoms of the bug: > I built and installed XEmacs 21.2.10, updated all installed packages (incl. > removing some that seemed unimportant for me) and now shrink-window-if- > larger-than-buffer doesn't work anymore. It doesn't produce an error > message, calling it by M-x shrink-window-if-larger-than-buffer or C-x - > simply has no action. This behaviour is reproducible here, even with > -vanilla. Please let me know what further info I can provide, thanks! I cannot reproduce this in 21.0. Is this a 21.2-specific problem?

1 participants
0 comments

Re: Package warnings when starting up 21.2.10 25 years, 2 months

John Mignault

>>>>> "Dmitry" == Dmitry Yaitskov <dimas(a)home.com> writes: Dmitry> The path looks wrong (a patch for package-admin.el fixing Dmitry> this was posted to the list a couple days ago). Could be Dmitry> that the package in question got installed twice - once in Dmitry> the proper directory, and then in its "man" subdir. This was it exactly, Dmitry. Thanks. I'll find the patch and apply it. j -- #!/usr/bin/perl $dot="\x2e";$lt="\x3c";$gt="\x3e";$at="\x40"; print "J Mignault ${lt}jbm${at}panix${dot}com${gt}\n"; $wright = qq(After eating, do amphibians have to wait one hour before getting out of the water?);

1 participants
0 comments

Re: [Failure] 21.2b10 sparc-sun-solaris2.5.1 25 years, 2 months

Didier Verna

Martin Buchholz writes: Martin> Please someone fix the shlib stuff. I've already sent a patch against aclocal.m4 for this problem. -- / / _ _ 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: Package warnings when starting up 21.2.10 25 years, 2 months

Dmitry Yaitskov

Gleb Arshinov <gleb(a)broadbase.com> writes: > >>>>> "John" == John Mignault <jbm(a)panix.com> writes: > > John> The only thing i"ve noticed so far is this warning when > John> starting up XEmacs: > > John> (1) (warning/warning) Autoload error in: > John> /usr/local/lib/xemacs/packages/man/lisp/strokes/auto-autoloads: ^^^^^ The path looks wrong (a patch for package-admin.el fixing this was posted to the list a couple days ago). Could be that the package in question got installed twice - once in the proper directory, and then in its "man" subdir. > John> Already loaded > > John> How exactly should I go about tracking down something like > John> this? I looked in the file mentioned and nothing jumped out > John> as an obvious suspect... Suggestions for appropriate parts > John> of the docs? Am I just indescribably dense? :) > > I've seen the same problem, except with a different package. For me > the cause was that lisp/[packagename]/auto-autoloads was already > loaded when dumping. I deleted the auto-autoloads.elc, then rebuilt, > which fixed the problem. I did not have good sence to do further > testing to narrow down the cause. > > Gleb > > PS The package in question was the last one I had installed, so that > may be important.

1 participants
0 comments

Re: Odd color behavior with 21.0.63 25 years, 2 months

Jan Vroonhof

"Kevin Oberman" <oberman(a)es.net> writes: > color on my screen when XEmacs starts (something that was not the case > at one time), but it switches to grey75 (or something close) as soon > as I change the selected font using the Options->Font menu. I am afraid the behaviour you describe is currently designed in. The Font menu uses custom now. Custom (unfortunately) cannot ADD to settings. Either you do all your settings using X resources/elisp or you have do to all your settings using customize. The solution your case would be to either 1. Not use the font menu, do it all by hand. 2. Specify the color using customize-face on 'default. Jan

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