December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [CRASH] 21.2-b5 with Jonathan's gc crash fix applied 25 years, 5 months

Norbert Koch

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Norbert Koch <n.koch(a)delta-ii.de> writes: > > > Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > > > > > >>>>> "Jonathan" == Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes: > > > > > > Jonathan> Adrian Aichner wrote: > > > Here's another of these: > > > > > > I have the baby tarpped inside MS VC++. How can I provide you with > > > the debug_backtrace() information? > > > > > > > I'm not sure I understand Jonathan's remark, but I guess he is > > thinking about the callstack, you can display in MS VC++. > > No, I think debug_backtrace() is the C function that spits out the > Lisp backtrace. You get it by calling `debug_backtrace()' from your > favorite debugger, and capturing the resulting output. Fie! Thanks :-) -- .. One FISHWICH coming up!!

1 participants
0 comments

Re: ksh mode in 21.0.60 doesn't do () or {} ? 25 years, 5 months

Adrian Aichner

>>>>> "Adrian" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: >>>>> "Matthew" == Matthew O Persico <mpersico(a)erols.com> writes: Matthew> I just noticed today that ksh mode does not do Matthew> match-highlighting fpr () or {}, as in the following: Matthew> foobar () { Matthew> if [ "$foo" = "$bar" ] Matthew> then Matthew> cd $(dirname $1) Matthew> fi Matthew> } Matthew> This is a legal ksh function def. The () that signify a Matthew> function don't highight. Neither do the braces not the Matthew> parens around the sub-shell invokation of dirname. Adrian> What do you have paren-mode set to? Mine is 'sexp. Adrian> If I put point at any closing ) or } above it highlights the whole Adrian> SEXP backwards including the matching open-paren or open-brace in Adrian> 21.2-b5+. 21.0-b60 shows the same behavior. Adrian> The only nit I have is that foobar is not highlit in Adrian> font-lock-function-name-face. Adrian> Here's what I see: Adrian> - c:\\Program Files\\TechSmith\\SnagIt32\\foobar-ksh.png Matthew> Was this always the case or did it break? Matthew> -- Matthew> Matthew O. Persico Matthew> http://www.erols.com/mpersico Matthew> http://www.digistar.com/bzip2 Adrian> -- Adrian> Adrian Aichner Adrian> European Design Center Adrian> Teradyne GmbH Adrian> Semiconductor Test Group Telephone +49/89/41861(0)-208 Adrian> Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) Adrian> D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com -- Adrian Aichner European Design Center Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: [CRASH] 21.2-b5 with Jonathan's gc crash fix applied 25 years, 5 months

Hrvoje Niksic

Norbert Koch <n.koch(a)delta-ii.de> writes: > Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > > > >>>>> "Jonathan" == Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes: > > > > Jonathan> Adrian Aichner wrote: > > >> > > >> This seems to be a new kind... > > > > Jonathan> I haven't played with 21.2 since Martin's changes. Could > > Jonathan> you provide a debug_backtrace() next time you hit this > > Jonathan> and a description of how to reproduce the problem, or > > Jonathan> failing that a description of what you were doing. > > > > Here's another of these: > > > > I have the baby tarpped inside MS VC++. How can I provide you with > > the debug_backtrace() information? > > > > I'm not sure I understand Jonathan's remark, but I guess he is > thinking about the callstack, you can display in MS VC++. No, I think debug_backtrace() is the C function that spits out the Lisp backtrace. You get it by calling `debug_backtrace()' from your favorite debugger, and capturing the resulting output.

1 participants
0 comments

Re: [PATCH] x-(get|set)-font-path 25 years, 5 months

William M. Perry

Christoph Wedler <wedler(a)fmi.uni-passau.de> writes: > >>>>>"KJ" == Kyle Jones <kyle_jones(a)wonderworks.com> writes: > > KJ> Christoph Wedler writes: > >> I only know, that my package X-Symbol really really needs additional > >> fonts (as I said, much less with a XEmacs face property > >> `baseline-shift'). > > KJ> Please explain how this baseline-shift property would be used. > KJ> I'm assuming it wold do what glyph-baselines do now, except apply > KJ> to the glyphs of a face's font. > > To display super- and subscripts in HTML and LaTeX buffers (via > font-lock). > http://www.fmi.uni-passau.de/~wedler/x-symbol/subscripts.png > > I could define the faces with > > (defface x-symbol-sub-face > '((((class color) (background light)) > (:family "Helvetica" :size "12pt" :baseline -2))) ; 2pt shifted down > "") > ;; using (set-face-baseline 'x-symbol-sub-face -2) would be fine for > ;; me, too > > instead (this is how it is done now) > > (defface x-symbol-sub-face > '((((class color) (background light)) > (:family "Helvetica_sub" :size "12pt"))) > "") > > and produce fonts Helvetica_sub (and _sup) with a PERL script. Please please please put this in. :) -Bill P.

1 participants
0 comments

Re: [PATCH] x-(get|set)-font-path 25 years, 5 months

Christoph Wedler

>>>>>"KJ" == Kyle Jones <kyle_jones(a)wonderworks.com> writes: KJ> Christoph Wedler writes: >> I only know, that my package X-Symbol really really needs additional >> fonts (as I said, much less with a XEmacs face property >> `baseline-shift'). KJ> Please explain how this baseline-shift property would be used. KJ> I'm assuming it wold do what glyph-baselines do now, except apply KJ> to the glyphs of a face's font. To display super- and subscripts in HTML and LaTeX buffers (via font-lock). http://www.fmi.uni-passau.de/~wedler/x-symbol/subscripts.png I could define the faces with (defface x-symbol-sub-face '((((class color) (background light)) (:family "Helvetica" :size "12pt" :baseline -2))) ; 2pt shifted down "") ;; using (set-face-baseline 'x-symbol-sub-face -2) would be fine for ;; me, too instead (this is how it is done now) (defface x-symbol-sub-face '((((class color) (background light)) (:family "Helvetica_sub" :size "12pt"))) "") and produce fonts Helvetica_sub (and _sup) with a PERL script. - Christoph

2 participants
1 comments

New 2.51 folding available 25 years, 5 months

Jari Aalto

-----BEGIN PGP SIGNED MESSAGE----- ## Subject: New 2.51 folding available Thanks to Gleb Arshinov <gleb(a)CS.Stanford.EDU> who has reported and fixed the recent 21.x bugs, the new folding is available at Anders's ftp dir ftp://ftp.csd.uu.se/pub/users/andersl/beta/ I also noticed that in the Misc text utilitied section, the package listing showed providing fold-isearch Please remove it and the package if you have, because foldin.el itself has included that package long time by now. jari -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv Comment: Processed by Emacs TinyPgp 2.97 iQBVAwUBNnkB4cC67dVHFB01AQGhtwIAwt9q9xdbAGihPWY4lLv8VZ+cTQzg5dJL HytMtivm18JN5yhxth/yo7u2je585Fc/uPnAYyQO4MOGog5QLrAXgA== =LGgV -----END PGP SIGNATURE-----

1 participants
0 comments

Re: [PATCH] x-(get|set)-font-path 25 years, 5 months

Kyle Jones

Christoph Wedler writes: > I only know, that my package X-Symbol really really needs additional > fonts (as I said, much less with a XEmacs face property > `baseline-shift'). Please explain how this baseline-shift property would be used. I'm assuming it wold do what glyph-baselines do now, except apply to the glyphs of a face's font.

1 participants
0 comments

Re: [CRASH] 21.2-b5 with Jonathan's gc crash fix applied 25 years, 5 months

Norbert Koch

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > >>>>> "Jonathan" == Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes: > > Jonathan> Adrian Aichner wrote: > >> > >> This seems to be a new kind... > > Jonathan> I haven't played with 21.2 since Martin's changes. Could > Jonathan> you provide a debug_backtrace() next time you hit this > Jonathan> and a description of how to reproduce the problem, or > Jonathan> failing that a description of what you were doing. > > Here's another of these: > > I have the baby tarpped inside MS VC++. How can I provide you with > the debug_backtrace() information? > > Please advise, I'm not sure I understand Jonathan's remark, but I guess he is thinking about the callstack, you can display in MS VC++. There is an option (you know, like right mouse-button on the toolbar) to show it. The callstack is analogous to the 'where' backtrace in gdb. Norbert, guessing. -- HELLO KITTY gang terrorizes town, family STICKERED to death!

1 participants
0 comments

Re: [CRASH] 21.2-b5 with Jonathan's gc crash fix applied 25 years, 5 months

Adrian Aichner

>>>>> "Jonathan" == Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes: Jonathan> Adrian Aichner wrote: >> >> This seems to be a new kind... Jonathan> I haven't played with 21.2 since Martin's changes. Could Jonathan> you provide a debug_backtrace() next time you hit this Jonathan> and a description of how to reproduce the problem, or Jonathan> failing that a description of what you were doing. Here's another of these: I have the baby tarpped inside MS VC++. How can I provide you with the debug_backtrace() information? Please advise, Adrian NTDLL! 77f76148() error_check_cons(Lisp_Object {...}) line 717 + 80 bytes condition_case_unwind(Lisp_Object {...}) line 1521 + 9 bytes unbind_to_hairy(int 0x0000001c) line 4625 + 18 bytes unbind_to(int 0x0000001c, Lisp_Object {...}) line 4600 + 181 bytes garbage_collect_1() line 4548 + 16 bytes Fgarbage_collect() line 4601 Ffuncall(int 0x00000001, Lisp_Object * 0x0082edf8) line 3189 + 63 bytes execute_optimized_program(const unsigned char * 0x01226a18, int 0x00000005, Lisp_Object * 0x01226958) line 750 + 16 bytes funcall_compiled_function(Lisp_Object {...}, int 0x00000000, Lisp_Object * 0x0082f0e8) line 530 + 53 bytes Ffuncall(int 0x00000001, Lisp_Object * 0x0082f0e4) line 3221 + 17 bytes execute_optimized_program(const unsigned char * 0x0082f2d8, int 0x00000004, Lisp_Object * 0x01225b3c) line 750 + 16 bytes Fbyte_code(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 2400 + 38 bytes Feval(Lisp_Object {...}) line 2986 + 195 bytes condition_case_1(Lisp_Object {...}, Lisp_Object (Lisp_Object)* 0x01058b06 Feval(Lisp_Object), Lisp_Object {...}, Lisp_Object (Lisp_Object, Lisp_Object)* 0x0105643e run_condition_case_handlers(Lisp_Object, Lisp_Object), Lisp_Object {...}) line 1640 + 7 bytes condition_case_3(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 1721 + 27 bytes execute_rare_opcode(Lisp_Object * 0x0082f630, const unsigned char * 0x01225e12, int 0x0000008f) line 1275 + 19 bytes execute_optimized_program(const unsigned char * 0x01225d4c, int 0x00000008, Lisp_Object * 0x01225994) line 660 + 17 bytes funcall_compiled_function(Lisp_Object {...}, int 0x00000001, Lisp_Object * 0x0082f92c) line 530 + 53 bytes Ffuncall(int 0x00000002, Lisp_Object * 0x0082f928) line 3221 + 17 bytes execute_optimized_program(const unsigned char * 0x01226764, int 0x00000005, Lisp_Object * 0x01226708) line 750 + 16 bytes funcall_compiled_function(Lisp_Object {...}, int 0x00000001, Lisp_Object * 0x0082fc24) line 530 + 53 bytes Ffuncall(int 0x00000002, Lisp_Object * 0x0082fc20) line 3221 + 17 bytes call1(Lisp_Object {...}, Lisp_Object {...}) line 3834 + 11 bytes execute_internal_event(Lisp_Object {...}) line 3044 + 19 bytes Fdispatch_event(Lisp_Object {...}) line 4689 + 9 bytes Fcommand_loop_1() line 578 + 9 bytes command_loop_1(Lisp_Object {...}) line 494 condition_case_1(Lisp_Object {...}, Lisp_Object (Lisp_Object)* 0x0103a91e command_loop_1(Lisp_Object), Lisp_Object {...}, Lisp_Object (Lisp_Object, Lisp_Object)* 0x0103a3ab cmd_error(Lisp_Object, Lisp_Object), Lisp_Object {...}) line 1640 + 7 bytes command_loop_3() line 255 + 35 bytes command_loop_2(Lisp_Object {...}) line 267 internal_catch(Lisp_Object {...}, Lisp_Object (Lisp_Object)* 0x0103a513 command_loop_2(Lisp_Object), Lisp_Object {...}, int * volatile 0x00000000) line 1315 + 7 bytes initial_command_loop(Lisp_Object {...}) line 304 + 25 bytes STACK_TRACE_EYE_CATCHER(int 0x00000001, char * * 0x10105680, char * * 0x101ce100, int 0x00000000) line 1715 + 9 bytes main(int 0x00000001, char * * 0x10105680, char * * 0x101ce100) line 2144 + 21 bytes XEMACS! mainCRTStartup + 180 bytes _start() line 165 KERNEL32! 77f1b304() Jonathan> Jonathan. Jonathan> -- Jonathan> Jonathan Harris | jhar(a)tardis.ed.ac.uk Jonathan> London, England | Jonathan.Harris(a)symbian.com -- Adrian Aichner European Design Center Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: ksh mode in 21.0.60 doesn't do () or {} ? 25 years, 5 months

Adrian Aichner

>>>>> "Matthew" == Matthew O Persico <mpersico(a)erols.com> writes: Matthew> I just noticed today that ksh mode does not do Matthew> match-highlighting fpr () or {}, as in the following: Matthew> foobar () { Matthew> if [ "$foo" = "$bar" ] Matthew> then Matthew> cd $(dirname $1) Matthew> fi Matthew> } Matthew> This is a legal ksh function def. The () that signify a Matthew> function don't highight. Neither do the braces not the Matthew> parens around the sub-shell invokation of dirname. What do you have paren-mode set to? Mine is 'sexp. If I put point at any closing ) or } above it highlights the whole SEXP backwards including the matching open-paren or open-brace in 21.2-b5+. The only nit I have is that foobar is not highlit in font-lock-function-name-face. Here's what I see: Matthew> Was this always the case or did it break? Matthew> -- Matthew> Matthew O. Persico Matthew> http://www.erols.com/mpersico Matthew> http://www.digistar.com/bzip2 -- Adrian Aichner European Design Center Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

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 1998