March 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Can't install packages produced on WindowsNT 24 years, 1 month

Adrian Aichner

Hello All, I don't know what this is yet: I used to be able to build private packages under Windows NT and install them using pui. Just tried that again today and failed. Both 21.1.9 and 21.2-b32 report incorrect md5 checksums. I suspect (insert-file-contents-internal ...) vs. (insert-file-contents ...) being used in package-get.el at this point. The .el files of my packages contain CRLF as they are written on Windows NT. This seems to be exposing the problem. Any ideas, pointers, etc? Best regards, Adrian

1 participants
0 comments

Re: Steve's 21.2.32 crashes 24 years, 1 month

Didier Verna

I wrote: > Andy Piper <andy(a)xemacs.org> wrote: > > > I can't commit right now and xrdb doesn't work on my broken windows system. > > Can you try the attached patch which I think clears up the brokeness I > > introduced earlier (but may not fix your problem). > > That fixes the crash (I was also experimenting) for me. However, I still get a similar (I think) crash when running in -nw mode (crash not reproducible with -vanilla): -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

1 participants
0 comments

Re: 'kill-region' replaces primary selection? 24 years, 1 month

Daniel Pittman

On Fri, 24 Mar 2000, Kyle Jones <kyle_jones(a)wonderworks.com> wrote: > Dmitry Yaitskov writes: > > New users with "Windows background" (and that's the majority of > > users now) will certainly (IMHO :) expect the yank/kill operations > > to interact with clipboard. > > Every time I read something like this I think of Abraham putting > the knife to Isaac's throat. I think of Yoda saying "Once you > start down the dark path, forever will it dominate your destiny. > Consume you it will!" I think of the French with their holding > actions against the English language infestation. And I despair. I think you overstate the case a touch. In any case, might it be possible to (fear and terror) have the default be the typical default for the platform: Under Win32, they do interact. Under Unix, they do not. Incidentally, under Win32, the action of deleting text does not modify the clipboard content at all. The UI guidelines, I believe, even specify this as a requirement... Daniel -- We had the experience but missed the meaning. -- T.S. Eliot, _The Dry Salvages_

1 participants
0 comments

Re: 'kill-region' replaces primary selection? 24 years, 1 month

Dmitry Yaitskov

New users with "Windows background" (and that's the majority of users now) will certainly (IMHO :) expect the yank/kill operations to interact with clipboard. Daniel Pittman <daniel(a)danann.net> wrote: > On 20 Mar 2000, Jan Vroonhof <vroonhof(a)math.ethz.ch> wrote: > > > "Daniel Pittman" <daniel(a)danann.net> writes: > > > >> I believe this is a fairly recent change in XEmacs behavior. > >> 'kill-word' currently replaces the primary selection with the killed > >> word, where previously (circa b29, I think) the primary selection was > >> left alone. > > > > It is new functionality. Try toggling > > "Options->Keyboard and Mouse->Yank/kill interact with clipboard". > > > > Do you mind this being the default? > > Thanks for the pointer. > > As to being the default, hmm. I think that the primary selection and the > kill ring are logically separate things, so I don't expect the two to > interact. > > I don't know what would be best for new users though. I don't think it > will be what most people expect. On that basis I would say turn it off > by default. > > In the end, though, I just don't really mind much (as long as I can set > my own preference :) > > Daniel -- Cheers, -Dima.

2 participants
1 comments

I was trying to exit when... 24 years, 1 month

Matthew Persico

--text follows this line-- This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.2 (beta32) "Kastor & Polydeukes" [Lucid] (sparc-sun-solaris2.6) of Tue Mar 21 2000 on amdev01 configured using `configure --site-includes=/opt/local_dev/include --site-libraries=/opt/local_dev/lib --dynamic --prefix=/opt/local_dev/xemacs-21.2.32 --with-xpm --with-tooltalk --with-sparcworks --with-gcc=no --with-xface' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: All I was donig was CxCc to exit... Lisp backtrace follows: kill-emacs() # bind (arg) save-buffers-kill-emacs(nil) # bind (command-debug-status) call-interactively(save-buffers-kill-emacs) # (condition-case ... . error) # (catch top-level ...) persicom＠amdev01 /home/amgdev/scripts/pm/AMG/Utils/work [209] $ dbx /opt/local_dev/xemacs-21.2.32/bin/xemacs core dbx: warning: cannot find global initialization file: dbxrc Reading symbolic information for xemacs core file header read successfully Reading symbolic information for rtld /usr/lib/ld.so.1 dbx: program is not active Reading symbolic information for libXm.so.3 Reading symbolic information for libtiff.so Reading symbolic information for libz.so Reading symbolic information for libXpm.so.4.11 Reading symbolic information for libtt.so.2 Reading symbolic information for libXmu.so.4 Reading symbolic information for libXt.so.4 Reading symbolic information for libXext.so.0 Reading symbolic information for libX11.so.4 Reading symbolic information for libdl.so.1 Reading symbolic information for libkstat.so.1 Reading symbolic information for libsocket.so.1 Reading symbolic information for libnsl.so.1 Reading symbolic information for libc.so.1 Reading symbolic information for libSM.so.6 Reading symbolic information for libICE.so.6 Reading symbolic information for libm.so.1 Reading symbolic information for libmp.so.2 Reading symbolic information for libc_psr.so.1 Reading symbolic information for nss_files.so.1 Reading symbolic information for nss_compat.so.1 Reading symbolic information for nss_nis.so.1 Reading symbolic information for straddr.so program terminated by signal BUS (Bus Error) (dbx 1) where =>[1] _kill(0x0, 0xa, 0x43981c, 0x0, 0xef1a2eb4, 0xc2830), at 0xef18800c [2] fatal_error_signal(0x5e05e8, 0x5e05dc, 0x40c400, 0x439804, 0x40c000, 0x3fac00), at 0xc2830 ---- called from signal handler with signal 10 (SIGBUS) ------ [3] RemoveMatchingEntries(), at 0xef6cd49c [4] _XmEnumerateHashTable(0x736a00, 0xef6cd520, 0x6b1000, 0xef788fc8, 0x134, 0x4d), at 0xef680294 [5] CleanupOnDisplayClose(0x6c6e00, 0xef780a4c, 0xef778434, 0xef6cd540, 0x18, 0x1), at 0xef6cd5d4 [6] XtCallCallbackList(0x6c6e00, 0x75e340, 0x0, 0x0, 0x0, 0x0), at 0xef41f99c [7] XtPhase2Destroy(0x6c6e00, 0xffffffff, 0x0, 0xef47016c, 0x73cba0, 0x0), at 0xef428200 [8] _XtDoPhase2Destroy(0x488800, 0x0, 0x0, 0x0, 0x0, 0x1), at 0xef428418 [9] XtDestroyWidget(0x6b0400, 0xef47016c, 0x488800, 0x1, 0x1f38, 0x29a), at 0xef428628 [10] x_delete_device(0x5f3800, 0x40c390, 0x3c7104, 0x3c70f8, 0x6b1000, 0x628880), at 0x2be710 [11] delete_device_internal(0x40c400, 0x40c610, 0x439804, 0x0, 0x406850, 0x439804), at 0xaacd0 [12] delete_console_internal(0x406850, 0x40c610, 0x0, 0x6d0a08, 0x5f3800, 0x0), at 0x9a34c [13] Fkill_emacs(0x628880, 0x40c610, 0x439804, 0x6d0954, 0x1, 0x439804), at 0xc4d4c [14] Ffuncall(0x40c610, 0x401ab8, 0x412f3c, 0x4015e8, 0x3fae38, 0x3fac00), at 0xe39a0 [15] execute_optimized_program(0x59de90, 0x4015e8, 0x40c610, 0x412f3c, 0xefffe204, 0xefffe1f0), at 0x8345c [16] funcall_compiled_function(0x4015e8, 0xbcbb80, 0x2, 0x412f3c, 0x59de80, 0x4), at 0x82ca4 [17] Ffuncall(0x40c610, 0x401ab8, 0x412f3c, 0x4015e8, 0x3fae38, 0x3fac00), at 0xe3f50 [18] Fcall_interactively(0x40c610, 0x4068a8, 0x40d000, 0xefffe514, 0x1, 0xefffe518), at 0x8b758 [19] Fcommand_execute(0x405c00, 0x401400, 0x439804, 0x0, 0x59849c, 0x439804), at 0xdfb2c [20] execute_command_event(0x64c2c0, 0xbefabc, 0xbefabc, 0x40c400, 0x406800, 0x0), at 0x13ec60 [21] Fdispatch_event(0xbefabc, 0x40c610, 0x0, 0x0, 0x14, 0x628880), at 0x13fd6c [22] Fcommand_loop_1(0x401800, 0x0, 0x40c400, 0x0, 0x8bea00, 0xb3a088), at 0x955e8 [23] condition_case_1(0x3fac00, 0x40c800, 0x406800, 0x944b8, 0x439804, 0x0), at 0xd1a3c [24] command_loop_2(0x40c610, 0x946ac, 0xefffe820, 0xefffeae0, 0x73, 0xefffec33), at 0x946f4 [25] internal_catch(0x44bfe4, 0x946ac, 0x439804, 0x0, 0x2f, 0x4943a4), at 0xd06e8 [26] initial_command_loop(0x406400, 0x405b08, 0x628880, 0x494398, 0x1, 0x40c610), at 0x94af0 [27] xemacs_21_2_b32_sparc_sun_solaris2_6(0x5, 0x433400, 0x439804, 0xefffec10, 0x602274, 0xefffee94), at 0xc42a4 [28] main(0x5, 0xefffee94, 0xefffeeac, 0x3ea400, 0x0, 0x0), at 0xc4b7c (dbx 2)

1 participants
0 comments

another 21.2.32/VM crash 24 years, 1 month

John A. Turner

here's another... looks similar to the others... environment as in: http://www.xemacs.org/list-archives/xemacs-beta/200003/msg00021.html results of debug_backtrace() included after the C stack, but I'm not sure it's useful... Program received signal SIGSEGV, Segmentation fault. GetToken () at Shell.c:3256 3256 Shell.c: No such file or directory. (gdb) where #0 GetToken () at Shell.c:3256 #1 0x1026deb8 in x_map_subwindow (p=0x10b7d800, x=0, y=0, dga=0x7fff1dd8) at glyphs-x.c:2153 #2 0x1016e44c in map_subwindow (subwindow=280483840, x=0, y=0, dga=0x7fff1dd8) at glyphs.c:4466 #3 0x10202bc8 in redisplay_output_subwindow (w=0x10b5cc00, image_instance=280483840, db=0x7fff1e90, dga=0x7fff1ea0, findex=12, cursor_start=0, cursor_width=0, cursor_height=0) at redisplay-output.c:1255 #4 0x10278554 in x_output_display_block (w=0x10b5cc00, dl=0x109a7400, block=0, start=0, end=1, start_pixpos=0, cursor_start=0, cursor_width=0, cursor_height=0) at redisplay-x.c:483 #5 0x102026ec in redisplay_output_display_block (w=0x10b5cc00, dl=0x109a7400, block=0, start=0, end=1, start_pixpos=0, cursor_start=0, cursor_width=0, cursor_height=0) at redisplay-output.c:1138 #6 0x102011e0 in output_display_line (w=0x10b5cc00, cdla=0x10ae4080, ddla=0x10ae4dc0, line=0, force_start=-1, force_end=-1) at redisplay-output.c:798 #7 0x1018e038 in output_gutter (f=0x10a4ec00, pos=TOP_GUTTER, force=1) at gutter.c:314 #8 0x1018fa60 in redraw_exposed_gutter (f=0x10a4ec00, pos=TOP_GUTTER, x=0, y=0, width=590, height=665) at gutter.c:568 #9 0x1018fbc0 in redraw_exposed_gutters (f=0x10a4ec00, x=0, y=0, width=590, height=665) at gutter.c:579 #10 0x1027d190 in x_redraw_exposed_area (f=0x10a4ec00, x=0, y=0, width=590, height=665) at redisplay-x.c:1795 #11 0x1025a43c in emacs_Xt_handle_magic_event (emacs_event=0x10b531d4) at event-Xt.c:1770 #12 0x10103178 in event_stream_handle_magic_event (event=0x10b531d4) at event-stream.c:527 #13 0x10109e24 in execute_internal_event (event=280310228) at event-stream.c:3041 #14 0x1010d044 in Fdispatch_event (event=280310228) at event-stream.c:4208 #15 0x100768d8 in Fcommand_loop_1 () at cmdloop.c:575 #16 0x1007653c in command_loop_1 (dummy=272336900) at cmdloop.c:490 #17 0x100acf94 in condition_case_1 (handlers=272336996, bfun=0x100764ec <command_loop_1>, barg=272336900, hfun=0x100758b0 <cmd_error>, harg=272336900) at eval.c:1644 #18 0x10075ad8 in command_loop_3 () at cmdloop.c:252 #19 0x10075b48 in command_loop_2 (dummy=272336900) at cmdloop.c:263 ---Type <return> to continue, or q <return> to quit--- #20 0x100ac818 in internal_catch (tag=272412644, func=0x10075b14 <command_loop_2>, arg=272336900, threw=0x0) at eval.c:1310 #21 0x10075e80 in initial_command_loop (load_me=272336900) at cmdloop.c:301 #22 0x100a5344 in xemacs_21_2_b31_mips_sgi_irix6_5 (argc=1, argv=0x7fff2e34, envp=0x7fff2e3c, restart=0) at emacs.c:1872 #23 0x100a6678 in main (argc=1, argv=0x7fff2e34, envp=0x7fff2e3c) at emacs.c:2291 (gdb) ldb Undefined command: "ldb". Try "help". (gdb) lbt (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. GetToken () at Shell.c:3256 3256 in Shell.c (gdb) lbt (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. GetToken () at Shell.c:3256 3256 in Shell.c (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. kill () at engine.c:648 648 engine.c: No such file or directory. (gdb) lbt Program received signal SIGSEGV, Segmentation fault. 0x101d5a3c in debug_backtrace () at print.c:1668 1668 int old_print_readably = print_readably; The program being debugged stopped while in a function called from GDB. When the function (debug_backtrace) is done executing, GDB will silently stop (instead of continuing to evaluate the expression containing the function call). (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x101d5a3c in debug_backtrace () at print.c:1668 1668 int old_print_readably = print_readably; (gdb) lbt (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x101d5a3c in debug_backtrace () at print.c:1668 1668 int old_print_readably = print_readably; (gdb) cont Continuing. Program terminated with signal SIGSEGV, Segmentation fault. -- John A. Turner, Senior Research Associate Blue Sky Studios, One South Rd, Harrison, NY 10528 http://www.blueskystudios.com/ (914) 825-8319

2 participants
3 comments

Re: W3 vs. browse-url.el 24 years, 1 month

Matt Curtin

>>>>> "Charles" == Charles G Waldman <cgw(a)fnal.gov> writes: Charles> In the case that that browser is W3, even if the file is a Charles> valid HTML document, the source rather than formatted HTML Charles> is shown. This doesn't happen for me. I actually see the formatted HTML. I'm using XEmacs 21.1.8 and w3 version 1.10 under Solaris/sparc 2.6. -- Matt Curtin cmcurtin(a)interhack.net http://www.interhack.net/people/cmcurtin/

2 participants
1 comments

cannot start beta32 24 years, 1 month

Colin Rafferty

Well, under certain circumstances. I guessed what the problem was from the error message. I have internalBorderWidth set to 0 in my resources, because I like to have as much desktop space as possible. 21.2beta28 didn't mind this. In fact, I've been using it for years. Now, 21.2beta32 doesn't like this at all. Here is an example of running XEmacs from the shell: sag3 $ echo 'Emacs*internalBorderWidth: 0' | xrdb -merge sag3 $ DISPLAY=malaria:0.0 src/xemacs Error: Widget clip-window has zero width and/or height sag3 $ echo 'Emacs*internalBorderWidth: 2' | xrdb -merge sag3 $ src/xemacs sag3 $ As you can see, a positive internalBorderWidth works just fine, but zero no longer works. Unfortunately, I cannot find this text anywhere in the code, so I am having a very hard time tracking it down. -- Colin

2 participants
2 comments

W3 vs. browse-url.el 24 years, 1 month

Charles G Waldman

Suppose you have some HTML text in a buffer which is not visiting a file, or embedded in another (non-html) file. In this case, the functions "browse-url-of-buffer" and "browse-url-of-region" will generate a temporary file and pass a file url to the browser of choice. In the case that that browser is W3, even if the file is a valid HTML document, the source rather than formatted HTML is shown. This seems to be happening because the temporary filename does not have a .html extension. In Netscape, even without the .hmtl, a formatted document, rather than source, is shown. Apparently Netscape sees the <html> header and decides the document is HTML, regardless of file extension. Kludging browse-url.el to append ".html" to the temporary file name causes formatted HTML to be shown... however this kludge hardly seems like the Right Thing. But, I can't really see in this situation what the Right Thing would be. Should "browse-url" look for a <html> or <HTML> tag in the document and generate a temp file name with .html extension in this case? Is this too crufty? (PS. I noticed this trying to use a package called PyLibLookup; you press a key and the Python Library documentation for the function at point is shown in a web-browser, courtesy of browse-url. A subprocess generates the html into a temporary buffer and calls browse-url-of-buffer. Works great with Netscape, shows HTML source when using W3).

1 participants
0 comments

More glyph/gutter/progress fixes 24 years, 1 month

Andy Piper

This significantly robustifies the progress gauge and friends. I have disabled the quit button for now since processing events for this causes too many problems. I have a better solution in mind. I also cannot reproduce the crash I was having under X. I would be interested if John Turner's crashes still occur (I assume yes since I haven't fixed anything that makes me think they would be gone). I also need to know if Steve's crashes occur with this since the fix I have actually applied to glyphs.c is different to the one I posted a couple of days ago. Ben's claim about hashing was prophetic as it turns out ..... andy 2000-03-24 Andy Piper <andy(a)xemacs.org> * gutter-items.el (add-tab-to-gutter): use copy-sequence. (abort-progress-display): ditto. Don't delete the created extent. (raw-append-progress-display): ditto. (progress-display-dispatch-non-command-events): new function. Encapsulates what we want to do when no command input is required. (progress-display-dispatch-command-events): likewise, but disable for now since it causes too many problems. (append-progress-display): use them. (raw-append-progress-display): ditto. (default-gutter-position-changed-hook): set this rather than default-gutter-position-changed. (default-gutter-position-changed-hook): lambda with zero arguments rather than one. (raw-append-progress-display): trap errors in pending input since allowing them to signal will hose the gauge well and truly. Ideally we would like to delay these until we are more able to cope. (append-progress-display): ditto. 2000-03-24 Andy Piper <andy(a)xemacs.org> * redisplay-output.c (compare_runes): use image_instance_changed to detect changes. Do not depend on glyphs_changed, only depend on dirtiness. (redisplay_output_layout): add debug messages. (compare_runes): ditto. * glyphs.h: declare new functions. (struct Lisp_Image_Instance): remove percent and associated accessors. * gui.h: declare new copying functions. * gui.c (copy_gui_item_tree): new function. (copy_gui_item): new function. (gui_item_id_hash): revert to standard hash. (gui_item_hash): ditto. (gui_item_hash_internal): deleted. (mark_gui_item): mark value. (gui_item_add_keyval_pair): add value. (gui_item_init): ditto. (gui_add_item_keywords_to_plist): ditto. (gui_item_equal): ditto. (syms_of_gui): add Q_value. * glyphs-x.c (x_progress_gauge_update): use pending items and value for setting the state. (x_update_widget): don't set items from pending here. * glyphs-widget.c (update_widget): update items here. (progress_gauge_set_property): use items for storing value. Put new value in pending items. * glyphs-msw.c (mswindows_progress_gauge_update): use pending items for new value. Convert percent -> value. (mswindows_tab_control_update): don't update items here. * glyphs.c (Fupdate_widget_instances): use image_instance_changed. (update_subwindow): ditto. (image_instance_changed): new function. Compare hash values and past and present widget items. (image_instantiate): We more careful about where we instantiate things. (image_instantiate): add error checking. * gutter.c (syms_of_gutter): use -hook. 2000-03-22 Andy Piper <andy(a)xemacs.org> * config.h.in: add ERROR_CHECK_GLYPHS. * configure.in: add error_check_glyphs. -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

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