July 1999 - XEmacs-Beta - XEmacs Mailing List Archives

tshell doesn't like "!." 25 years, 4 months

Charles G Waldman

I just discovered that if I do M-x tshell RET then type "!." at the shell prompt, XEmacs goes into an infloop that even C-g won't get me out of. Anybody else see this? 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2) Linux 2.2.10 SMP /lib/libc-2.1.1.so I'll try to work up a patch when I get enough time to study the problem.

1 participants
0 comments

Re: The plague is back: "Attempt to delete the sole visible or iconified frame" strikes again 25 years, 4 months

Jan Vroonhof

"James N. Potts" <jnpotts(a)plutonium.net> writes: > This also arises under NT (with different circumstances): > Start with a single frame. > Press the news button. > Minimize the original frame. > Click the Exit Gnus button. > > The result: "Attempt to delete the sole visible or iconified frame" Can you also reproduce this with frames created by C-x 5 2 ?, i.e. C-x 5 2 C-x 5 o (little ooo) minimize other frame C-x 5 0 (zero) Jan

1 participants
0 comments

Re: The plague is back: "Attempt to delete the sole visible or iconified frame" strikes again 25 years, 4 months

James N. Potts

This also arises under NT (with different circumstances): Start with a single frame. Press the news button. Minimize the original frame. Click the Exit Gnus button. The result: "Attempt to delete the sole visible or iconified frame" -Jim -----Original Message----- From: Hrvoje Niksic <hniksic(a)srce.hr> To: XEmacs Beta List <xemacs-beta(a)xemacs.org> Date: Monday, July 19, 1999 10:25 AM Subject: Re: The plague is back: "Attempt to delete the sole visible or iconified frame" strikes again >Kyle Jones <kyle_jones(a)wonderworks.com> writes: > >> Are you sure this is a bug? The point of the check, obviously, is >> to prevent you from being left with just unmapped frame and thus >> have no way to control the running XEmacs. > >It's a bug. I am not talking about the last XEmacs frame, but about >the last frame on any one workspace. That means that if I configure >Gnus or VM to start up in a separate frame on a different workspace, I >can't exit it without the FORCE argument. >

1 participants
0 comments

adjust gdbinit to current lrecord implementation 25 years, 4 months

Gunnar Evermann

This has been annoying me for quite some time now. Am I the only person who actually uses gdb or noticed Martin's testsuite at the end of gdbinit? :-) 1999-07-17 Gunnar Evermann <ge204(a)eng.cam.ac.uk> * gdbinit (pobj): change lrecord_foo to &lrecord_foo to match Olivier's change to lrecord.h of 1999-04-22 --- src/gdbinit.orig Sat Jul 17 19:38:21 1999 +++ src/gdbinit Sat Jul 17 19:38:30 1999 ＠＠ -228,151 +228,151 ＠＠ printf "Char: %d\n", $val end else - if $type == Lisp_Type_String || $imp == lrecord_string + if $type == Lisp_Type_String || $imp == &lrecord_string pstruct Lisp_String else - if $type == Lisp_Type_Cons || $imp == lrecord_cons + if $type == Lisp_Type_Cons || $imp == &lrecord_cons pstruct Lisp_Cons else - if $type == Lisp_Type_Symbol || $imp == lrecord_symbol + if $type == Lisp_Type_Symbol || $imp == &lrecord_symbol pstruct Lisp_Symbol printf "Symbol name: %s\n", $xstruct->name->data else - if $type == Lisp_Type_Vector || $imp == lrecord_vector + if $type == Lisp_Type_Vector || $imp == &lrecord_vector pstruct Lisp_Vector printf "Vector of length %d\n", $xstruct->size #print *($xstruct->data) ＠ $xstruct->size else - if $imp == lrecord_bit_vector + if $imp == &lrecord_bit_vector pstruct Lisp_Bit_Vector else - if $imp == lrecord_buffer + if $imp == &lrecord_buffer pstruct buffer else - if $imp == lrecord_char_table + if $imp == &lrecord_char_table pstruct Lisp_Char_Table else - if $imp == lrecord_char_table_entry + if $imp == &lrecord_char_table_entry pstruct Lisp_Char_Table_Entry else - if $imp == lrecord_charset + if $imp == &lrecord_charset pstruct Lisp_Charset else - if $imp == lrecord_coding_system + if $imp == &lrecord_coding_system pstruct Lisp_Coding_System else - if $imp == lrecord_color_instance + if $imp == &lrecord_color_instance pstruct Lisp_Color_Instance else - if $imp == lrecord_command_builder + if $imp == &lrecord_command_builder pstruct command_builder else - if $imp == lrecord_compiled_function + if $imp == &lrecord_compiled_function pstruct Lisp_Compiled_Function else - if $imp == lrecord_console + if $imp == &lrecord_console pstruct console else - if $imp == lrecord_database + if $imp == &lrecord_database pstruct Lisp_Database else - if $imp == lrecord_device + if $imp == &lrecord_device pstruct device else - if $imp == lrecord_event + if $imp == &lrecord_event pstruct Lisp_Event else - if $imp == lrecord_extent + if $imp == &lrecord_extent pstruct extent else - if $imp == lrecord_extent_auxiliary + if $imp == &lrecord_extent_auxiliary pstruct extent_auxiliary else - if $imp == lrecord_extent_info + if $imp == &lrecord_extent_info pstruct extent_info else - if $imp == lrecord_face + if $imp == &lrecord_face pstruct Lisp_Face else - if $imp == lrecord_float + if $imp == &lrecord_float pstruct Lisp_Float else - if $imp == lrecord_font_instance + if $imp == &lrecord_font_instance pstruct Lisp_Font_Instance else - if $imp == lrecord_frame + if $imp == &lrecord_frame pstruct frame else - if $imp == lrecord_glyph + if $imp == &lrecord_glyph pstruct Lisp_Glyph else - if $imp == lrecord_hash_table + if $imp == &lrecord_hash_table pstruct Lisp_Hash_Table else - if $imp == lrecord_image_instance + if $imp == &lrecord_image_instance pstruct Lisp_Image_Instance else - if $imp == lrecord_keymap + if $imp == &lrecord_keymap pstruct Lisp_Keymap else - if $imp == lrecord_lcrecord_list + if $imp == &lrecord_lcrecord_list pstruct lcrecord_list else - if $imp == lrecord_lstream + if $imp == &lrecord_lstream pstruct lstream else - if $imp == lrecord_marker + if $imp == &lrecord_marker pstruct Lisp_Marker else - if $imp == lrecord_opaque + if $imp == &lrecord_opaque pstruct Lisp_Opaque else - if $imp == lrecord_opaque_list + if $imp == &lrecord_opaque_list pstruct Lisp_Opaque_List else - if $imp == lrecord_popup_data + if $imp == &lrecord_popup_data pstruct popup_data else - if $imp == lrecord_process + if $imp == &lrecord_process pstruct Lisp_Process else - if $imp == lrecord_range_table + if $imp == &lrecord_range_table pstruct Lisp_Range_Table else - if $imp == lrecord_specifier + if $imp == &lrecord_specifier pstruct Lisp_Specifier else - if $imp == lrecord_subr + if $imp == &lrecord_subr pstruct Lisp_Subr else - if $imp == lrecord_symbol_value_buffer_local + if $imp == &lrecord_symbol_value_buffer_local pstruct symbol_value_buffer_local else - if $imp == lrecord_symbol_value_forward + if $imp == &lrecord_symbol_value_forward pstruct symbol_value_forward else - if $imp == lrecord_symbol_value_lisp_magic + if $imp == &lrecord_symbol_value_lisp_magic pstruct symbol_value_lisp_magic else - if $imp == lrecord_symbol_value_varalias + if $imp == &lrecord_symbol_value_varalias pstruct symbol_value_varalias else - if $imp == lrecord_toolbar_button + if $imp == &lrecord_toolbar_button pstruct toolbar_button else - if $imp == lrecord_tooltalk_message + if $imp == &lrecord_tooltalk_message pstruct Lisp_Tooltalk_Message else - if $imp == lrecord_tooltalk_pattern + if $imp == &lrecord_tooltalk_pattern pstruct Lisp_Tooltalk_Pattern else - if $imp == lrecord_weak_list + if $imp == &lrecord_weak_list pstruct weak_list else - if $imp == lrecord_window + if $imp == &lrecord_window pstruct window else - if $imp == lrecord_window_configuration + if $imp == &lrecord_window_configuration pstruct window_config else echo Unknown Lisp Object type\n -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

2 participants
1 comments

Re: The plague is back: "Attempt to delete the sole visible or iconified frame" strikes again 25 years, 4 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > It's a bug. I am not talking about the last XEmacs frame, but about > the last frame on any one workspace. That means that if I configure > Gnus or VM to start up in a separate frame on a different workspace, I > can't exit it without the FORCE argument. It's a bug, but is in the window manager as far as I am concerned. Jan

1 participants
0 comments

Re: The plague is back: "Attempt to delete the sole visible or iconified frame" strikes again 25 years, 4 months

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Kyle Jones <kyle_jones(a)wonderworks.com> writes: > > > Are you sure this is a bug? The point of the check, obviously, is > > to prevent you from being left with just unmapped frame and thus > > have no way to control the running XEmacs. > > It's a bug. I am not talking about the last XEmacs frame, but about > the last frame on any one workspace. That means that if I configure > Gnus or VM to start up in a separate frame on a different workspace, I > can't exit it without the FORCE argument. Still, it's not a bug in XEmacs, but rather a misconception of the X Windows' states[1] and the way window managers achieve their desired effect. Basically, what happens is that a window on another desktop is really unmapped in the X sense, and XEmacs has no way to know that this window can be visible again (thanks to a WM command). In the best situation, some window managers will supply more information through a specific communication protocol, which means that if we want to improve XEmacs' concept of window states, we'll have to write specific code for all window managers on earth. In the worst case, some window managers won't give you any information. For them, it will be impossible to fix the problem you describe. Footnotes: [1] To be honest, at the time X was written, there was probably no concept of workspace yet. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Re: The plague is back: "Attempt to delete the sole visible or iconified frame" strikes again 25 years, 4 months

Hrvoje Niksic

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Are you sure this is a bug? The point of the check, obviously, is > to prevent you from being left with just unmapped frame and thus > have no way to control the running XEmacs. It's a bug. I am not talking about the last XEmacs frame, but about the last frame on any one workspace. That means that if I configure Gnus or VM to start up in a separate frame on a different workspace, I can't exit it without the FORCE argument.

1 participants
0 comments

Re: Putting it all together 25 years, 4 months

Jan Vroonhof

Andy Piper <andy(a)xemacs.org> writes: > This patch fixes a few errors in my gutter and widget support and combine > everything to provide tabbed buffers on devices that support tabbed widgets > (i.e. only mswindows currently). I didn't look in depth at it yet, but the doc strings for the gutter tab items still contain references to the buffer menus. Jan P.S. Does anybody know a free Xt based toolkit that has all these modern widgets?

3 participants
5 comments

buffer.h is screwed w/no error checking 25 years, 4 months

Neal D. Becker

INC_CHARBYTIND is not defined if --error-checking=none in the latest CVS.

2 participants
1 comments

Re: Putting it all together 25 years, 4 months

Jan Vroonhof

Andy Piper <andy(a)xemacs.org> writes: > Well LessTif has all but Tab control and Tree view. Ben thinks that I > should write a tab control for lwlib but I'm not sure I am sufficiently > motivated (or able). Doing the Motif stuff was bad enough without building > my own toolkit. I have to address Steve's concerns still as well. There seem to be a pure Xt tab widget at http://www.best.com/~falconer/Widgets/ Jan

3 participants
3 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 July 1999