XEmacs-Beta January 2000

xemacs-beta@xemacs.org

95 participants
438 discussions

Re: Solarys 2.7 21.2.25 crash 24 years, 3 months

Raymond Toy

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> --=====================_946465045==_ Andy> Content-Type: text/plain; charset="us-ascii" Andy> At 03:31 PM 12/28/99 -0500, Raymond Toy wrote: >> >> For the first time in a while, I had enabled the gutter tabs. I was >> trying to compose a mail via VM when it crashed. I'm not exactly sure >> when it happened, because I went off and did something else because I >> thought it was swapping but xemacs was really dumping 100 MB of >> core. :-) Andy> Hi Ray, Andy> Can you see if this makes any difference. Thanks, I'll give it a try. Ray

1 participants
0 comments

[ESD] More... 24 years, 3 months

Karl M. Hegbloom

I think you'll also have to have `ESD_NO_SPAWN=1' in your environment for my crash recipe to work.

1 participants
0 comments

[ESD; Crash] assert: signal.c, line 340, async_timer_suppress_count > 0 24 years, 3 months

Karl M. Hegbloom

This happens if the ESD is not running. I think what happened is that I'd logged into `gdm' as root, and it changed the ownership of the /tmp/.esd/socket to root.root. So when I logged in as myself (or on the console without ESD running) `esd' would not start; it says it cannot open the socket. (I rm'd the socket dir, and then it started, setting the socket karlheg.karlheg.) To repeat: Build an XEmacs with `esd' support. Log in on the console, or into X, _but_do_not_start_ `esd'. Start `xemacs -vanilla -f load-default-sounds', then push `C-g', `C-x lsdkfj [TAB]', or anything that would play a noise. I have not looked at the code... I'm too busy with other studies right now. I guess it ought to be able to handle `esd' not being there, huh? Hope it's not hard to fix.

1 participants
0 comments

Re: Problem with directory name in CVS checkout. 24 years, 3 months

Tor Arntsen

On May 25, 3:13, Martin Buchholz wrote: >I've wanted to fix this myself for a long time, and I've now gone >ahead and done that. Please send me comments on the new >http://cvs.emacs.org. xemacs >Jareth: regarding putting `update -Pd' in ~/.cvsrc, I have done this >for a year now without any problems. I thought `-A' is the argument >that removes sticky tags. Yes. >Some parts of the new page may be controversial. Page looks good to me. >Martin -Tor

1 participants
0 comments

Re: Problem with directory name in CVS checkout. 24 years, 3 months

Vin Shelton

>>>>> On Sat, 01 Jan 2000 , Martin Buchholz <martin(a)xemacs.org> said: Martin> I've wanted to fix this myself for a long time, and I've now Martin> gone ahead and done that. Please send me comments on the new Martin> http://cvs.emacs.org. Thank you. Martin> Jareth: regarding putting `update -Pd' in ~/.cvsrc, I have done this Martin> for a year now without any problems. I, too, have had 'update -Pd' in my ~/.cvsrc for a long time without difficulty. Martin> Some parts of the new page may be controversial. I find nothing under the heading "Quick Start Guide" to be either wrong or controversial. I guess you're referring to the sentences quoted below, which I think are an accurate reflection of the consensus of sentiments of the list members. It is now recognized that it was a mistake to have unstable development on a branch, while the stable tree is on the CVS trunk (no branch). So the above information is likely to change soon. I also think it's an extremely useful warning that things may change in the near future. - vin

1 participants
0 comments

Re: Problem with directory name in CVS checkout. 24 years, 3 months

Lloyd Zusman

Martin Buchholz <martin(a)xemacs.org> writes: > >>>>> "LZ" == Lloyd Zusman <ljz(a)asfast.com> writes: > > LZ> I have just recently subscribed to this mailing list after having > LZ> tried to download the current CVS tree for XEmacs. After a proper > LZ> CVS login, I issued the following command: > > LZ> cvs -z3 -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot checkout > LZ> XEmacs > > There is no CVS module named 'XEmacs'. All the XEmacs-related modules > happen to be in a directory named 'XEmacs', so your command worked > accidentally. > > To get the latest xemacs-21.2 from CVS, do: > > cvs -z3 -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot checkout -d > xemacs-21.2 -r release-21-2 xemacs Aha! Yes, that's working. Thanks. And now, it would probably be good if someone updated the instructions on http://cvs.emacs.org to reflect this info. > [ ... ] > > LZ> protocol error: directory > LZ> '/usr/CVSrooy/XEmacs/xemacs-19/lisp/custom' > LZ> not within root '/usr/CVSroot' > > LZ> It appears as if someone typed a "y" instead of "t" in "CVSroot" > LZ> somewhere within the CVS tree. > > I can't find a `CVSrooy' anywhere in the master repository. A random > bit got flipped somewhere? Could be ... ??? But I think it's somewhere in the CVS tree because I ran the command several times with the "t" and not the "y", but I kept getting this result. Oh well ... no big deal. All's well that ends well. Thanks again. -- Lloyd Zusman ljz(a)asfast.com

2 participants
1 comments

Problem with directory name in CVS checkout. 24 years, 3 months

Lloyd Zusman

I have just recently subscribed to this mailing list after having tried to download the current CVS tree for XEmacs. After a proper CVS login, I issued the following command: cvs -z3 -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot checkout XEmacs Everything proceeded wonderfully while hundreds of files downloaded to my machine. And then, I received the following error message (which I'm wrapping here): protocol error: directory '/usr/CVSrooy/XEmacs/xemacs-19/lisp/custom' not within root '/usr/CVSroot' It appears as if someone typed a "y" instead of "t" in "CVSroot" somewhere within the CVS tree. Is there anything I can do on my side to compensate for this? If not, is there anything that one of you folks could do to fix this? Thanks in advance. -- Lloyd Zusman ljz(a)asfast.com God bless you.

2 participants
1 comments

`yes-or-no-p-dialog-box' crash - Aborts. 24 years, 3 months

Karl M. Hegbloom

To repeat: Build similar to mine (Installation file attached along with `ldd' output.) then run `(yes-or-no-p-dialog-box "Yes or No")' in the *scratch* buffer. When I click on [Yes], [No] or [Cancel], the button presses, but XEmacs does not respond. When I click the [X] in the WM frame, it aborts. Here's the stack dump.

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 2000