March 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: ChangeLog wierdness 25 years, 9 months

Colin Rafferty

SL Baur writes: > Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: >> 2) Font-locking of ChangeLog's from C-x C-f is much faster than reverting a >> ChangeLog buffer that has been changed externally. >> Does anyone esle see this? > Yes, but not with ChangeLogs in specific. Anything font-locked takes > longer to be font-locked after a revert because it appears to be doing > it twice. I thought I fixed this at some point, but it does not > appear to be working optimally now. If you use lazy-shot, you will not see this, since it stops font-lock from doing anything. It implicitly makes sure that fontification happens at most once. Of course, this is still a problem for XEmacs in general. -- Colin

1 participants
0 comments

Re: [Failure] XEmacs 21.2-b11 "Calliope", i586-pc-win32 25 years, 9 months

Adrian Aichner

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> At 01:57 PM 3/2/99 +0900, you wrote: >> Dmitry Yaitskov <dimas(a)home.com> writes in xemacs-beta(a)xemacs.org: >> >>> Adrian Aichner <aichner(a)ecf.teradyne.com> spake thusly: >>>> Hmmh, any clues? 21.2b10 built just fine, now this... >>>> >>>> <lines deleted by Adrian> >>>> Loading loaddefs.el... >>>> Loading dumped-lisp.el... >>>> Loading site-load.el... >>>> >>>> Bootstrapping from temacs...*** Error in XEmacs initialization >>>> (error "Can't add consoles in -batch mode") >>>> *** Backtrace >>>> really-early-error-handler((error "Can't add consoles in -batch mode")) >>>> *** Killing XEmacs >>>> NMAKE : fatal error U1077: '..\src\temacs.exe' : return code Andy> '0xffffffff' >>>> Stop. >>>> >>>> Compilation exited abnormally with code 2 at Mon Mar 01 18:04:08 >> >>> Extracting the xemacs-21.2.11-elc.tar.gz into the source tree fixes >>> that. Dunno if this is the way it should be. If it is, the error >>> messages could be more specific I think. >> >> It sounds like a bug that causes you not to be able to run temacs. >> Try removing a single .elc, like lisp/subr.elc, and rebuilding. You >> should get the same error. >> >> Is `make run-temacs' implemented on the MS Windows port? Andy> It is under cygwin Not under Windows NT, though (nt\xemacs.mak). Adrian Andy> andy -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

2 participants
1 comments

Re: rambling again 25 years, 9 months

Michael Sperber

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: Hrvoje> [... gc problems ...] >> This is only an issue if: >> >> - you insist on shared address spaces Hrvoje> I'm not sure I understand you here. My point is that if you store a Hrvoje> Python object in an Elisp data structure, you would like that object Hrvoje> not to be gc'ed away by Python. And vice versa. This is what "shared address spaces means". It's not necessary for communication between Python and Elisp --- you can just copy things >From one address space to another. This is what happens when you use COM or CORBA. Sure it's somewhat restrictive, but it causes way less trouble. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Distribution Build Report for XEmacs-21.0.64 25 years, 9 months

SL Baur

Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: ... > Well my opinion is, as always, that it will never be perfect so > just ship it :) How about a deadline of next saturday :) (only half > joking) I think I'll wait until the end of the month and release it during the Mule Symposium. Then we can have a real release party ...

1 participants
0 comments

The latest w3 package is hosed 25 years, 9 months

SL Baur

I'll upload a fixed version before I leave the lab tonight.

1 participants
0 comments

Re: rambling again 25 years, 9 months

Hrvoje Niksic

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: [... gc problems ...] > This is only an issue if: > > - you insist on shared address spaces I'm not sure I understand you here. My point is that if you store a Python object in an Elisp data structure, you would like that object not to be gc'ed away by Python. And vice versa. I know the Perl extension had that problem last time I looked at it.

1 participants
0 comments

Re: rambling again 25 years, 9 months

Michael Sperber

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Neal Becker <nbecker(a)fred.net> writes: >> The thought occurs - it's easy to embed a python interpreter into >> any C program. Emacs is a C program. I wonder if that would be >> useful? I suppose you'd have to make wrappers to interface the >> elisp with python if it was to be really useful. Hrvoje> One big problem with such embedding is that both Emacs and Python use Hrvoje> garbage collecting. To avoid memory leaks, you would have to make Hrvoje> Emacs increase refcounts of Python object, and make Python an Hrvoje> alternative "root of accessibility" for Emacs' mark-and-sweep. I'm Hrvoje> not sure if this is doable. This is only an issue if: - you insist on shared address spaces - one of the two substrates uses conservative GC, and the other does not I think Neal is talking about adding Python to XEmacs rather than replacing the substrate---with separate address spaces, this is definitely doable. Given the general slowness of both Python and Elisp, I doubt that the performance hit you'd get from copying would be significant. I have general doubts about the usefulness of this, but that's beside the point here. The Right Way to implement this, though, is to support CORBA or COM in XEmacs and be done with it. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: ChangeLog wierdness 25 years, 9 months

SL Baur

Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > 1) Edit a changelog, select some text, hit M-w, then C-x C-f and get > another ChangeLog, do C-y, I get part of the path yanked instead of the > text I selected. Did you cut & paste into the minibuffer to spell out the file name when you were doing C-x C-f? That's the only way I was able to duplicate it. I think that's a feature. > 2) Font-locking of ChangeLog's from C-x C-f is much faster than reverting a > ChangeLog buffer that has been changed externally. > Does anyone esle see this? Yes, but not with ChangeLogs in specific. Anything font-locked takes longer to be font-locked after a revert because it appears to be doing it twice. I thought I fixed this at some point, but it does not appear to be working optimally now.

2 participants
1 comments

Re: [Failure] XEmacs 21.2-b11 "Calliope", i586-pc-win32 25 years, 9 months

SL Baur

Dmitry Yaitskov <dimas(a)home.com> writes in xemacs-beta(a)xemacs.org: > Adrian Aichner <aichner(a)ecf.teradyne.com> spake thusly: >> Hmmh, any clues? 21.2b10 built just fine, now this... >> >> <lines deleted by Adrian> >> Loading loaddefs.el... >> Loading dumped-lisp.el... >> Loading site-load.el... >> >> Bootstrapping from temacs...*** Error in XEmacs initialization >> (error "Can't add consoles in -batch mode") >> *** Backtrace >> really-early-error-handler((error "Can't add consoles in -batch mode")) >> *** Killing XEmacs >> NMAKE : fatal error U1077: '..\src\temacs.exe' : return code '0xffffffff' >> Stop. >> >> Compilation exited abnormally with code 2 at Mon Mar 01 18:04:08 > Extracting the xemacs-21.2.11-elc.tar.gz into the source tree fixes > that. Dunno if this is the way it should be. If it is, the error > messages could be more specific I think. It sounds like a bug that causes you not to be able to run temacs. Try removing a single .elc, like lisp/subr.elc, and rebuilding. You should get the same error. Is `make run-temacs' implemented on the MS Windows port?

2 participants
1 comments

Re: Distribution Build Report for XEmacs-21.0.64 25 years, 9 months

SL Baur

Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > At 10:10 AM 3/1/99 -0800, Steven Baur wrote: >> Greetings XEmacs beta testers. I am in the process of building the next >> distribution of XEmacs 21.0. I have tested the attached >> configuration. > So how close are we to a real release? I don't know. Close. I'm beginning to think that the only way to get this out is to set a hard deadline, release whatever we have at that point and fix problems as they arise in 21.1.

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