August 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Ignore Scaled Fonts Under Menubar? 24 years, 3 months

Daniel Pittman

On 14 Aug 2000, Vin Shelton <acs(a)xemacs.org> wrote: [...] > In my opinion, this option should appear under Options/Fonts. Does > anyone agree or care? Yes and yes. It /belongs/ there, from a UI point-of-view. :) Daniel -- Do you remember chalk hearts melting on a playground wall? Do you remember dawn escapes from moonwashed college halls? -- Marillion, _Kayleigh_ (Misplaced Childhood)

1 participants
0 comments

Ignore Scaled Fonts Under Menubar? 24 years, 3 months

Vin Shelton

Why does the Option "Ignore Scaled Fonts" appear under Options/Menubars in 21.2? What does this option have to do with menubars? The situation is no better under 21.1, BTW - it appears under Options/Menubar Appearance. In my opinion, this option should appear under Options/Fonts. Does anyone agree or care? - vin

1 participants
0 comments

Re: 21.2.24 Crashes! 24 years, 3 months

Gunnar Evermann

Ben Wing <ben(a)666.com> writes: > Gunnar Evermann wrote: > > > > resize_string also has problems if the string is shrunk as extents > > might have endpoints to the right of the new string end and therefore > > won't get adjusted. > > the solutions are, i think: > > [1] when replacing a character, callers should set POS to point to the beginning > of the following character. this should be clarified in the doc string of > resize_string(). > [2] when calling adjust_extents[], we should use the old string length, not the > new one. I had tried this and I think it will do for the case where the new char is longer than the old one. It won't work if the string shrinks, I think. BTW. the function Ffillarray is completely broken as far as the handling of extents is concerned, it doesn't even _try_ to adjust them. The only other use of resize_string (in redisplay) should be ok, as extents are explicitly detached before the resizing. I am afraid I will have no time at all for XEmacs hacking till the end of the month... I'll fix this then. Gunnar

1 participants
0 comments

PTY defines in src/process.h override src/s/linux.h 24 years, 3 months

Stephen J. Turnbull

... and the latter look a lot more sensible. But I don't know anything about PTYs. Could someone who does look at this? -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

1 participants
0 comments

Re: A New Package 24 years, 3 months

Steve Youngs

* Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: >>>>>> Steve Youngs <youngs_s(a)ozlinx.com.au> writes: Steve> My package, which is an ICQ client for XEmacs, needs an Steve> external binary program to run. The external binary is a Steve> UDP to TCP bridge. Unfortunately, at the moment it will Steve> only run on Linux (x86)[1]. Steve> See the dilemma? > No. If it's not free software, we won't distribute it. If it is, we > can. It is free software, so, in your eyes it's not a dilemma? > If it is really quite Emacs-specific, it would go in ./lib-src. If > the UDP-to-TCP bridge seems more generally useful, create a project on > SourceForge, and we can put a version in ./lib-src is that seems > necessary. Either way, it will probably get ported (and quickly; > people can't seem to live without ICQ, whatever that is ;-). Well at the moment I have no interest in doing anything with it except for using it for ICQ in XEmacs, so I guess that would make it pretty well Emacs-specific. I have put it in ./lib-src (figured that would be the best place for it). Should I just submit the package as is and mark the description "For Linux x86 only - please port me"? > The work to do it as an Emacs module would be appreciated, but that > can't change any system dependencies. Would there be any advantages to having it as a module? Or would it just be a waste of time? -- |---<Regards, Steve Youngs>-----------[GnuPG KeyID: EFD82ED2]---| | It's a funny thing about life; if you refuse to accept | | anything but the best, you very often get it | |-----------------------------<mailto:youngs_s＠ozlinx.com.au>---|

3 participants
2 comments

xemacs 21.1.12 crash 24 years, 3 months

Simon Josefsson

I was quiting gnus and triggered the following assert() Fatal error: assertion failed, file /usr/local/src/xemacs-21.1/src/eval.c, line 1877, abort() Backtrace below. I think it's similar to something I've encountered (and reported) earlier -- XEmacs trying to report a internal error and crashes signaling this. uname -a: Linux barbar.josefsson.org 2.4.0-test5 #2 Fri Aug 4 12:17:40 CEST 2000 i686 unknown ../configure '--with-mule' '--debug' XEmacs 21.1.12 "Channel Islands" configured for `i686-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.1 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 native sound support. Compiling in support for Berkeley DB. Compiling in support for LDAP. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). 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 session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. #0 0x40310d41 in __kill () from /lib/libc.so.6 #1 0x403109b6 in raise (sig=6) at ../sysdeps/posix/raise.c:27 #2 0x403120d8 in abort () at ../sysdeps/generic/abort.c:88 #3 0x80a6833 in assert_failed () at /usr/local/src/xemacs-21.1/src/emacs.c:2627 #4 0x80a7d66 in signal_1 (sig=137158604, data=145228320) at /usr/local/src/xemacs-21.1/src/eval.c:1877 #5 0x80a83bd in Fsignal (error_symbol=137158604, data=145228320) at /usr/local/src/xemacs-21.1/src/eval.c:2044 #6 0x8097a53 in Fcar (list=143789188) at /usr/local/src/xemacs-21.1/src/data.c:105 #7 0x80ac1c8 in Fbacktrace (stream=137267244, detailed=137158464) at /usr/local/src/xemacs-21.1/src/eval.c:4885 #8 0x80a68b9 in fatal_error_signal (sig=6) at /usr/local/src/xemacs-21.1/src/emacs.c:246 #9 0x40310c68 in __restore () at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127 #10 0x403120d8 in abort () at ../sysdeps/generic/abort.c:88 #11 0x80a6833 in assert_failed () at /usr/local/src/xemacs-21.1/src/emacs.c:2627 #12 0x80a7d66 in signal_1 (sig=137158548, data=145228392) at /usr/local/src/xemacs-21.1/src/eval.c:1877 #13 0x80a83bd in Fsignal (error_symbol=137158548, data=145228392) at /usr/local/src/xemacs-21.1/src/eval.c:2044 #14 0x80aca67 in signal_simple_error ( reason=0x81a2640 "Internal error: lstream not open", frob=143987016) at /usr/local/src/xemacs-21.1/src/eval.c:2053 #15 0x811a2f4 in Lstream_write_1 (lstr=0x8951148, data=0x880e568, size=24) at /usr/local/src/xemacs-21.1/src/lstream.c:289 #16 0x811ae91 in Lstream_write (lstr=0x8951148, data=0x880e568, size=24) at /usr/local/src/xemacs-21.1/src/lstream.c:481 #17 0x80cc5cf in encoding_writer (stream=0x893bd18, data=0x880d0c0 "nnimap and Courier imapdenet-rz.(", size=24) at /usr/local/src/xemacs-21.1/src/file-coding.c:2288 #18 0x811a262 in Lstream_flush_out (lstr=0x893bd18) at /usr/local/src/xemacs-21.1/src/lstream.c:343 #19 0x811a656 in Lstream_close (lstr=0x893bd18) at /usr/local/src/xemacs-21.1/src/lstream.c:372 #20 0x811b4d1 in finalize_lstream (header=0x893bd18, for_disksave=0) at /usr/local/src/xemacs-21.1/src/lstream.c:178 #21 0x808036f in sweep_lcrecords_1 (prev=0x829e6f8, used=0xbfffe558) at /usr/local/src/xemacs-21.1/src/alloc.c:3582 #22 0x8081956 in garbage_collect_1 () at /usr/local/src/xemacs-21.1/src/alloc.c:4257 #23 0x80a9974 in funcall_recording_as (recorded_as=137462616, nargs=2, args=0xbfffe894) at /usr/local/src/xemacs-21.1/src/eval.c:3114 #24 0x80adbdd in Ffuncall (nargs=2, args=0xbfffe894) at /usr/local/src/xemacs-21.1/src/eval.c:3238 #25 0x8089b66 in Fbyte_code (bytestr=139622652, vector=141660376, maxdepth=11) at /usr/local/src/xemacs-21.1/src/bytecode.c:416 #26 0x80aa931 in funcall_lambda (fun=141797668, nargs=3, arg_vector=0xbfffeaa8) at /usr/local/src/xemacs-21.1/src/eval.c:3597 #27 0x80a9e1e in funcall_recording_as (recorded_as=141800104, nargs=3, args=0xbfffeaa4) at /usr/local/src/xemacs-21.1/src/eval.c:3214 #28 0x80adbdd in Ffuncall (nargs=4, args=0xbfffeaa4) at /usr/local/src/xemacs-21.1/src/eval.c:3238 #29 0x8089b66 in Fbyte_code (bytestr=139624812, vector=141658264, maxdepth=17) at /usr/local/src/xemacs-21.1/src/bytecode.c:416 #30 0x80aa931 in funcall_lambda (fun=141797724, nargs=3, arg_vector=0xbfffede0) at /usr/local/src/xemacs-21.1/src/eval.c:3597 #31 0x80a9e1e in funcall_recording_as (recorded_as=141800244, nargs=3, args=0xbfffeddc) at /usr/local/src/xemacs-21.1/src/eval.c:3214 #32 0x80adbdd in Ffuncall (nargs=4, args=0xbfffeddc) at /usr/local/src/xemacs-21.1/src/eval.c:3238 #33 0x8089b66 in Fbyte_code (bytestr=139892428, vector=141655720, maxdepth=15) at /usr/local/src/xemacs-21.1/src/bytecode.c:416 #34 0x80aa931 in funcall_lambda (fun=141798536, nargs=0, arg_vector=0xbffff580) at /usr/local/src/xemacs-21.1/src/eval.c:3597 #35 0x80a9e1e in funcall_recording_as (recorded_as=141699900, nargs=0, args=0xbffff57c) at /usr/local/src/xemacs-21.1/src/eval.c:3214 #36 0x80adbdd in Ffuncall (nargs=1, args=0xbffff57c) at /usr/local/src/xemacs-21.1/src/eval.c:3238 #37 0x8089b66 in Fbyte_code (bytestr=140000380, vector=141624696, maxdepth=11) at /usr/local/src/xemacs-21.1/src/bytecode.c:416 #38 0x80aa931 in funcall_lambda (fun=141798592, nargs=0, arg_vector=0xbffff6dc) at /usr/local/src/xemacs-21.1/src/eval.c:3597 #39 0x80a9e1e in funcall_recording_as (recorded_as=141798592, nargs=0, args=0xbffff6d8) at /usr/local/src/xemacs-21.1/src/eval.c:3214 #40 0x80acd3c in apply1 (fn=141798592, arg=137158436) at /usr/local/src/xemacs-21.1/src/eval.c:3238 #41 0x808b0c2 in Fcall_interactively (function=139186616, record_flag=137158436, keys=137158436) at /usr/local/src/xemacs-21.1/src/callint.c:397 #42 0x80a8b18 in Fcommand_execute (cmd=139186616, record=137158436, keys=137158436) at /usr/local/src/xemacs-21.1/src/eval.c:2584 #43 0x80db5c2 in execute_command_event (command_builder=0x833d150, event=139593444) at /usr/local/src/xemacs-21.1/src/event-stream.c:4346 #44 0x80dbc85 in Fdispatch_event (event=139593444) at /usr/local/src/xemacs-21.1/src/event-stream.c:4685 #45 0x8091dea in Fcommand_loop_1 () at /usr/local/src/xemacs-21.1/src/cmdloop.c:579 #46 0x8091faa in command_loop_1 (dummy=137158436) at /usr/local/src/xemacs-21.1/src/cmdloop.c:494 #47 0x80ad8bb in condition_case_1 (handlers=137158548, bfun=0x8091f94 <command_loop_1>, barg=137158436, hfun=0x80918f0 <cmd_error>, harg=137158436) at /usr/local/src/xemacs-21.1/src/eval.c:1653 #48 0x809207e in command_loop_2 (dummy=137158436) at /usr/local/src/xemacs-21.1/src/cmdloop.c:256 #49 0x80ad79f in internal_catch (tag=137233144, func=0x809204c <command_loop_2>, arg=137158436, threw=0x0) at /usr/local/src/xemacs-21.1/src/eval.c:1328 #50 0x8091b2c in initial_command_loop (load_me=137158436) at /usr/local/src/xemacs-21.1/src/cmdloop.c:305 #51 0x80a5581 in xemacs_21_1_12_i686_pc_linux () at /usr/local/src/xemacs-21.1/src/emacs.c:1720 #52 0x80a6bcd in main (argc=1, argv=0xbffffbc4, envp=0xbffffbcc) at /usr/local/src/xemacs-21.1/src/emacs.c:2137

1 participants
0 comments

JDE 2.1.9 checked into CVS 24 years, 3 months

Michael Sperber

Subject says it: This is a huge checkin, and I haven't tested all aspects of JDE. (I hate Java, so my exposure to it is limited to teaching.) I may have screwed up in any number of ways. The new JDE requires a new speedbar and the semantic package which I checked in a while ago. I do know there's a newer version of JDE out, but I thought I'd check in what I had now. Now that the difference between the official release and the XEmacs package is much smaller than before, further updates shouldn't be that hard. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

[comp.emacs.xemacs] Re: Xemacs 21.1.12 build problems 24 years, 3 months

Gunnar Evermann

1 participants
0 comments

[comp.emacs.xemacs] XEmacs 21.1.12 build problems 24 years, 3 months

Gunnar Evermann

Alexandre Olivia sent the following to c.e.x. Maybe one of our configure/build experts could investigate... thanks. Gunnar

1 participants
0 comments

Re: A New Package 24 years, 3 months

Steve Youngs

* Daniel Pittman <daniel(a)danann.net> writes: > *blink* Er, this may seem like a silly suggestion, but... have you > considered adding the needed UDP support to xemacs, rather than using > the external binary? No that's not a silly suggestion, but it is one that I hadn't thought of. I'll definitely give that some consideration. -- |---<Regards, Steve Youngs>-----------[GnuPG KeyID: EFD82ED2]---| | It's a funny thing about life; if you refuse to accept | | anything but the best, you very often get it | |-----------------------------<mailto:youngs_s＠ozlinx.com.au>---|

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 2000