January 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: gnuclient's immediate exit 24 years, 9 months

Hrvoje Niksic

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > >> But if I just say "gnuclient", it exits as soon as the frame > >> appears. > > Hrvoje> That's a feature. > > But gnuclient -nw also exits immediately, albeit for a different > reason: Obviously, that's a bug. Aaaaandyyyy! :-)

2 participants
1 comments

More on AIX C preprocessor lossage 24 years, 9 months

Valdis Kl=?iso8859-4?Q?=BA?=tnieks

I've narrowed it down to this line in lwlib/config.h tickling the bug: #define ATHENA_H_PATH X11/Xaw The code preprocesses fine if that #define doesn't have a / in it (but of course then loses because it can't fine the header files. I'm about to report this to IBM. The truly bizzare part is this exposed ANOTHER preproccesor bug - the code would expand into *asking* for "#include <X11/Xaw/whatever.h>", but what would get *included* was "#include <X11>". It quit after the /. And yes, the preprocessor would happily suck in the directory. Gaak. I've already reported that one. /Valdis

2 participants
1 comments

[PATCH] Last assault on binary-process-output 24 years, 9 months

Kirill 'Big K' Katsnelson

This might break packages which expect NTEmacs variable binary-process-output to do things. Packages in XEmacs sumo tarball are clear, please test 3rd party packages which you are using. The correct fix is: Whenever a construct (let ((binary-process-output t)) ... ) is used, add one more binding: (let ((binary-process-output t) (coding-system-for-read 'binary)) ... ) This way, old compatibility is not broken and XEmacs compatibility is restored. I'll delete the code and definitions unless it is going to break an overwhelming number of packages (I do not believe but I made this change in a revertable way). NT testers please give your feedback soon if possible. Big K 2000-01-26 Kirill 'Big K' Katsnelson <kkm(a)dtmx.com> * callproc.c (Fcall_process_internal): Ignore Vbinary-process_output. Index: callproc.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/callproc.c,v retrieving revision 1.29.2.11 diff -u -r1.29.2.11 callproc.c --- callproc.c 2000/01/24 07:36:19 1.29.2.11 +++ callproc.c 2000/01/26 21:33:08 ＠＠ -501,16 +501,19 ＠＠ if (nread == 0) break; +#if 0 #ifdef DOS_NT /* Until we pull out of MULE things like make_decoding_input_stream(), we do the following which is less elegant. --marcpa */ + /* We have pulled them out. -- kkm */ { int lf_count = 0; if (NILP (Vbinary_process_output)) { nread = crlf_to_lf(nread, bufptr, &lf_count); } } +#endif #endif total_read += nread;

1 participants
0 comments

Xemacs version 21.1.8 Bug in CDE 24 years, 9 months

Magnant, James A

Under the older version of Xemacs (20.3), I am able to set my CDE desktop session preferences so that Xemacs starts in a particular session "screen" in lieu of the "screen" selected at the time it pops up. In addition, the CDE home session preferences allow specifying the Xemacs window geometry. These settings are stored in the $HOME/user_name/.dt/sessions/home/dt.session file. Using Version 21.1.8, Xemacs does not honor the style manager's "home session" settings. Xemacs21 pops up in whatever "screen" the user has selected at the time the window activates. Please advise work-around or open bug for future fix. I have included my dt.session file for your review. Thanks, Jim Magnant Filename: dt.session dtsmcmd -hints "-geometry 1x1+0+0 -state NormalState -cmd \"dtfile -session dt01MxQP \"" -screen 0 -cmd "dtfile -session dt01MxQP" dtsmcmd -hints "-geometry 0x13+253+961 -state NormalState -workspaces \"ws2 ws0 ws1 ws3 \" -cmd \"/usr/openwin/bin/clock -Wp 247 936 -Ws 132 59 -WP 8 11 +Wi +Wn -12 -digital -date +seconds -alarmtime 0:0 \"" -screen 0 -cmd "/usr/openwin/bin/clock -Wp 247 936 -Ws 132 59 -WP 8 11 +Wi +Wn -12 -digital -date +seconds -alarmtime 0:0" dtsmcmd -hints "-geometry 105x180+500+175 -state IconicState -workspaces \"ws3 ws0 ws1 ws2 \" -cmd \"/usr/openwin/bin/cm -Wp 494 150 -Ws 485 440 -WP 200 946 -Wi \"" -screen 0 -cmd "/usr/openwin/bin/cm -Wp 494 150 -Ws 485 440 -WP 200 946 -Wi" dtsmcmd -hints "-geometry 1x1+0+0 -state NormalState -cmd \"dtterm -session dtR9OHN_ -sl 100s -name BigTerm -title Long\ Scrollback\ Terminal \"" -screen 0 -cmd "dtterm -session dtR9OHN_ -sl 100s -name BigTerm -title Long\ Scrollback\ Terminal" dtsmcmd -hints "-geometry 1x1+0+0 -state NormalState -cmd \"dtterm -session dt0uYYu8 -bg darkgreen -fg white -sl 100s -ls -C -name Console -title Long\ Scrollback\ Console \"" -screen 0 -cmd "dtterm -session dt0uYYu8 -bg darkgreen -fg white -sl 100s -ls -C -name Console -title Long\ Scrollback\ Console" dtsmcmd -hints "-geometry 1x1+0+0 -state NormalState -cmd \"dtterm -session dtkl9Mu_ -sl 100s -name BigTerm -title Long\ Scrollback\ Terminal \"" -screen 0 -cmd "dtterm -session dtkl9Mu_ -sl 100s -name BigTerm -title Long\ Scrollback\ Terminal" dtsmcmd -hints "-geometry 1x1+0+0 -state NormalState -cmd \"dtterm -session dtbympd_ -sdtserver \"" -screen 0 -cmd "dtterm -session dtbympd_ -sdtserver" dtsmcmd -hints "-geometry 195x60+6+959 -state NormalState -workspaces \"ws0 ws1 ws2 ws3 \" -cmd \"/apps/shared/xmcd/xmcd -xrm *iconX:2 -xrm *iconY:5 \"" -screen 0 -cmd "/apps/shared/xmcd/xmcd -xrm *iconX:2 -xrm *iconY:5" dtsmcmd -hints "-geometry 80x61+687+28 -state NormalState -cmd \"xemacs-21.1.8 -geometry 80x61+687+28 \"" -screen 0 -cmd "xemacs-21.1.8 -geometry 80x61+687+28" --=-=-=--

1 participants
0 comments

Re: Windows native version of "makeinfo.exe"? 24 years, 9 months

Fabrice Popineau

* Damon Lipparelli <lipp(a)primus.com> writes: > Does anyone have a NT native version of "makeinfo.exe"? I'm having > trouble building the latest version of "man/xemacs-faq.texi" with > XEmacs itself. Yes, I can send it if you want. Fabrice

1 participants
0 comments

Crash in xemacs-21.2-b27 -vanilla -eval 24 years, 9 months

Nick V. Pakoulin

>From command line : ------------------------------------------------------------------------------- hookah : npakoulin >$ xemacs-21.2-b27 -vanilla -eval XEmacs: Option `-eval' requires an argument Segmentation fault (core dumped) ------------------------------------------------------------------------------- uname -a: Linux hookah 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 i686 unknown ./configure '--with-pop' '--error-checking=none' XEmacs 21.2-b27 "Hera" configured for `i686-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.2.27 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 Athena library to link: Xaw Athena header include path: X11/Xaw 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 Enlightened Sound Daemon (ESD). Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid 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. Using POP for mail access. Compiling in extra code for debugging. ------------------------------------------------------------------------------- hookah : npakoulin >$ gdb /usr/local/bin/xemacs-21.2-b27 core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... Core was generated by `xemacs-21.2-b27 -vanilla -eval'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/X11R6/lib/libXaw.so.6...done. Reading symbols from /usr/lib/libtiff.so.3...done. Reading symbols from /usr/lib/libpng.so.2...done. Reading symbols from /usr/lib/libjpeg.so.62...done. Reading symbols from /usr/lib/libz.so.1...done. Reading symbols from /usr/X11R6/lib/libXpm.so.4...done. Reading symbols from /usr/X11R6/lib/libXmu.so.6...done. Reading symbols from /usr/X11R6/lib/libXt.so.6...done. Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Reading symbols from /usr/X11R6/lib/libSM.so.6...done. Reading symbols from /usr/X11R6/lib/libICE.so.6...done. Reading symbols from /lib/libdl.so.2...done. Reading symbols from /lib/libdb.so.3...done. Reading symbols from /usr/lib/libgpm.so.1...done. Reading symbols from /usr/lib/libncurses.so.4...done. Reading symbols from /usr/lib/libesd.so.0...done. Reading symbols from /usr/lib/libaudiofile.so.0...done. Reading symbols from /lib/libm.so.6...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. #0 0x40319dcc in chunk_free (ar_ptr=0x656b616d, p=0x83d3000) at malloc.c:2987 2987 malloc.c: No such file or directory. (gdb) where #0 0x40319dcc in chunk_free (ar_ptr=0x656b616d, p=0x83d3000) at malloc.c:2987 #1 0x40319d75 in __libc_free (mem=0x83d3008) at malloc.c:2959 #2 0x402e19fe in exit (status=1) at exit.c:65 #3 0x807665d in fatal (fmt=0x8162500 "Option `%s' requires an argument\n") at emacs.c:295 #4 0x80774ae in sort_args (argc=3, argv=0xbffffb24) at emacs.c:2037 #5 0x807687f in xemacs_21_2_b27_i686_pc_linux (argc=3, argv=0xbffffb24, envp=0xbffffb34, restart=0) at emacs.c:591 #6 0x8078c0f in main (argc=3, argv=0xbffffb24, envp=0xbffffb34) at emacs.c:2331 #7 0x402d91eb in __libc_start_main (main=0x8078b10 <main>, argc=3, argv=0xbffffb24, init=0x804dbf8 <_init>, fini=0x815cb00 <_fini>, rtld_fini=0x4000a610 <_dl_fini>, stack_end=0xbffffb1c) at ../sysdeps/generic/libc-start.c:90 ------------------------------------------------------------------------------- Nick.

1 participants
0 comments

Re: gnuclient's immediate exit 24 years, 9 months

Karl Kleinpaste

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > I was under the impression that what Karl describes is that `gnuclient > FILE' exits immediately, which is a bug. No, the problem is evidently what was just observed by Michael, about the tab instantiator error; I just hadn't gotten as far as peeking into the returned buffer. In any event, "gnuclient -nw" should not (and, now looking at the code more carefully, would not) exit immediately, because in the -nw case, gnuclient does not ship across the 'quick qualifier on the gnuserv-edit-files directive. The really perverse situation is that, in the -nw case of immediate departure, XEmacs tries to retain control of the tty anyhow. I was in fact exploiting this with "gnuclient ; sleep 1000000" so that XEmacs didn't conflict with my shell. I suspect that a tweak to XEmacs is in order, to force giving up control of the client tty in the case of any gnuserv-edit-files error return.

2 participants
1 comments

Re: gnuclient's immediate exit 24 years, 9 months

Hrvoje Niksic

"Kevin Oberman" <oberman(a)es.net> writes: > I have seen this behavior for some time, at least for all XEmacs 21 > releases and maybe before that. If I do "gnuclient FILE", gnuclient > waits for the frame to close before terminating. But if I just say > "gnuclient", it exits as soon as the frame appears. That's a feature. I was under the impression that what Karl describes is that `gnuclient FILE' exits immediately, which is a bug.

1 participants
0 comments

Re: the culprit is zmacs-regions 24 years, 9 months

Hrvoje Niksic

"T. V. Raman" <ramantv(a)earthlink.net> writes: > thanks for everyone's help. AT present the only way I am able to > get things working is to use Colin's "evil" solution of setting > zmacs-regions to nil. That is evil (no quotes I'm afraid) because it overrides the user's settings. If I knew what exactly the problem was, I might be able to help you. This way I can just guess. Let's recapitulate: * In XEmacs, the term "active region" pertains to zmacs regions. They are on by default. If you set zmacs-regions to nil, you kill all zmacs region behaviour -- (mark) always returns the last location of mark, etc. * The functions (point) and (mark) return the endpoints of a zmacs region. If the region is currently not active, (mark) returns nil. If you really really want to know where the mark was last located, use (mark t). * A better (less confusing) interface for using regions are functions `region-active-p', `region-beginning', and `region-end'. * All the commands deactivate the region except for those that explicitly choose not to. This is by design. > Any other suggestions? Setting zmacs-region-stays at the end of > every emacspeak function would be a huge amount of work -- Not at the end of every emacspeak function, but only at the end of those commands that really need to preserve the region. If every emacspeak function is a movement command then yes, every one of them needs to preserve the region. But somehow I doubt that this is the case. Could you be a bit more specific with the problem description?

1 participants
0 comments

Crash in update_frame_gutters 24 years, 9 months

Kirill 'Big K' Katsnelson

I have been working for some time before it crashed on me. I had a variable help window open, (C-h v ...), and pressed q to close it, and XEmacs crashed. I think, but am not sure, that before bringing up the help I had only one window in the frame. Relevant top of stack trace was: get_builtin_face_cache_index(window * 0x01e5a600, long 28332160) line 1335 + 30 bytes output_gutter(frame * 0x01b90a00, int 0) line 227 + 16 bytes update_frame_gutters(frame * 0x01b90a00) line 356 + 13 bytes redisplay_frame(frame * 0x01b90a00, int 0) line 6358 + 9 bytes redisplay_device(device * 0x01d98f00, int 1) line 6471 + 11 bytes redisplay_without_hooks() line 6560 + 11 bytes redisplay() line 6623 Fnext_event(long 33008984, long 28360708) line 2238 Fcommand_loop_1() line 566 + 16 bytes Current line was: for (elt = 0; elt < Dynarr_length (w->face_cachels); elt++) Select members of the w structure were: w->face_cachels: 0 w->pixel_top: 380 w->pixel_left: 0 w->pixel_height: 344 w->pixel_width: 578 w->mini_p: (Qnil) w->next: (Qnil) w->prev: (Qnil) w->parent: (Qnil) w->dead: 1 It looks like FRAME_LAST_NONMINIBUF_WINDOW in output_gutter picked the dead window. I could not track this any further right now. Big K

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 January 2000