May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Outstanding hot issues. Was[ Re: is `-name' functional?] 26 years, 6 months

Jan Vroonhof

Didier Verna <verna(a)inf.enst.fr> writes: > - What's the status of the .xemacs directory for 21.0 ? I'd be sad > if it's not gonna make it. I just had a look the code again (I have code in .emacs to load .xemacs/init.el so I don't notice it before.) But currently XEmacs prefers .xemacs/init.el when it is present. Secondly the default value of custom-file is ~/.xemacs/options.el ! So while I have seen patches striking it from the documentations we still use the .xemacs dir! > - Sorry but I still think that this mess about the application class > - Sorry again ;-) but I still think that the modeline shouldn't have the same > default as the default face, and shouldn't be affected by the -bg > option. Although not implemented exactly this way, the modeline *is* a > widget and should look like the menubar, the scrollbars and the dividers by > default. YES! YES! YES! YES! YES! YES! YES! YES! YES! YES! YES! YES! YES! YES! YES! YES! , sorry, OUI! OUI! OUI! OUI! OUI! OUI! OUI! OUI! OUI! OUI! OUI! OUI! OUI! OUI! OUI! OUI!. I hope it is clear that I agree!. I only have two patches running against CVS again, this one for ages" Index: etc/Emacs.ad =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/etc/Emacs.ad,v retrieving revision 1.8 diff -u -r1.8 Emacs.ad --- Emacs.ad 1998/03/10 04:11:50 1.8 +++ Emacs.ad 1998/05/19 19:57:26 ＠＠ -31,8 +31,8 ＠＠ ! `rgb.txt', usually found in /usr/lib/X11/ or /usr/openwin/lib/X11/. ! Set the modeline colors. -!Emacs.modeline*attributeForeground: Black -!Emacs.modeline*attributeBackground: Gray75 +Emacs.modeline*attributeForeground: Black +Emacs.modeline*attributeBackground: Gray80 ! Set the color of the text cursor. !Emacs.text-cursor*attributeBackground: Red3

1 participants
0 comments

xpm file problem / bug 26 years, 6 months

Andy Piper

I have this problem both with xpm and my cursor implementation. If you do something like: (make-glyph [xpm :file "some-non-existant-file.xpm"]) You don't get an error. Now I have debugged the code and signal_double_error *is* getting called by potential_pixmap_instantiator, but the error doesn't make its way back up to emacs. Does anyone else see this or know why this happens? andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

1 participants
0 comments

Re: is `-name' functional? 26 years, 6 months

Didier Verna

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > >>>>> "Didier" == Didier Verna <verna(a)inf.enst.fr> writes: > > Didier> - What's the status of the .xemacs directory for 21.0 ? I'd be sad if it's not > Didier> gonna make it. > > XEmacs currently regards ~/.xemacs as an early package hierarchy. By > default, its stuff shows up at the very beginning of the various > paths. Yes, but what about init.el and options.el ? -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: is `-name' functional? 26 years, 6 months

Michael Sperber

>>>>> "Didier" == Didier Verna <verna(a)inf.enst.fr> writes: Didier> - What's the status of the .xemacs directory for 21.0 ? I'd be sad if it's not Didier> gonna make it. XEmacs currently regards ~/.xemacs as an early package hierarchy. By default, its stuff shows up at the very beginning of the various paths. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

[i586-linux; b40] Seg fault while printing lisp backtrace after fatal error 26 years, 6 months

Samuel Mikes

XEmacs died of a seg fault while printing a lisp backtrace of an error condition. Here's the C backtrace: #0 0x8147d63 in print_internal (obj=146582848, printcharfun=137564988, escapeflag=1) at print.c:1213 1213 if (LHEADER_IMPLEMENTATION (lheader)->printer) (gdb) print lheader $19 = (struct lrecord_header *) 0xffffffff Obj is a Lisp_Type_Record, but the result of XRECORD_LRECORD (obj) is (struct lrecord_header *)(-1). The seg fault comes from the dereference of lheader. (gdb) where #0 0x8147d63 in print_internal (obj=146582848, printcharfun=137564988, escapeflag=1) at print.c:1213 #1 0x8147733 in print_cons (obj=146582848, printcharfun=137564988, escapeflag=1) at print.c:921 #2 0x8147d77 in print_internal (obj=144870916, printcharfun=137564988, escapeflag=1) at print.c:1214 #3 0x81476a9 in print_cons (obj=144871336, printcharfun=137564988, escapeflag=1) at print.c:914 #4 0x8147d77 in print_internal (obj=144871780, printcharfun=137564988, escapeflag=1) at print.c:1214 #5 0x8146778 in Fprin1 (object=144871780, stream=137564988) at print.c:506 #6 0x80b6281 in Fbacktrace (stream=137564988, detailed=137456824) at eval.c:4927 #7 0x80aa313 in fatal_error_signal (sig=11) at emacs.c:245 #8 0xbffff368 in ?? () <-- this should be a call to print_internal #9 0x8147733 in print_cons (obj=146582848, printcharfun=138966072, escapeflag=1) at print.c:921 print.c:921 -> print_internal (obj, printcharfun, escapeflag); #10 0x8147d77 in print_internal (obj=144870916, printcharfun=138966072, escapeflag=1) at print.c:1214 #11 0x8146d8d in print_error_message (error_object=144871780, stream=138966072) at print.c:651 #12 0x8146f97 in Fdisplay_error (error_object=144871780, stream=137456824) at print.c:704 #13 0x80b2caa in funcall_recording_as (recorded_as=137564736, nargs=2, args=0xbffff7e4) at eval.c:3197 #14 0x80b2e83 in Ffuncall (nargs=3, args=0xbffff7e4) at eval.c:3238 #15 0x8088fe6 in Fbyte_code (bytestr=136651092, vector=136651232, maxdepth=11) at bytecode.c:416 #16 0x80b3d90 in funcall_lambda (fun=136651436, nargs=1, arg_vector=0xbffff8f8) at eval.c:3597 #17 0x80b2e3e in funcall_recording_as (recorded_as=137531140, nargs=1, args=0xbffff8f4) at eval.c:3214 #18 0x80b2e83 in Ffuncall (nargs=2, args=0xbffff8f4) at eval.c:3238 #19 0x80b43ef in call1 (fn=137531140, arg0=144871780) at eval.c:3912 #20 0x809087c in cmd_error (data=144871780, dummy=137456796) at cmdloop.c:195 #21 0x80afecc in condition_case_1 (handlers=137456908, bfun=0x8091420 <command_loop_1>, barg=137456796, hfun=0x8090830 <cmd_error>, harg=137456796) at eval.c:1636 #22 0x8090931 in command_loop_3 () at cmdloop.c:256 #23 0x8090958 in command_loop_2 (dummy=137456796) at cmdloop.c:267 #24 0x80afa69 in internal_catch (tag=137531196, func=0x8090950 <command_loop_2>, arg=137456796, threw=0x0) at eval.c:1328 #25 0x8090cdb in initial_command_loop (load_me=137456796) at cmdloop.c:305 #26 0x80ab443 in xemacs_21_0_b40_i586_pc_linux (argc=1, argv=0xbffffab4, envp=0xbffffabc, restart=0) at emacs.c:1683 #27 0x80abbdd in main (argc=1, argv=0xbffffab4, envp=0xbffffabc) at emacs.c:2100 #28 0x80781ee in _start () Here's the lisp backtrace it was trying to print when it died: Lisp backtrace follows: # bind (print-message-label) display-error((error "Invalid list format" (vm-add-mail-mode-header-separator vm-convert-folder-type-headers vm-digest-get-header-contents vm-parse-structured -header vm-energize-headers vm-mime-parse-content-header vm-headers-of vm-set-he aders-of vm-match-ordered-header vm-mm-encoded-header vm-vheaders-regexp-of vm-s tartup-apply-header-variables vm-matched-header-contents-start vm-mime-get-heade r-contents vm-reorder-message-headers vm-matched-header-contents vm-matched-head er-contents-end vm-set-mime-encoded-header-flag-of vm-mail-mode-get-header-conte nts vm-highlight-headers-maybe vm-matched-header-end vm-stuff-header-variables v m-forward-message-all-headers vm-match-header vm-mm-layout-header-start vm-remov e-mail-mode-header-separator vm-matched-header vm-energize-headers-and-xfaces vm -vheaders-of vm-highlight-headers vm-forward-message-all-headers-other-frame vm- matched-header-name vm-convert-folder-header vm-folder-header vm-matched-header- name-end vm-decode-mime-message-headers vm-save-message-sans-headers vm-matched- header-start vm-gobble-visible-header-variables vm-mime-insert-mime-headers vm-m atched-header-name-start vm-vs-header-or-text vm-set-vheaders-regexp-of vm-build I haven't tried to reproduce it yet: I think I was executing M-x apropos RET vm.*mark RET when it died, so this may have happened somewhere in hyper-apropos. I'm currently recompiling with more debuging and error checking information, and I'll try to reproduce it then. Tips and suggestions are very welcome! Thanks, -- Sam Mikes smikes(a)alumni.hmc.edu

1 participants
0 comments

Re: [bug] Completions buffer not splitting window! 26 years, 6 months

Hrvoje Niksic

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > Some time ago, Hrvoje Niksic wrote... > |+ > | In b40, showing the completions buffer fails to split the current > | window! > > Not for me. What do you do to see the problem? I can't repeat it anymore. Sorry for the false alarm. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- I luv the smell of nature in the morning. Smells like manure!

1 participants
0 comments

Re: New redisplay engine for Emacs 20.x? 26 years, 6 months

Hrvoje Niksic

"William M. Perry" <wmperry(a)aventail.com> writes: > Is he talking about the XEmacs engine? Or did they go back and totally > reimplement everything yet again? The latter, probably. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Speak softly and carry a +6 two-handed sword.

1 participants
0 comments

Re: is `-name' functional? 26 years, 6 months

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > I guess it's adding insult to injury, but the "solution" to that is > of course `xemacs-21.0-b39 -name xemacs'. OK, you convinced me; thanks for being patient. * `-name foo' has nothing to do with application class. The two are quite orthogonal, only in some (rare) circumstances they overlap. * The xterm examples confused me because I happened to have my xterm resources as `xterm*' rather than `XTerm*'. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Ooh, Granny, what a BIG belly-button you have!

1 participants
0 comments

patch for patch-xemacs.sh 26 years, 6 months

Jeff Miller

I had inadvertently used a bash'ism here. This failed when I tried it on solaris today. Not sure if there is really a changelog associated with this. jeff --- patch-xemacs.sh.orig Mon May 18 22:47:48 1998 +++ patch-xemacs.sh Mon May 18 23:15:41 1998 ＠＠ -12,6 +12,11 ＠＠ # # Nick Holloway <Nick.Holloway(a)alfie.demon.co.uk>, 2nd January 1995. # Modified for use with XEmacs - Jeff Miller <jmiller(a)smart.net> 8 August 1997. +# +# changed "source $sourcedir/version.sh" to ". $sourcedir/version.sh" +# Using "source" was a bash'ism. +# Jeff Miller <jmiller(a)smart.net> 18 May, 1998 + # This was originally patch-kernel, which comes with the linux kernel source. # Set directories from arguments, or use defaults. ＠＠ -19,7 +24,7 ＠＠ patchdir=${2-..} # set current VERSION, PATCHLEVEL, SUBLEVEL -source $sourcedir/version.sh +. $sourcedir/version.sh # for newer version of gnu patch POSIXLY_CORRECT=t

1 participants
0 comments

toolbar weirdness again 26 years, 6 months

Jeff Miller

I'm getting similar toolbar glitches like I reported last week, though it appears that Kirril's patch that fixed has been applied. I tried his last patch on xemacs-patches but it doesn't apply cleanly for me. Jeff

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 May 1998