April 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Crash (while t(all-hail-xemacs)) 24 years, 7 months

Jan Vroonhof

"Robin S. Socha" <robin(a)socha.net> writes: > Sound: > Compiling in support for sound (native). > Compiling in support for ESD (Enlightened Sound Daemon). Does it also happen if you compile without ESD support? To me it very much looks like you are bitten by the problem where libesd sets up timeout for some reason and the SIGARLM ends up in our signal handler. Jan

2 participants
1 comments

[comp.emacs.xemacs] Re: XEmacs 21.1-b46 pop3.el? 24 years, 7 months

Adrian Aichner

Torgny has located the problem. Thanks, Torgny! What is the right approach to fix this? Best regards, Adrian -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-115 D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

5 participants
9 comments

Adding goto-addr.el from Emacs to XEmacs? 24 years, 7 months

Alex Schroeder

Hi, I have an old copy of XEmacs here, 21.1 (patch 10) which comes without goto-addr.el. Is this still true for the latest XEmacs? I am writing a package which uses goto-addr. Currently the package just ignores errors when loading it. A little testing on my system shows, however, the goto-addr can be made to work: (require 'overlay) (load-file "/usr/local/share/emacs/20.7/lisp/goto-addr.el") (goto-address) This will add faces to URLs and mail address, and it will allow you to browse-url or send mail using C-c C-m. In Emacs 20.7 this is also possible using mouse-2. I'd be willing to make any necessary changes to goto-addr -- even if it is just a little snipplet of code at the beginning: (when (featurep 'xemacs) (require 'overlay)) I'll look at the keybindings, too. Eric Ding <ericding(a)alum.mit.edu>, the original author, writes: > quick answer from me, at least: I keep an eye on it, but haven't > touched it for years. :) So the FSF is responsible for maintaining > it now. I am sure that the current Emacs maintainer would not mind adding XEmacs compatibility to existing files. :) Alex. -- http://www.geocities.com/kensanata/ Coffee should be black as hell, strong as death and sweet as love. -- Turkish proverb

1 participants
0 comments

marking then searching 24 years, 7 months

Allen Walker

In GNU emacs, if I do a C-SPACE then C-s I get a mark from the current point to the point of my first search result. In XEMACS, it doesn't do that, the only highlighted region is the currently found character, not all the characters before that (from where I initiated my C-space). In GNU emacs this is extremely useful when defining powerful macros.. In XEMACS I assume this a bug or maybe there's on option to turn this on. Any help appreciated. -allen-

3 participants
2 comments

Re: Mule redisplay crash 24 years, 7 months

Mike FABIAN

Yoshiki Hayashi <yoshiki(a)xemacs.org> writes: > Mike Fabian <mike.fabian(a)gmx.de> writes: > > > > (defun delete-and-split () > > > (interactive) > > > (delete-other-windows) > > > (split-window)) > > > (split-window-vertically) > > > (insert "が") > > > (backward-char) > > > (redraw-frame) > > > (delete-and-split) > > > Fatal error: assertion failed, file /deb-huge/home/gunnar/src/XEmacs/xemacs/src/objects.h, line 143, RECORD_TYPEP (obj, &lrecord_font_instance) > > > > > > [... rest of backtrace see Gunnar's original message, > > > Message-ID: <874sdmtok3.fsf(a)eng.cam.ac.uk> ...] > > > > Gunnar offered the following patch, which I am using all the time > > since then and apply to every new release of XEmacs (21.1 and 21.2): > > Sorry for late answer but my time and expertise are limited. > I think this is a right patch but I'm not 100% sure because > I don't understand redisplay. > > The problem is, Fsplit_window incorrectly invalidates face > cache when splitted window has no parents. This doesn't > make sense because Fsplit_window only adds new modeline > between windows and scrolls window to make point visible. > They don't change any faces. Function and variable names > are very cryptic in these functions. I'll probably refactor > it when I have some more time. > > 2000-12-04 Yoshiki Hayashi <yoshiki(a)xemacs.org> > > * window.c (Fsplit_window): Don't invalidate face cache. Thank you very much, it seems to work OK now in XEmacs 21.2 (beta46) "Urania". -- Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian

1 participants
0 comments

Bug (or doc bug) with zero-length extents? 24 years, 7 months

Michael Toomim

;;; Note: I posted the following message a couple of days ago, but had an ;;; invalid return address and so haven't recieved a reply. My apologies ;;; go out to anyone who had mailed me an answer in vain! I have noticed xemacs' behaviour to be inconsistent with the documentation, when inserting text onto certain zero-length extents. According to the info xemacs lisp reference and comments in extents.c, insertion at a zero-length extent with the properties start-open and end-closed (like the extent (5, 5]) should go before the extent: ---- extents.c: "Insertion at the position of a zero-length extent ... goes before the extent if it is open-closed." Info - extent endpoints: "Insertion at the position of a zero-length extent ... goes before the extent if it has the `start-open' property " ---- Thus, for the above extent, if one inserts the text "###" at position 5 in the buffer, the documentation implies that the extent would change to (8, 8]. This doesn't happen. With xemacs version 21.1, patches 12 and 9, the extent instead expands to include the inserted text (like the extent [5, 5] does) -- causing the extent to change to (5, 8]. The following e-lisp code, according to the documentation, should insert "1234###56789" into the buffer, un-colored, with a zero-length extent before the 5. Instead, it creates an extent covering the "###", making those characters green. (save-excursion (goto-char 1) (insert "123456789\n") (let ((ext (make-extent 5 5))) (set-extent-properties ext '(start-open t end-closed t face green)) (goto-char 5) (insert "###") (message "The extent is now %S" ext))) The more recent stable versions of xemacs don't seem to mention any fixes of this nature. Can anyone verify this on a new release? Is this a true xemacs bug (or a documentation bug?)? Thank you, Michael Toomim

3 participants
5 comments

Crash on windows at 2043 AD 24 years, 7 months

Nickolay Pakoulin

Today I have experienced a number of crashes in icq2000beta and Xemacs-21.2.45 on windows. Finally, I found the cause -- my Win2000 (with SP1) has set the date to 3 Apr 2043 (first of April joke?). The test case is (current-time-string '(35273 29735 377000)) According to debugger in Visual Studio, the error "Access Violation" occured in the body of `current-time-string' (editfns.c, 1254) when it tries to determine the length of the string that was returned by `ctime': ------------------------------------------------------------------------------- /* ctime is documented as always returning a "\n\0"-terminated 26-byte American time string, but let's be careful anyways. */ for (len = 0; the_ctime[len] != '\n' && the_ctime[len] != '\0'; len++) ; ------------------------------------------------------------------------------- The problem is that in this case `lisp_to_time' fails to convert lisp representation of time to a value of time_t type. `ctime' is called with pointer to -1 and returns an empty string "". Thus the supposition in comment does not hold. I'm not shure how to handle this exceptional situation and it seems a long way till it really hurts. Nick.

5 participants
4 comments

pre-command-hook error with highlighted paren matching and searching 24 years, 7 months

Wes Hardaker

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.2 (beta43) "Terspichore" [Lucid] (i686-pc-linux, Mule) of Wed Feb 7 2001 on wanderer.hardakers.net configured using `configure --dynamic --without-toolbars --without-dialogs --with-pop --error-checking=none --with-modules --with-mule' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: It's taken me forever to figure out exactly what key strokes I hit to reproduce this. Basically, it comes down to this: Turn one paren highlighting: (require 'paren) (paren-set-mode 'sexp) Then, do a search (C-s) for something that doesn't exist (say, "xyzzy"). Hit return, escape or c-g (ie, stop the search). Then hit C-s again, followed by C-s to repeat the last search. Now, hit C-a (beginning of line) and you'll get the following back trace: Signaling: (wrong-type-argument integer-or-marker-p nil) goto-char(nil) (progn (goto-char (cdr isearch-region)) (push-mark (car isearch-region) nil t)) (and isearch-region (progn (goto-char ...) (push-mark ... nil t))) (unwind-protect (and isearch-region (progn ... ...)) (setq isearch-region nil) (remove-hook (quote pre-command-hook) (quote isearch-pre-pre-command-hook))) isearch-activate-region-on-exit() run-hooks(isearch-activate-region-on-exit) isearch-done() isearch-pre-command-hook() Wheeeee... Now, to make matters worse, the paren highlinghting matching is broken and in a way that it highlights new paren groups, but fails to unhighlight them after you move the cursor away from the matching parens. Recent keystrokes: C-x C-s C-s C-s C-g C-g C-n C-n C-x C-f v a c TAB c RET C-s < < < C-a C-g C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-p C-x 1 C-SPC C-n C-n C-n C-n C-n C-w C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-SPC C-n C-w C-x C-s C-x 4 b RET C-x o C-s C-s C-a f8 C-s C-s C-a C-g C-g C-s C-s C-g C-g f8 C-s C-s C-s C-g C-g C-g C-g C-g C-s C-s C-a C-g C-g C-g f8 misc-user Recent messages (most recent first): Welcome to flyspell. Use M-tab or Mouse-2 to correct words. Welcome to flyspell. Use M-tab or Mouse-2 to correct words. Loading emacsbug...done Loading emacsbug... Paren mode is sexp Paren mode is OFF Quit Quit Quit Quit -- "Ninjas aren't dangerous. They're more afraid of you than you are of them."

1 participants
0 comments

Alt key 24 years, 7 months

Pimenov Yuri

Greetings! my xemacs (last beta) don't recognize Alt key at all! it's echoes "A-x not defined"... this problem doesn't happen with XEmacs 21.1 i'm using cvs KDE, XFree86 4.0.3 with XKB extension on (russian layout). PS. LeftAlt is defined to Meta in XF86Config... thanks in advance. Yuri Pimenov

2 participants
3 comments

Duplicate menubar accelerators 24 years, 7 months

Hrvoje Niksic

I've just noticed that the accelerators in the menubar are duplicated. Pressing Alt+M opens the "Cmds" menu; however, there is no way to get "Message" and "MML". Is it a bug or an oversight?

1 participants
0 comments

2025

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 April 2001