December 1999 - XEmacs-Beta - XEmacs Mailing List Archives

[CRASH] Crash instantiating widgets with CVS ~00:30GMT 23/12 24 years, 4 months

Daniel Pittman

Running the glyph tests with a new CVS build I got a crash. Backtrace is attached, the specific test is: (set-extent-begin-glyph (make-extent (point) (point)) (make-glyph [button :face modeline-mousable :descriptor "ok" :callback foo :image [xpm :file "../etc/xemacs-icon.xpm"]])) uname -a: Linux inanna 2.2.14pre16 #1 Wed Dec 22 16:34:20 EST 1999 i686 unknown ./configure '--with-mule' '--with-sound=native,nonas,noesd' '--with-athena=next' '--with-scrollbars=athena' '--debug=no' '--error-checking=none' XEmacs 21.2-b24 "Hecate" configured for `i686-pc-linux'. Where should the build process find the source code? /usr/src/xemacs What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Athena scrollbars. Using Athena native widgets. Using Athena dialog boxes. Compiling in dynamic shared object module support. movemail will use "dot-locking" for locking mail spool files. -- Trust the art, not the artist. -- Bruce Springsteen

2 participants
1 comments

Re: Merging customize support 24 years, 4 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > wmperry(a)aventail.com (William M. Perry) writes: > > > slant can be italic or oblique. > > Surely it allows a value for normal fonts :-) nil?

1 participants
0 comments

Re: Merging customize support 24 years, 4 months

William M. Perry

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > wmperry(a)aventail.com (William M. Perry) writes: > > > slant can be italic or oblique. > > Surely it allows a value for normal fonts :-) Sorry, was in a hurry. :) ----------------------- `:slant' VALUE specifies the slant of the font to use. It must be one of the symbols `italic', `oblique', `normal', `reverse-italic', or `reverse-oblique'. ----------------------- -bp

1 participants
0 comments

Re: Merging customize support 24 years, 4 months

Jan Vroonhof

wmperry(a)aventail.com (William M. Perry) writes: > slant can be italic or oblique. Surely it allows a value for normal fonts :-) Jan

1 participants
0 comments

Re: Merging customize support 24 years, 4 months

William M. Perry

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > >>>>> "Per" == Per Abrahamsen <abraham(a)dina.kvl.dk> writes: > > Per> In Emacs 21 :bold and :italic are being fased out in favor of > Per> :weight and :slant. :bold and :italic are still recognized > Per> by `defface' for backward compatibility, but not by > Per> `customize-face'. > > :weight is obviously a good idea (although I wish somebody would > define weight quantitatively in a way that makes it possible to match > weights for different character sets). > > What values does :slant take? It had better not be a boolean, nor > numerical: italic != slanted. Or have they given up on trying to match > roman and italic fonts by family, and are doing it by database? slant can be italic or oblique. -Bill P.

1 participants
0 comments

Re: Reflections on Athena Configuration 24 years, 4 months

Daniel Pittman

On 22 Dec 1999, Vin Shelton <acs(a)xemacs.org> wrote: > Last night I compiled 21.2 from the latest CVS sources to check out > Daniel Pittman's new athena configuration stuff. Here's what I found > along the way. [...] > 2. Next I installed the neXtaw library (into the default location > generated by xmkmf) and the header files ended up in > /usr/X11R6/include/neXtaw. I can submit a patch to search in `Xaw*/' for headers, but I don't know if that is the right thing(tm) to do. I think that Athena headers are supposed to be accessed as <X11/Xaw/*> and all... [...] > 3. (Off topic) OK, now I have this XEmacs with this spiffier scrollbar > - is it possible to get this to scroll by more than one line? This > seems like the most feeble (and slowest) scrollbar I've ever used; > why would I want it? Actually, when I read this I went and tried it and, yes, you are right. The repeat behavior is /awful/. So, I sent a patch off to Mr Kojima just now, making the initial delay and repeat rate configurable with resources. If you want the patch, I will send it to y'all. I mostly wanted neXtaw because the rest of my system looks as much like neXtaw as possible... Daniel -- Increasing numbers of private-sector companies are discovering the efficiency of hiring bright undergraduates or recent graduates and paying them next to nothing. -- Washingtonian magazine

1 participants
0 comments

Re: Merging customize support 24 years, 4 months

Per Abrahamsen

wmperry(a)aventail.com (William M. Perry) writes: > Sure. We should really just try to emulate the real font model that is in > Emacs 21 right now though. This would be a huge win for cross-platform > setting of font resources. In Emacs 21 :bold and :italic are being fased out in favor of :weight and :slant. :bold and :italic are still recognized by `defface' for backward compatibility, but not by `customize-face'. Do you want XEmacs 21.2 to go the same way?

2 participants
1 comments

Reflections on Athena Configuration 24 years, 4 months

Vin Shelton

Last night I compiled 21.2 from the latest CVS sources to check out Daniel Pittman's new athena configuration stuff. Here's what I found along the way. 1. Even though I had been successfully building with Xaw3d, I hadn't installed the 3d headers. If I understand the emails which had been passing back and forth, this was a good recipe for a crash. The new configuration code warned me about this and defaulted to plain old athena. Good job, Daniel. 2. Next I installed the neXtaw library (into the default location generated by xmkmf) and the header files ended up in /usr/X11R6/include/neXtaw. (This is a Mandrake 6.1 system, BTW). The new configuration code could not find the headers in this spot, so I added a symlink from /usr/X11R6/include/X11/neXtaw to /usr/X11R6/include/neXtaw; this made the neXtaw configuration work fine. Daniel, I don't know if you want to support /usr/X11R6/include/neXtaw, it seems like a good idea to me, but you have a much better idea than I do. 3. (Off topic) OK, now I have this XEmacs with this spiffier scrollbar - is it possible to get this to scroll by more than one line? This seems like the most feeble (and slowest) scrollbar I've ever used; why would I want it? Anyway, that's what I found. Nice work, Daniel. - vin

1 participants
0 comments

Re: Merging customize support 24 years, 4 months

William M. Perry

Andy Piper <andy(a)xemacs.org> writes: > This sounds cool. Is the code available? If you can get the Emacs 21 distribution out of CVS, yes. I've been asked not to advertise where exactly you can get that though. If you are on the Emacs 21 pretesters list, you know where to find it. :) -Bill P.

1 participants
0 comments

Re: Merging customize support 24 years, 4 months

William M. Perry

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > William M. Perry writes: > > So to make a face in Emacs 21 now, you do: > > > > (make-face 'foo) > > (set-face-attribute 'foo nil > > :family "lucidatypewriter" > > :width 'normal > > :height 200 > > :weight 'normal > > :foreground "red" > > :background "pink" > > :strike-through t) > > Well, I almost like this setup. The thing I don't like is a face having > all these properties. A property list like this should be recognized as > an instantiator for a font specifier. Well, that was kind of the idea behind font.el. Although you need more than just a font specifier to replace font.el. You would need various new face specifiers like dropcaps, smallcaps, etc. But that takes more redisplay hackery than just new font stuff. -Bill P.

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