January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Rick Campbell

Sorry for the noise. I've sent a couple of messages that didn't seem to make it through. I think I had a configuration problem at my end which is hopefully resolved now. Rick

1 participants
0 comments

sounnd-* packages problesm [was Re: Feedback on pui-list-packages] 25 years, 10 months

Jan Vroonhof

"Barry A. Warsaw" <bwarsaw(a)cnri.reston.va.us> writes: > And the *Packages* directory still shows those two packages as not > installed (and needing update). That is because the package still need to have a _pgk.el (and corresponding autoload.el) created so the package code will notice them, Could some of the package builders manage that before 21.0 release? Jan

1 participants
0 comments

Re: Building 21.0.60 on AIX 4.3.1 25 years, 10 months

Michael Sperber

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes in xemacs-beta(a)xemacs.org: >> My general stance is that it's a bad idea to cater to OS fuckage in >> configure, because it will alleviate pressure to get the actual bug >> fixed. sb> How are going to force Motif bugs to get fixed? As near as I can tell sb> Motif has pretty much always been broken in some way or another. Notwithstanding the general brokenness of Motif, this is really a problem with IBM's fucked-up distribution of it. At least in theory it's possible someone with a service contract will send a Problem Report to IBM, and with some luck, it will get fixed. Does anyone know why IBM insists on hacking and breaking MIT's X before they ship it with AIX? It doesn't seem they add much if any functionality, and the delays this incurs are impressive. They replaced X11R5 by X11R6 only like what, half a year ago? sb> Death to Motif. Good riddance to bad rubbish. I think it's a serious sb> mistake defaulting to Motif support. I like this idea a lot. Since this change would be trivial and not really affect anything we've tested, couldn't we make it so for 21.0? >> BTW: We still do need a note in PROBLEMS about AIX X libXt, don't we? sb> That would be good. Coming up. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Building 21.0.60 on AIX 4.3.1 25 years, 10 months

SL Baur

Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes in xemacs-beta(a)xemacs.org: >>>>>> "Valdis" == Valdis Kletnieks <Valdis.Kletnieks(a)vt.edu> writes: Valdis> [1 <text/plain; us-ascii (7bit)>] Valdis> On 05 Jan 1999 19:20:18 +0100, Michael Sperber [Mr. Preprocessor] said: >>> From the PROBLEMS file: >>> >>> ** AIX >>> *** On AIX 4.3, you must specify --with-dialogs=athena with configure Valdis> Until such time as we track down the actual problem here, would it make Valdis> sense for ./configure to default this, and to urinate all over the Valdis> user if they attempt to overrride it, since we *know* it won't work? > I *did* figure out what the problem is in a rough way: Motif pees all > over the data area with allocated storage. Lovely. > My general stance is that it's a bad idea to cater to OS fuckage in > configure, because it will alleviate pressure to get the actual bug > fixed. How are going to force Motif bugs to get fixed? As near as I can tell Motif has pretty much always been broken in some way or another. > But I know Steve has felt differently about this in the past. I'll > leave it to him. Death to Motif. Good riddance to bad rubbish. I think it's a serious mistake defaulting to Motif support. Valdis> I'm pretty sure that, unlike the 'xemacs -nw locks up' problem, this Valdis> one isn't a problem in the IBM X libraries, since I build against Valdis> the MIT X11R6.4 and *still* see it. I haven't looked to see if it's Valdis> an IBM xlc compiler fuckage (possibly), or if it's an actual XEmacs bug Valdis> (but why isn't it seen elsewhere?) > No, it's Motif. > BTW: We still do need a note in PROBLEMS about AIX X libXt, don't we? That would be good.

1 participants
0 comments

Re: Bug Report for XEmacs 20.4 25 years, 10 months

Martin Buchholz

>>>>> "SJT" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: SJT> The following patch is against a fresh CVS update (1999-01-04) of SJT> the mule/egg-its source package, version 1.13. SJT> 1999-01-04 YOKOTA Hiroshi <y5t0964(a)students.chiba-u.ac.jp> SJT> * egg.el: defvar (not defconst) some user parameters SJT> `egg:*fence-open*', `egg:*fence-close*', `egg:*fence-face*' I am applying this patch. Given how Japanese characters can get munged by the Net and by Martin, please check my work. Yokota-san, thank you for your contribution. Martin

1 participants
0 comments

Re: Building 21.0.60 on AIX 4.3.1 25 years, 10 months

Michael Sperber

>>>>> "David" == David Kropman <dkropman(a)truworths.co.za> writes: David> Hi have had several problems compiling xemacs on AIX 4.3.1 I have many David> different versions. The most success I have is with the version above. I David> now have the following problem that I hope somone will give me some help on! David> [ ... ] Using Motif dialog boxes. >From the PROBLEMS file: ** AIX *** On AIX 4.3, you must specify --with-dialogs=athena with configure -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

Feedback on pui-list-packages 25 years, 10 months

Barry A. Warsaw

First of all, the package stuff has come a *long* way since I looked at it last. pui-list-packages is very cool, and you guys deserve a round of kudos! Very easy to use, and it seems to work very well. 'Course I have a couple of suggestions, apologies if these have already been discussed. :-) - It would be nice if package-get-remote were set to point to ftp.xemacs.org by default. I had to set this before I could get anything working. - It seems that any error in unpacking a package stops the whole process. It would be better if the other packages could be installed and some indicator in the *Packages* buffer could be used to show there was a problem (you might change the colors to red for problem, yellow to be downloaded). As an example of this problem, I tried to install the irchat package, which I didn't have installed. XEmacs couldn't find the package on ftp.xemacs.org, and install just stopped. - It would be useful to include package sizes to know how much has to get downloaded. - It would be good to have a progressive indicator as things are getting installed. I thought for example xemacs-base had just hung, but (I think) it was just taking a long time. - I've had some problems installing a package which I had done some edits in, creating an RCS subdirectory. XEmacs complained that it couldn't find .../package/RCS and the install process just hung. I think that's it. Other than that, things look very good! Thanks, -Barry

1 participants
1 comments

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

Didier Verna

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. Was there an announcement for this list? If yes, I think it didn't reach me. -- / / _ _ 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

2 participants
1 comments

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

SL Baur

Richard Coleman <coleman(a)math.gatech.edu> writes in xemacs-beta(a)xemacs.org: > Does XEmacs have a mailing list so we can see the CVS commit > messages? Yes. The mailing list name is `xemacs-cvs'. Send an email message to <majordomo(a)xemacs.org> with the magic word `lists' in the body for a complete list of available mailing lists.

2 participants
1 comments

Re: xemacs & redhat 25 years, 10 months

SL Baur

Didier Verna <verna(a)inf.enst.fr> writes in xemacs-beta(a)xemacs.org: ... > If those programs are the same as in the GNU Emacs distribution, > they probably should be rpm'ized or debianized or whatever'ized as > standalone packages. Otherwise, at least for 2 of them, it's probably > better to let fall the `gnu' prefix, and why not, add an `xe' prefix, > like xedoit and xeserv ? Yuck! Nothing personal Didier, but Yuck! If there's something worse than the name `XEmacs', it's definitely the abbreviation `xe'.

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