August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: 21.2.19 SEGV on null frame pointer 24 years, 9 months

Jan Vroonhof

Karl Kleinpaste <karl(a)justresearch.com> writes: > I'm leaving this (dying) XEmacs attached to the gdb which caught it, > so I am open to suggestions for things to look at. Anything you'd > like to see pobj'd...? The window id as given in the X event structure of the event x_event_to_emacs_event is dealing with and whether you can find this id some where in 'xwininfo -tree' Note that below for the 'magic' X events the event dropped onto the floor when x_any_window_to_frame == 0 [1]. Maybe the same thing should be done for keyboard events? Jan Footnotes: [1] And that is wrong for other reasons for things like SelectionClear.

2 participants
1 comments

Re: package manager misuses pgp5, and fails with pgp2.6.2, too 24 years, 9 months

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > SL Baur <steve(a)xemacs.org> writes: >> As am I. I now have a pgp 2.6.3 binary built from sources off of >> replay.com. Should I try signing with that version instead? > That would be heaven for now. I will give that a try. I was under a mistaken impression about what the "international" version of pgp 2 is. I presume it is legal for me to use. It is very depressing how difficult this situation is.

1 participants
0 comments

Re: 21.2.19 SEGV on null frame pointer 24 years, 9 months

Jan Vroonhof

Karl Kleinpaste <karl(a)justresearch.com> writes: > 0x4c002d9 (has no name): () 481x15+4+258 +9+279 > 0x4c0014b (has no name): () 481x15+4+258 +9+279 Notice how these two have exactly the same coordinates. > Hm, given the window name cited by xwininfo, I guess my recollection > about Gnus having cleaned itself out to just the *Group* buffer was > incorrect -- it hadn't gotten quite that far yet. Maybe there is some race condition where XEmacs thinks it has deleted the window but X still thinks it is there? Jan

1 participants
0 comments

Re: regexp-opt 24 years, 9 months

SL Baur

Olivier Galibert <galibert(a)pobox.com> writes in xemacs-beta(a)xemacs.org: > regexp-opt is for now part of xemacs-devel, which mean usually not > installed by non xemacs-developers. Bad thing is, it is used by > make-mode.el without even a require. What is the right fix? make-mode should require it for starters. Maybe regexp-opt needs to be moved. What does it buy one, exactly?

1 participants
0 comments

Re: 21.2.19 SEGV on null frame pointer 24 years, 9 months

Karl Kleinpaste

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > The window id as given in the X event structure of the event > x_event_to_emacs_event is dealing with and whether you can find this > id some where in 'xwininfo -tree' Very interesting. "xwininfo -tree" informs me... xwininfo: Window id: 0x4c00029 "emacs: *Summary comp.emacs.xemacs*" Root window id: 0x26 (the root window) (has no name) Parent window id: 0x1808752 (has no name) 1 child: 0x4c0002a (has no name): () 1267x976+0+0 +5+21 10 children: 0x4c002db (has no name): () 1244x15+4+933 +9+954 0x4c002a2 (has no name): () 15x866+1248+67 +1253+88 0x4c002b1 (has no name): () 15x206+1248+67 +1253+88 0x4c002d9 (has no name): () 481x15+4+258 +9+279 0x4c0015f (has no name): () 15x191+485+67 +490+88 0x4c0012b (has no name): () 15x661+485+287 +490+308 0x4c0014b (has no name): () 481x15+4+258 +9+279 0x4c002b3 (has no name): () 1244x15+4+258 +9+279 0x4c0002c (has no name): () 1267x950+0+26 +5+47 0x4c0002b (has no name): () 1265x24+0+0 +5+21 And gdb reveals... (gdb) p/x x_event->xany.window $49 = 0x4c002d9 ...being the 4th child down in the list. BTW... (gdb) p x_event->xkey.keycode $50 = 46 ...which is an `l', the 2nd of the keystrokes I'd hit when XEmacs tripped over the SEGV. Hm, given the window name cited by xwininfo, I guess my recollection about Gnus having cleaned itself out to just the *Group* buffer was incorrect -- it hadn't gotten quite that far yet. If you need to see how my Gnus-involved XEmacs usually looks (if it matters to understanding what all the child windows are), take a peek at http://www.cs.cmu.edu/~karl/gnus/pterodactyl/sample.gif. --karl

1 participants
0 comments

Re: current-pixel-column 24 years, 9 months

William M. Perry

Andy Piper <andy(a)xemacs.org> writes: > How about this? How about one for passing in an arbitrary buffer position, not just current-point? -Bill P.

3 participants
2 comments

Re: etc/custom/theme-examples? 24 years, 9 months

Jan Vroonhof

nbecker(a)fred.net writes: > According to CHANGES-beta: > -- Custom themes, API part. See etc/custom/theme-examples from Jan Vroonhof > > I don't have any etc/custom-theme-anything It is actually "etc/custom/example-themes" Did you use "-d" with CVS update? Jan

1 participants
0 comments

Re: (b19) I can't use custom anymore (because of themes) 24 years, 9 months

Jan Vroonhof

Didier Verna <verna(a)inf.enst.fr> writes: > I'm wrong. It's a bug that I fixed some time ago, but seems to have > reappeared with the themes stuff: custom doesn't protect symbols with special > characters in them when writing the custom file. It's a matter of using > print1-to-string instead of print1 somewhere. I haven't found out where yet. This is just a guess: I think it is more related to the comment stuff. I rewrote the whole write-out logic so it is actually (more) logic[1], when I merged it in with the theme stuff. Jan Footnotes: [1] It was already ugly before. You addition of yet another case just made it cross the annoyance barrier.

1 participants
0 comments

Re: XEmacs 21.2.19 "?$B?7=I?(B" is released 24 years, 9 months

Jan Vroonhof

"Barry A. Warsaw" <bwarsaw(a)cnri.reston.va.us> writes: > > What am I doing wrong (this has worked for me before)? The package-index.LASTEST is gpg signed again. It should point to the unsigned version as gpg. Jan

1 participants
0 comments

Re: package manager misuses pgp5, and fails with pgp2.6.2, too 24 years, 9 months

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > Right. Jan Vroonhof has been having me do that for some number of > releases now to bypass mailcrypt signature checking problems. I think > the current situation is hopeless and I give up. Join the club :-( There are just too many failure modes for using pgp 5 style signatures right now. Combine that with the fact that mailcrypt was never designed to be a library and bingo! The right scenario would be 1. We sign with pgp 2.6 for now 2. somebody writes a true digsignature.el that does its own parsing of the PGP armor and can accurately distinguish between 1. false signature. 2. PGP 5 sign used but only pgp 2.6 availaible 3. PGP 2.6 sign used but only gpg-norsa available 4. PGP available, but not setup for the user 5. no PGP available. [Note: I have seen all of these in real life except 1.] 3. This gets embedded in to package-get.el 4. We try again. > As am I. I now have a pgp 2.6.3 binary built from sources off of > replay.com. Should I try signing with that version instead? That would be heaven for now. Jan

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