August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [Success] XEmacs 21.1.4 "Arches", i386-pc-win32 25 years, 3 months

Adrian Aichner

>>>>> "Vin" == Vin Shelton <acs(a)xemacs.org> writes: Vin> Well, I have these patches in a mail folder, and using gnus Vin> it's very easy to extract the message-id. The message-id Vin> uniquely identifies the message, and we should be able to Vin> search the archive based on that string. I don't really want Vin> to have to go to the website every time I want to refer to a Vin> patch which I already have saved and ticked. I see. Yes this is very inconvenient. Jan and I were not able to find your cited message-id even though I do have that patch in my xemacs-patches nnml fail folder. Jan's patch in the archive contains these HTML comments:        This message-id agrees with the message in my xemacs-patches folder: > From: Jan Vroonhof <vroonhof(a)math.ethz.ch> > Subject: Fix for custom problems with italic face > To: xemacs-patches(a)xemacs.org > Cc: Adrian Aichner <aichner(a)ecf.teradyne.com> > Date: 07 Jul 1999 01:13:44 +0200 > Message-ID: <87hfnhxtg7.fsf(a)petteflet.dialup.ethz.ch> Would it be possible for the search engine to search these HTML comments also? Where the message-id you cited (Message-ID: <byaexc6i8w.fsf_-_(a)bolzano.math.ethz.ch>) came from remains a mystery. I couldn't find it in my xemacs-patches mail folder. Could it be that in my case gnus deleted the duplicate arriving via xemacs-patches because I had gotten it from Jan already via the CC. Does that sound right? But why do the message-ids in the archive and my mail folder agree then? Hmmh, seems like we are in dire need of a UXEPL[1] :-) Adrian Vin> Another option is for the mailinglist to add the archive URL to the Vin> message header. Vin> - vin Footnotes: [1] Uniform XEmacs Patch Locator.

2 participants
1 comments

emacs-build-time may be wrong in Win NT native build 25 years, 3 months

Adrian Aichner

After building XEmacs-21.1.6 a couple of times I finally figured out why emacs-build-time was consistenly reported incorrect. Output from nmake /f xemacs.mak distclean contains this: del *.exe d:\tmp\21.1\xemacs\src\xemacs.exe The process cannot access the file because it is being used by another process. This is not an error under the Windows NT [Adrian scratches his head to find the right word] Operating System. xemacs.exe is silently not removed. What I'm not sure of: Is xemacs.exe correctly rebuilt in such a case? It's modification time remains that of the previous build. Dumping however, does not report an error: Dumping from d:\tmp\21.1\xemacs\src\temacs.exe to d:\tmp\21.1\xemacs\src\xemacs.exe Thanks for any insight, Adrian

1 participants
0 comments

Re: XEmacs Build Report for XEmacs-21.1.6 25 years, 3 months

SL Baur

If it isn't working in 21.1 I am *furious*. It is supposed to work. Tsukamoto Tetsuo <czkmt(a)remus.dti.ne.jp> writes in xemacs-beta(a)xemacs.org: > Again, I have a question about the XEmacs 21.1 and the latest > mule-base package. > mule-base 1.32 contains changes that cause problems under XEmacs > 21.1. Even though this package appears under /pub/xemacs/packages > directory, it is not for the latest version of XEmacs 21.1. > Several users asked me why XEmacs 21.1 with mule-base 1.32 > complains max-lisp-eval-depth or something. Of course mule-base 1.31 > is O.K. > Is someone thinking of updating 21.1 for mule-base 1.32 ? If not, > please upload the mule-base that is good for XEmacs 21.1. > Thanks. > -- > Tsukamoto, Tetsuo

1 participants
0 comments

Re: xemacs size 25 years, 3 months

SL Baur

Adrian Aichner <aichner(a)ecf.teradyne.com> writes in xemacs-beta(a)xemacs.org: >>>>>> "Kyle" == Kyle Jones <kyle_jones(a)wonderworks.com> writes: Kyle> From the src directory Kyle> in the distribution run 'make run-temacs' and temacs will load > Just for the record: > This is not implemented in xemacs.mak for native WindowsNT. It needs to be.

1 participants
0 comments

Re: followup patch for 9907/msg00022.html for 21.1.6 25 years, 3 months

Adrian Aichner

>>>>> "Vin" == Vin Shelton <acs(a)xemacs.org> writes: Vin> Adrian, Vin> 21.1.6 is closed. The sources have been tagged and the tarballs Vin> have been cut. Your changes did not make it, but I can get your Vin> changes in 21.1.7. That's fine. I just meant 21.1 as opposed to 21.2. Vin> Clearly, I need to be more communicative than I have been in Vin> the past. I've been taking some shortcuts due to lack of Vin> time, but that's no excuse. There is no escape from xemacs-patches mailbox! ;-> Vin> Before the next release, after I have chosen all the likely Vin> candidate bugfixes, I will commit all the pending changes to Vin> CVS and then send a notice to xemacs-beta. This will give Vin> people a couple of days to lobby me for additional changes Vin> before a release. Sounds perfect. Vin> If there is sufficient demand, I can release 21.1.7 quickly - Vin> in a week or two. I don't see this as an urgent issue, I would just like 21.1 native Win32 to be able to produce info files without first installing makeinfo (which wasn´t trivial on WinNT when I looked. I succeeded, but only after patching (and subbmitting a patch for) sources). However, people will need to have to texinfo package installed. Perhaps I need to make that clear in xemacs.mak, when the info target fails? Regards, Adrian Vin> - vin

1 participants
0 comments

Re: followup patch for 9907/msg00022.html for 21.1.6 25 years, 3 months

Vin Shelton

Adrian, 21.1.6 is closed. The sources have been tagged and the tarballs have been cut. Your changes did not make it, but I can get your changes in 21.1.7. Clearly, I need to be more communicative than I have been in the past. I've been taking some shortcuts due to lack of time, but that's no excuse. Before the next release, after I have chosen all the likely candidate bugfixes, I will commit all the pending changes to CVS and then send a notice to xemacs-beta. This will give people a couple of days to lobby me for additional changes before a release. If there is sufficient demand, I can release 21.1.7 quickly - in a week or two. - vin

1 participants
0 comments

Re: Need help with `imenu-generic-expression' wrt menu splitting 25 years, 3 months

Jan Vroonhof

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > Is this a known limitation of imenu? > Does Emacs not suffer this problem? I do not know. However imenu is in need of a sync so why not have a look? Jan

1 participants
0 comments

XEmacs Build Report for XEmacs-21.1.6 25 years, 3 months

XEmacs Build 'Bot

Hello XEmacs beta testers. I am in the process of building XEmacs-21.1.6 for distribution. I have tested the attached configuration. Have a great day! Sincerely, The XEmacs Build 'Bot (revision 2) -- uname -a: Linux mithril 2.2.11 #1 SMP Thu Aug 12 00:21:53 EDT 1999 i686 unknown ./configure '--prefix=/home/acs/cvsroot' '--cflags=-O' '--with-mule' '--without-x11' '--debug=no' '--error-checking=none' XEmacs 21.1.6 "Big Bend" configured for `i686-pc-linux'. Where should the build process find the source code? /home/acs/cvsroot/xemacs-21.1 What installation prefix should install use? /home/acs/cvsroot What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -O Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? none Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits.

2 participants
1 comments

followup patch for 9907/msg00022.html for 21.1.6 25 years, 3 months

Adrian Aichner

>>>>> "APA" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: APA> Could the latter please be applied also? I already verified that it APA> still applies cleanly for 21.1.6. I will send another mini-patch APA> fixing a dependency of that patch from the check target which doesn't APA> make sense under 21.1. Here is the mini-patch, with nt/ChangeLog. Please apply this to 21.1.6 AFTER applying http://www.xemacs.org/list-archives/xemacs-patches/9907/msg00022.html which has following messag-id: > From: Adrian Aichner <aichner(a)ecf.teradyne.com> > Subject: Native info support and man cleanup for 21.1.4 "i386-pc-win32" > To: xemacs-patches(a)xemacs.org > Date: 10 Jul 1999 12:24:58 +0200 > Message-ID: <u7lo8ls3p.fsf(a)ecf.teradyne.com> Please advise whether this patch can still make it in. I have tested it with nmake /f xemacs.mak distclean nmake /f xemacs.mak install and it works fine. Regards, Adrian 1999-08-15 Adrian Aichner <aichner(a)ecf.teradyne.com> * xemacs.mak (SRCDIR): Add definition. (PROGNAME): Ditto. cd d:\tmp\21.1\xemacs\ diff -u nt/xemacs.mak.orig nt/xemacs.mak Compilation started at Sun Aug 15 13:51:37 1999 +0200 (W. Europe Daylight Time) --- nt/xemacs.mak.orig Sun Aug 15 13:43:38 1999 +++ nt/xemacs.mak Sun Aug 15 13:04:39 1999 ＠＠ -960,6 +960,8 ＠＠ rc xemacs.rc # Section handling info starts here +SRCDIR=..\src +PROGNAME=$(SRCDIR)\xemacs.exe MAKEINFO=$(PROGNAME) -no-site-file -no-init-file -batch -l texinfmt -f batch-texinfo-format MANDIR = $(XEMACS)\man Compilation exited abnormally with code 1 at Sun Aug 15 13:51:38

1 participants
0 comments

Re: XEmacs Build Report for XEmacs-21.1.6 25 years, 3 months

Justin Vallon

Justin Vallon <vallon(a)mindspring.com> writes: > "XEmacs Build 'Bot" <xemacs-dist(a)xemacs.org> writes: > > > Hello XEmacs beta testers. I am in the process of building > > XEmacs-21.1.6 for distribution. I have tested the attached > > configuration. Have a great day! > > 21.1.5 and 21.1.6? Never mind. [ 21.1.5 was mis-built and thrown out ] -- -Justin vallon(a)mindspring.com

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