January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Tor Arntsen

On Jan 4, 11:52, SL Baur wrote: [...] >cvs -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout xemacs -d xemacs-21.0 [...] >cvs -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout \ > -rrelease-21-2 xemacs -d xemacs-21.2 > >for the experimental 21.2 sources. This sequence will use the >subdirectory xemacs-21.0/ to store the stable version and xemacs-21.2 The final -d xemacs-21.2 has to be put *before* the module name (xemacs), i.e. cvs -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout -d xemacs-21.0 xemacs or it won't work.. (it will first check out in 'xemacs' and then complain about the rest) - Tor

1 participants
0 comments

Re: 21.0 vs 21.2 25 years, 3 months

Richard Coleman

> Peter> If I want to track the 21.0 sources, must I `cvs update -R > Peter> release-21-0' in said directory? ... > > If you wish to track both versions use two XEmacs source trees. Check > out one with the default branch, eg. something like Ugh. Two source trees? I thought one of the purposes of CVS was to have a unified version of the source. Why is this? Also, what about adding tags like xemacs-current and xemacs-stable that would track these two branches without dealing with version numbers. Also, my understanding is that 21.0 is the main part of the tree and 21.2 is a branch. Is there any chance of eventually flipping this, so that the developmental sources are always the main line of the tree? -- Richard Coleman coleman(a)math.gatech.edu

1 participants
0 comments

Re: mailing list for commit messages 25 years, 3 months

SL Baur

Didier Verna <verna(a)inf.enst.fr> writes in xemacs-beta(a)xemacs.org: > SL Baur writes: sb> Richard Coleman <coleman(a)math.gatech.edu> writes in sb> xemacs-beta(a)xemacs.org: >>> Does XEmacs have a mailing list so we can see the CVS commit messages? sb> Yes. The mailing list name is `xemacs-cvs'. > I had asked this a while ago and seen no answer. That list has been up for a *long*[1] time. > Was there an announcement for this list? I presume so. Footnotes: [1] Since 2-May-1998.

1 participants
0 comments

Re: 21.0 vs 21.2 25 years, 3 months

SL Baur

Martin Buchholz <martin(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: >>>>>> "Peter" == Peter Bernard West <p.west(a)uq.net.au> writes: Peter> Martin Buchholz writes: >>> >>> The officially sanctioned way to get 21.2 via CVS is: >>> >>> cvs -z3 -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot checkout -R release-21-2 xemacs >>> >>> I changed the tag as well so that a simple `cvs update' will get the >>> latest CVS sources. This better not mean what I think it means. Peter> Does this mean that if I `cvs update' in an xemacs directory Peter> containing the 21.0.6 cvs sources, that they will be updated to the Peter> 21.2.8 (or whatever the current head of the branch is) sources? The release branch tag is sticky. Once you check out a branch, you can do `cvs update's in it to get updated versions. > No. It will be updated to the latest 21.0 sources. Peter> If I want to track the 21.0 sources, must I `cvs update -R Peter> release-21-0' in said directory? ... If you wish to track both versions use two XEmacs source trees. Check out one with the default branch, eg. something like cvs -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout xemacs -d xemacs-21.0 for the 21.0 (and soon-to-be) 21.1 sources. and cvs -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout \ -rrelease-21-2 xemacs -d xemacs-21.2 for the experimental 21.2 sources. This sequence will use the subdirectory xemacs-21.0/ to store the stable version and xemacs-21.2 to store the experimental version. You should then be able to run `cvs update' in each top-level XEmacs source directory to get future updates. > I haven't tried that, but I think it should work. Check the > version.sh file after your `cvs update' to make sure you got the > version you expected. Good advice.

1 participants
0 comments

Can somebody send me their startup.elc ? 25 years, 3 months

Didier Verna

Thanks. --didier

1 participants
0 comments

Re: irchat package 25 years, 3 months

SL Baur

Norbert Koch <n.koch(a)delta-ii.de> writes in xemacs-beta(a)xemacs.org: > I think, we should either remove the irchat package's entry from the > package index file or put it into the package directory. It's going back in sans US-unexportable encryption.

1 participants
0 comments

package-ui-add-site in 21.2+ 25 years, 3 months

Vin Shelton

Running an XEmacs 21.2 built from CVS, with packages built from CVS, I'm getting the following error when I attempt to add xemacs.org using Options/Manage Packages/Add Download Site Symbol's function definition is void: package-ui-add-site This yielded the following backtrace: Signaling: (void-function package-ui-add-site) (package-ui-add-site (quote ("ftp.xemacs.org" "pub/xemacs/packages"))) ) eval((package-ui-add-site (quote ("ftp.xemacs.org" "pub/xemacs/packages")))) Today is the first time I have built the xemacs-packages from scratch, so it's certainly possible I screwed something up, but I notice that 21.0 (using the same xemacs-packages) does not have this problem. vin

2 participants
1 comments

irchat package 25 years, 3 months

Norbert Koch

Hi, I think, we should either remove the irchat package's entry from the package index file or put it into the package directory. At the moment you'll get an error on trying to update this package, because file and directory contents are not in sync. -norbert. -- Somebody should have told him that being a physicist, on a planet where the smartest animals hate being alive so much, means never having to say you're sorry.

1 participants
0 comments

Re: XEmacs 21 /vs./ my keyboard: I want my DEL back 25 years, 3 months

Richard Coleman

> How about a little historical reminder? When people were looking for > Emacs on small machines like DOS, Coherent, Atari ST, and QNX, > MicroEmacs was the most widely used and accepted alternative. > MicroEmacs eventually lost a large number of users to MicroGNUEmacs > and Elle, at least partly because the MicroEmacs developers kept > diddling with the keyboard layout. I finally threw out MicroEmacs > when it became impossible to reconfigure MicroEmacs to the old > familiar layout. > > The lesson, don't diddle with the default keyboard behaviour, > especially not in such a way as to make it difficult for people to get > the old familiar behaviour. Then again, maybe those programs fell out of favor due to the author(s) not responding to the wishes of its user base. I doubt the reason for a program's decline can be attributed only to changes in keybindings. A program must either evolve or become a legacy product. Personally, I think making DEL delete forward like C-d is the right thing to do. But as long as it is configurable, I could care less. It always surprises me how the smallest changes provoke the most debate. I see this all the time on the FreeBSD mailing lists. If someone wants to rewrite the kernel from scratch, no one says a word, but if someone wants to add an option to "ls", it provokes weeks of debate. -- Richard Coleman coleman(a)math.gatech.edu

1 participants
0 comments

Re: [ERROR] pui-list-packages, file permissions 25 years, 3 months

Norbert Koch

Martin Buchholz <martin(a)xemacs.org> writes: > >>>>> "N" == Norbert Koch <n.koch(a)delta-ii.de> writes: > > N> Can someone please change the permissions? Thanks :-) > > Done. Hmm, am I looking in the wrong place? I still get the error and see (in /ftp.xemacs.org:/pub/xemacs/packages) -rw------- 1 6112 6199 46273 Dec 31 08:42 package-index-1998-12-31.pgp lrwxrwxrwx 1 6112 6199 28 Dec 31 08:42 package-index.LATEST.pgp -> package-index-1998-12-31.pgp -norbert

2 participants
1 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 January 1999