November 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: GC crash on 21.2.37 (Was Re: GC crash with 21.2.36 on Solaris 2.7) 24 years

Gunnar Evermann

Olivier Galibert <galibert(a)pobox.com> writes: > On Thu, Nov 16, 2000 at 01:24:04PM +0000, Gunnar Evermann wrote: > > Yes, that's what I realised after writing the question and meant by > > "Hm, I guess it is". We should automatically check whether we always > > do this. Maybe in debug_gcpro(). > > Tricky. There are a number of gcpros done on already instanciated > lisp objects, and nothing looks more like a valid lisp_object than > random garbage. You can't even test for alignment since the lower > bits encode the type information for integers and chars. Yes, you are right. Maybe Jan's old idea of using C++ and explicit constructor and destructor methods for LispObject would work. We could just inintialise LispObjects to NULL in the constructor. Then we can check in GCPRO (giving some false positives as they only need to hold real LispObjects when the GC actually happens). Alternatively we could have a special function that is always called when a GC could happen (like always_gc) and then checks the gcprolist for NULLs. Gunnar

2 participants
1 comments

Andy, please look at this code: 24 years

Martin Buchholz

In lwlib/lwlib-Xlw.c:xlw_update_one_widget, we have #ifdef LWLIB_MENUBARS_LUCID else if (class == xlwMenuWidgetClass) { XlwMenuWidget mw; Arg al [1]; if (XtIsShell (widget)) mw = (XlwMenuWidget)((CompositeWidget)widget)->composite.children [0]; else mw = (XlwMenuWidget)widget; XtSetArg (al [0], XtNmenu, val); XtSetValues (widget, al, 1); } #endif Note how the code carefully creates a mw widget, and then ignores it. Perhaps the XtSetValues call should be XtSetValues (mw, al, 1);

4 participants
4 comments

Xemacs Mule + koi8 fonts question. 24 years

Nickolay Pakoulin

This question is pretty frequent in russian lists: How to make XEmacs use koi8-r fonts instead of iso8859-5 fonts? The problem is that there are many nice looking koi8-r fonts but only few 8859-5 fonts. And many people complain that they have to install 8859-5 fonts for XEmacs solely while all other apps do well with koi8. Is there easy and straightforward way to use koi8-r fonts in Mule xemacs? TIA, Nick.

3 participants
3 comments

Gutter vs VM 24 years

Philip Aston

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 (beta37) "Pan" [Lucid] (i686-pc-cygwin) of Sat Nov 18 2000 on PASTON configured using `configure -with-png -with-xpm --site-includes=/usr/local/include --with-dragndrop --cflags '-g -O'' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: xemacs -q M-x vm Get stack trace below. Repeat M-x vm and frame is set up fine. Signaling: (error "Must be string or vector" #<mswindows-frame "emacs" 0x34cd>) check-valid-instantiator(#<mswindows-frame "emacs" 0x34cd> image) canonicalize-spec(#<mswindows-frame "emacs" 0x34cd> image nil) byte-code("..." [spec-list nil result rest noerror throw cann-spec-list t signal error "Invalid list format" canonicalize-spec specifier-type res2] 5) canonicalize-spec-list((#<mswindows-frame "emacs" 0x34cd> . [tab-control :descriptor "Buffers" :face buffers-tab :orientation top :pixel-width (gutter-pixel-width) :items nil]) image) set-specifier(#<image-specifier global=<unspecified> fallback=((nil . ...)) 0x2420> [tab-control :descriptor "Buffers" :face buffers-tab :orientation top :pixel-width (gutter-pixel-width) :items nil] #<mswindows-frame "emacs" 0x34cd> nil nil) set-glyph-property(#<glyph (buffer) #<image-specifier global=<unspecified> fallback=(...) 0x2420>0x241f> image [tab-control :descriptor "Buffers" :face buffers-tab :orientation top :pixel-width (gutter-pixel-width) :items nil] #<mswindows-frame "emacs" 0x34cd> nil nil) set-glyph-image(#<glyph (buffer) #<image-specifier global=<unspecified> fallback=(...) 0x2420>0x241f> [tab-control :descriptor "Buffers" :face buffers-tab :orientation top :pixel-width (gutter-pixel-width) :items nil] #<mswindows-frame "emacs" 0x34cd>) update-tab-in-gutter(#<mswindows-frame "emacs" 0x34cd> t) #<compiled-function (frame) "...(8)" [frame gutter-buffers-tab update-tab-in-gutter t] 3>(#<mswindows-frame "emacs" 0x34cd>) make-frame(((width . 80) (top . 50) (left . 140))) vm-goto-new-frame(primary-folder folder) apply(vm-goto-new-frame (primary-folder folder)) <snip> Recent keystrokes: M-x v m RET misc-user Recent messages (most recent first): Parsing /home/philipa/.mailrc... Loading mail-abbrevs...done Loading mail-abbrevs... Loading emacsbug...done Must be string or vector: #<mswindows-frame "emacs" 0x29fe> Loading emacsbug... Loading vm-motion...done Loading vm-motion... Loading vm-message...done Loading vm-message...

3 participants
2 comments

Re: pcl-cvs-v2_9_9 feature 24 years

Neal D. Becker

>>>>> "Dan" == Dan Holmsand <dan(a)eyebee.com> writes: Dan> nbecker(a)fred.net writes: >> After running cvs-status, I see a file that says "Need update". I've >> got r1.15, while the current is r1.16. I'd like to see what has been >> changed in the file. There doesn't seem to be any way to do this >> under pcl-cvs-2.9.9. Selecting either diff "=" or interactive diff >> "de" doesn't work. Instead, it seems to be diffing between my current >> 1.15 and the repository 1.15, which shows no differences. I want to >> diff against the head. This must be a commonly desired item. Dan> Does "dh" (cvs-mode-diff-head) do what you want? Possibly, but it isn't on the menu! so I didn't know it was an option.

1 participants
0 comments

Re: pcl-cvs-v2_9_9 feature 24 years

Dan Holmsand

nbecker(a)fred.net writes: > After running cvs-status, I see a file that says "Need update". I've > got r1.15, while the current is r1.16. I'd like to see what has been > changed in the file. There doesn't seem to be any way to do this > under pcl-cvs-2.9.9. Selecting either diff "=" or interactive diff > "de" doesn't work. Instead, it seems to be diffing between my current > 1.15 and the repository 1.15, which shows no differences. I want to > diff against the head. This must be a commonly desired item. Does "dh" (cvs-mode-diff-head) do what you want? /dan -- Dan Ola Holmsand IB dan(a)eyebee.com

1 participants
0 comments

Re: pcl-cvs-v2_9_9 feature 24 years

Neal D. Becker

>>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: >>>>> "nbecker" == nbecker <nbecker(a)fred.net> writes: nbecker> After running cvs-status, I see a file that says "Need nbecker> update". I've got r1.15, while the current is r1.16. nbecker> I'd like to see what has been changed in the file. There nbecker> doesn't seem to be any way to do this under nbecker> pcl-cvs-2.9.9. Selecting either diff "=" or interactive nbecker> diff "de" doesn't work. Instead, it seems to be diffing nbecker> between my current 1.15 and the repository 1.15, which nbecker> shows no differences. I want to diff against the head. nbecker> This must be a commonly desired item. APA> What platform are you on? APA> This working fine for me in APA> pcl-cvs-version APA> "v2_9_9" APA> (emacs-version) APA> "XEmacs 21.1 (patch 12) \"Channel Islands\" [Lucid] (i386-pc-win32) of APA> Fri Nov 17 2000 on ZJ75T" I'm using pcl-cvs-version "v2_9_9" (emacs-version) Value: "21.1 (patch 12) \"Channel Islands\" XEmacs Lucid" (i686-pc-linux-gnu)

1 participants
0 comments

Re: pcl-cvs-v2_9_9 feature 24 years

Adrian Aichner

>>>>> "nbecker" == nbecker <nbecker(a)fred.net> writes: nbecker> After running cvs-status, I see a file that says "Need nbecker> update". I've got r1.15, while the current is r1.16. nbecker> I'd like to see what has been changed in the file. There nbecker> doesn't seem to be any way to do this under nbecker> pcl-cvs-2.9.9. Selecting either diff "=" or interactive nbecker> diff "de" doesn't work. Instead, it seems to be diffing nbecker> between my current 1.15 and the repository 1.15, which nbecker> shows no differences. I want to diff against the head. nbecker> This must be a commonly desired item. What platform are you on? This working fine for me in pcl-cvs-version "v2_9_9" (emacs-version) "XEmacs 21.1 (patch 12) \"Channel Islands\" [Lucid] (i386-pc-win32) of Fri Nov 17 2000 on ZJ75T" Adrian nbecker> I know I can switch to vc and do diff between revisions, nbecker> but it would be nice to not have to switch tools. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org

1 participants
0 comments

pcl-cvs-v2_9_9 feature 24 years

Neal D. Becker

After running cvs-status, I see a file that says "Need update". I've got r1.15, while the current is r1.16. I'd like to see what has been changed in the file. There doesn't seem to be any way to do this under pcl-cvs-2.9.9. Selecting either diff "=" or interactive diff "de" doesn't work. Instead, it seems to be diffing between my current 1.15 and the repository 1.15, which shows no differences. I want to diff against the head. This must be a commonly desired item. I know I can switch to vc and do diff between revisions, but it would be nice to not have to switch tools.

1 participants
0 comments

Re: Tabs widget problem in 21.2.37 24 years

Markus Alt

Andy Piper wrote: > > At 02:40 PM 11/14/00 +0100, Markus Alt wrote: > >Apparently the problem reported by Stephen in > > > > http://www.xemacs.org/list-archives/xemacs-beta/200010/msg00190.html > > > >still exists in 21.2.37, although I had to set > >`buffers-tab-filter-functions' to nil in order to see the tabs of all > >open buffers. Previously, I just had to set > > > > buffers-tab-max-buffer-line-length 25 > > buffers-tab-max-size 6 > > > >to get all of the tabs. > > Don't understand this. If I set max-size to 10 I get 10 buffers. What were > you expecting? Ups, apparently I mixed this up! Sorry for the confusion, Andy! The values above are Stephen's which he noted in the aforementioned thread. Mine are buffers-tab-max-buffer-line-length 0 buffers-tab-max-size nil But, as said, I had to set `buffers-tab-filter-functions' also to nil in order to see the tabs of all open buffers (starting with 21.2.37). However, this is not a problem. The problem are the overlapping tabs. But I see from your answer to original thread that you were able to reproduce it. Sorry again for the misleading info! Markus

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 November 2000