December 1999 - XEmacs-Beta - XEmacs Mailing List Archives

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

John S. J. Anderson

>>>>> "Olivier" == Olivier Galibert <galibert(a)xemacs.org> writes: >> Letting the web people know which ones are broken might result in >> them becoming un-broken sooner than not... Olivier> Since you seem to have a problem in this area, a friend of Olivier> mine just wrote a script for you to use. It requires another Olivier> of his scripts to run, dead link check, which you can find on Olivier> http://dlc.sourceforge.net/. Thanks, and thanks to your friend. I elected to use Linbot instead, as I'm more familiar with that. It's now installed and configured for the web maintainers to use; drop me a line privately if you need it and can't find it. Once I suss out the correct options, I'll get it set up as a cron job, so that the reports will update automatically. Of course, the dead links still aren't fixed, but I have now determined which ones they are (which presumably includes the ones that started this thread, at least as a subset). john. -- ------------------------------------------------------------------------ John S Jacobs Anderson \ <URL:http://www.xemacs.org> You'll have to pry my Emacs from my cold \ jacobs(a)xemacs.org dead oversized control-pressing left pinky finger. -- Randal L. Schwartz

1 participants
0 comments

Re: Weird byte-compiler tests 24 years, 11 months

Hrvoje Niksic

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > Hrvoje> ObXEmacs: what Perl mode are people actually *using*? The > Hrvoje> cperl mode we ship behaves horribly. > > I switched to use Ilya's latest version of cperl-mode like a few > other people on the list have. Does that work? Where do I get it?

1 participants
0 comments

Re: Weird byte-compiler tests 24 years, 11 months

Adrian Aichner

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)iskon.hr> writes: Hrvoje> Adrian Aichner <aichner(a)ecf.teradyne.com> writes: >> Until Hrvoje> that's done I'll just do everything using perl modules Hrvoje> instead >> of spending my time re-inventing the Hrvoje> perl^H^H^H^Hwheel :-) Hrvoje> It's not like Perl is the be-all end-all, you know. If Hrvoje> you look around, you should find a Python module or two. Hrvoje> Anyway, good luck with your Perling. I know *I* need it. Hrvoje> ObXEmacs: what Perl mode are people actually *using*? The Hrvoje> cperl mode we ship behaves horribly. I switched to use Ilya's latest version of cperl-mode like a few other people on the list have. Submitting a formal patch to XEmacs is on my (pretty long) todo list. Adrian

1 participants
0 comments

Re: Weird byte-compiler tests 24 years, 11 months

Hrvoje Niksic

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > Until that's done I'll just do everything using perl modules instead > of spending my time re-inventing the perl^H^H^H^Hwheel :-) It's not like Perl is the be-all end-all, you know. If you look around, you should find a Python module or two. Anyway, good luck with your Perling. I know *I* need it. ObXEmacs: what Perl mode are people actually *using*? The cperl mode we ship behaves horribly.

1 participants
0 comments

Re: Weird byte-compiler tests 24 years, 11 months

Adrian Aichner

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)iskon.hr> writes: Hrvoje> Martin Buchholz <martin(a)xemacs.org> writes: >> Here's a little perl that shows you which files in your workspace >> are modified: Hrvoje> I use `cvs diff' for that right now, but I guess this Hrvoje> would work too. Hrvoje> TODO: port your Perl scripts to Python. :-) Hi Hrvoje, the real killer TODO is to port ALL of CPAN to python. Until that's done I'll just do everything using perl modules instead of spending my time re-inventing the perl^H^H^H^Hwheel :-) Adrian

1 participants
0 comments

Re: Weird byte-compiler tests 24 years, 11 months

Hrvoje Niksic

Martin Buchholz <martin(a)xemacs.org> writes: > Here's a little perl that shows you which files in your workspace > are modified: I use `cvs diff' for that right now, but I guess this would work too. TODO: port your Perl scripts to Python. :-)

1 participants
0 comments

Re: Modules (was: Re: How about a feature freeze) 24 years, 11 months

Jan Vroonhof

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > No, but I think they are more or less orthogonal. I am all for > make concentrated push on the essentials, but you cannot simply trade > projects for another when the only time available is volunteer time. > > Even though I know one of the most useful contributions right now > XEmacs would be to work a complete weekend with the FSF and XEmacs Does anybody know whether forgetting-to-type-every-third-word-disorder is a known medical problem? Jan

2 participants
1 comments

Re: CVS hosed? tests/automated/base64-tests.el is gone! 24 years, 11 months

Hrvoje Niksic

Martin Buchholz <martin(a)xemacs.org> writes: > I edited the file in the CVS repository, changed all occurences of > NUL bytes with the string "\0" and renamed it to base64-tests.el in > the repository. This allows me to successfully run cvs update. > This file is all yours again, Hrvoje. Thanks a bunch! I've now committed the latest version to the repository.

1 participants
0 comments

Re: CVS hosed? tests/automated/base64-tests.el is gone! 24 years, 11 months

Hrvoje Niksic

Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: > After Martin´s fix for the Fmapconcat crashes I wanted to reenable the > test in base64-tests.el which Hrvoje had disabled some time ago, I haven't it. The base64-tests file has been broken in the repository for a long time, and I'm still waiting for someone to fix it. The problem was that that file used to have a raw-zero character embedded in it, which CVS apparently doesn't grok. Even worse, I can't find a way to fix the situation, even after having removed the offending character. If you want, I'll mail you a working copy of the file.

2 participants
1 comments

Re: CVS hosed? tests/automated/base64-tests.el is gone! 24 years, 11 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > > > Otherwise why don't we just remove the existing file and add a fresh > > > copy? > > > > I tried that. It didn't work. > > Did you make sure your removed it any reference to the original file > from your local repository as well? Did you do a fresh checkout > after the file was removed from CVS? Nope; I did something along the lines of: mv base64-tests.el foo cvs remove base64-tests.el cvs commit mv foo base64-tests.el cvs add base64-tests.el cvs commit Should I try something else? Or, you can try it yourself? Maybe we should organize a "remove base64-tests.el from CVS" contest, with Gnus tattoos as prizes. :-)

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 1999