June 2000 - XEmacs-Beta - XEmacs Mailing List Archives

John S. J. Anderson

>>>>> "Trey" == Trey <trey(a)veggie.stu.wesleyan.edu> writes: Trey> Can anyone tell me whom I should bother with my elisp checkers Trey> game? What would you like to have happen with it? Assuming it's not huge, posting it on the gnu.emacs.sources newsgroup might be the best way to expose a large number of people to it. HTH, john. -- ------------------------------------------------------------------------ John S Jacobs Anderson \ <URL:http://www.xemacs.org> You'll have to pry my Emacs from my cold \ jacobs(a)xemacs.org dead oversized control-pressing left pinky finger. -- Randal L. Schwartz

3 participants
2 comments

gutter crash 24 years, 5 months

Ben Wing

i just hit this after hitting ESC ESC ESC, which was doing the equivalent of C-x 1 on a frame with 2 windows [the bottom one a grep window]. Dynarr_free(void * 0x0000007d) line 207 + 3 bytes free_display_line(display_line * 0x02489318) line 6962 + 12 bytes free_display_lines(display_line_dynarr * 0x0206d740) line 6993 + 19 bytes free_display_structs(window_mirror * 0x02060840) line 7012 + 12 bytes free_window_mirror(window_mirror * 0x02060840) line 478 + 9 bytes update_mirror_internal(long 28360708, window_mirror * 0x02060980) line 358 + 9 bytes update_mirror_internal(long 28595200, window_mirror * 0x01ee10c0) line 369 + 28 bytes update_frame_window_mirror(frame * 0x01d1d600) line 461 + 22 bytes window_display_buffer(window * 0x01b45400) line 575 + 21 bytes output_display_line(window * 0x01b45400, display_line_dynarr * 0x01d26840, display_line_dynarr * 0x01d26640, int 0, int -1, int -1) line 578 + 9 bytes output_gutter(frame * 0x01d1d600, int 0, int 0) line 318 + 25 bytes update_frame_gutters(frame * 0x01d1d600) line 562 + 15 bytes redisplay_frame(frame * 0x01d1d600, int 0) line 6384 + 9 bytes redisplay_device(device * 0x01bc4000, int 1) line 6467 + 11 bytes redisplay_without_hooks() line 6556 + 11 bytes redisplay() line 6619 Fnext_event(long 34969604, long 28360708) line 2183 Fcommand_loop_1() line 570 + 16 bytes command_loop_1(long 28360708) line 495 condition_case_1(long 28360804, long (long)* 0x0105a4fb command_loop_1(long), long 28360708, long (long, long)* 0x01059f10 cmd_error(long, long), long 28360708) line 1640 + 7 bytes command_loop_3() line 256 + 35 bytes command_loop_2(long 28360708) line 268 internal_catch(long 28438700, long (long)* 0x0105a060 command_loop_2(long), long 28360708, int * 0x00000000) line 1306 + 7 bytes initial_command_loop(long 28360708) line 305 + 25 bytes STACK_TRACE_EYE_CATCHER(int 1, char * * 0x01b8cfc8, char * * 0x01df5300, int 0) line 2169 + 9 bytes main(int 1, char * * 0x01b8cfc8, char * * 0x01df5300) line 2598 + 21 bytes mainCRTStartup + 211 bytes _start() line 169 KERNEL32! 77e9bc52() -- Ben In order to save my hands, I am cutting back on my mail. I also write as succinctly as possible -- please don't be offended. If you send me mail, you _will_ get a response, but please be patient, especially for XEmacs-related mail. If you need an immediate response and it is not apparent in your message, please say so. Thanks for your understanding. See also http://www.666.com/ben/chronic-pain/

1 participants
0 comments

Re: CVS packages 24 years, 5 months

Jerry James

On Wed, 21 Jun 2000 at 10:33:28 +0900 (JST), Martin Buchholz <martin(a)xemacs.org> wrote: > Suggestions: > > - Use cvs-1.10.7 or cvs-1.10.8 for your CVS client. I was using cvs-1.10.6, so I upgraded. Doing a "cvs update" then updated *everything*, but still didn't give me the missing files. > - Don't use :ext: for read-only operations (this might not apply to you) No, it doesn't. > - Add these entries to .cvsrc: > > checkout -P > update -Pd This worked. It also gave me a few other files deep in the hierarchy, such as comm/gnus/gnus/.new.configure. Any idea why it didn't let me have them when I did the initial checkout? Thanks, Martin. -- Jerry James

2 participants
1 comments

Problems with the new package making scheme 24 years, 5 months

Didier Verna

1/ I like it, in particular the fact that I can install a symlink tree in /usr/local/lib/xemacs/*-packages 2/ Mew is always recompiled by each consecutive `make' command. I don't know if it's related, but all compilation gives this: While compiling toplevel forms in file /usr/local/src/xemacs-packages/comm/mew/mew/mew-cache.el: !! Symbol's value as variable is void ((mew-use-overlay-keymap)) 3/ I don't like the fact that *all* packages are compiled, even the ones I don't want to install. I understand that the primary goal of the Makefiles are to generate distributions for all packages, but I still think there should be a way to make a partial bytecompilation. 4/ I can't install the mule "locale" package. I get this: ls -1 pkginfo/MANIFEST.locale > pkginfo/MANIFEST.locale) ls: lisp/locale/ChangeLog: No such file or directory ls: lisp/locale/auto-autoloads.elc: No such file or directory ls: lisp/locale/auto-autoloads.el: No such file or directory ls: lisp/locale/_pkg.el: No such file or directory make[1]: *** [binkit-common] Error 1 make[1]: Leaving directory `/usr/local/src/xemacs-packages/mule/locale' make: *** [install] Error 2 The following patch fixes it, although it's totally blind. Since the fix is actually just to uncomment conditionals, I guess somebody commented those lines in order see if this was going to trigger an error somewhere. Well, here it is :-) Index: XEmacs.rules =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-packages/XEmacs.rules,v retrieving revision 1.17 diff -u -r1.17 XEmacs.rules --- XEmacs.rules 2000/06/02 14:17:21 1.17 +++ XEmacs.rules 2000/06/21 13:50:27 ＠＠ -268,13 +268,13 ＠＠ endif (cd $(STAGING); \ ls -1 $(MANIFEST) > $(MANIFEST)) -#ifneq ($(ELCS),) +ifneq ($(ELCS),) ＠(cd $(STAGING); \ ls -1 lisp/$(PACKAGE)/ChangeLog \ $(patsubst %, lisp/$(PACKAGE)/%, $(notdir $(SOURCE_FILES_TO_COPY))) \ $(patsubst %, lisp/$(PACKAGE)/%, $(notdir $(EXTRA_SOURCES))) \ >> $(MANIFEST)) -#endif +endif ifneq ($(ELCS_1),) ＠(cd $(STAGING); \ ls -1 $(patsubst %, lisp/$(ELCS_1_DEST)/%, $(notdir $(ELCS_1_FILES))) \ -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠lrde.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: CVS packages 24 years, 5 months

Andreas Jaeger

>>>>> Jerry James writes: > I wanted to see why the PSGML package is messing up unless it is > re-bytecompiled, so I checked the current packages out of CVS as > indicated on cvs.xemacs.org. I may just be suffering from some mental > defect, but I didn't get a Local.rules.mk or Local.rules.template when I > asked for xemacs-packages. Any compile immediately bombs out without > Local.rules.mk, and creating an empty one causes bizarre things to > happen, so I'm stuck. What am I missing? You should get Local.rules.mk and Local.rules.template - if not you've got some CVS problems. Have a look: gromit:/cvs/xemacs-packages:[0]$ cvs status Local.rules.mk =================================================================== File: Local.rules.mk Status: Up-to-date Working revision: 1.2 Repository revision: 1.2 /usr/CVSroot/XEmacs/xemacs-packages/Local.rules.mk,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) gromit:/cvs/xemacs-packages:[0]$ cvs status Local.rules.template =================================================================== File: Local.rules.template Status: Up-to-date Working revision: 1.2 Repository revision: 1.2 /usr/CVSroot/XEmacs/xemacs-packages/Local.rules.template,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) I advise to run cvs update again from the xemacs-packages directory. Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.inka.de

1 participants
0 comments

Re: question 24 years, 5 months

John S. J. Anderson

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: >>>>> "jsja" == John S J Anderson <jacobs(a)xemacs.org> writes: >>>>> "Trey" == Trey <trey(a)veggie.stu.wesleyan.edu> writes: Trey> Can anyone tell me whom I should bother with my elisp checkers Trey> game? jsja> What would you like to have happen with it? Assuming it's not jsja> huge, posting it on the gnu.emacs.sources newsgroup might be the jsja> best way to expose a large number of people to it. Martin> First of all, an elisp package designed to run only with Martin> XEmacs is not welcome on gnu.emacs.sources. Sorry; wasn't aware of that restriction in the group charter. Would creating a specific public place for the posting of XEmacs-specific elisp sources be a Good Thing? (It really doesn't seem as if xemacs-beta should be that place; xemacs-patches also doesn't seem like the right place.) Martin> Secondly, I think our eventual goal is to have all "good" Martin> elisp packages be part of the XEmacs package tree, where the Martin> package maintainers can update them. So we want to put Martin> checkers into xemacs-packages/games. But, in order to get the ball rolling -- to make the package maintainers aware of a candidate package, and to enable them to check it out and discuss it -- is posting the source (or a link to the source) to xemacs-beta the way to go? I'm pretty sure this is the second time Trey has posted this query, and this is the first time I recall anyone responding. If that is the "eventual goal", then the question: "How do I get my elisp package added to the XEmacs distribution" should probably be in the FAQ, along with an answer outlining the process. I'm not currently clear on what that process is supposed to be. "Question 1.1.3: How do I contribute to XEmacs itself?" looks as if it should contain the answer, but really doesn't. It also talks about 'posting', but it's unclear what forum one should post to; I guess xemacs-beta. john. -- ------------------------------------------------------------------------ John S Jacobs Anderson \ <URL:http://www.xemacs.org> You'll have to pry my Emacs from my cold \ jacobs(a)xemacs.org dead oversized control-pressing left pinky finger. -- Randal L. Schwartz

4 participants
4 comments

CVS packages 24 years, 5 months

Jerry James

I wanted to see why the PSGML package is messing up unless it is re-bytecompiled, so I checked the current packages out of CVS as indicated on cvs.xemacs.org. I may just be suffering from some mental defect, but I didn't get a Local.rules.mk or Local.rules.template when I asked for xemacs-packages. Any compile immediately bombs out without Local.rules.mk, and creating an empty one causes bizarre things to happen, so I'm stuck. What am I missing? Also, while trying to find some documentation that might tell me where I am going wrong, I saw that <URL:http://cvs.xemacs.org/packages.html> refers to XEmacs 20.5. As far as I know, that version never existed, right? Thanks, -- Jerry James

3 participants
2 comments

crash - linux/vm/recent cvs 24 years, 5 months

Jeff Miller

redhat 6.1 was running vm under an xemacs that i had cvs'd and compiled last night (tues). I have been having trouble with crashes with betas the last week or so crashing with vm, once with gnus. I usually get not backtrace or error msg. So i was running this one under gdb I was composing a message, nothing fancy just typing. this was all the output in my xterm running gdb (gdb) run Starting program: /usr/local/bin/xemacs Warning: XtRemoveGrab asked to remove a widget not on the list Warning: XtRemoveGrab asked to remove a widget not on the list Warning: XtRemoveGrab asked to remove a widget not on the list Warning: XtRemoveGrab asked to remove a widget not on the list Warning: XtRemoveGrab asked to remove a widget not on the list Program received signal SIGSEGV, Segmentation fault. 0x8132fd9 in image_instance_parent_glyph (ii=0x9001598) at glyphs.c:1341 1341 if (IMAGE_INSTANCEP (IMAGE_INSTANCE_PARENT (ii))) (gdb) i get the XtRemoveGrab messages whenever i close a frame, i.e. send an email. I did a "where" and get this #0 0x8132fd9 in image_instance_parent_glyph (ii=0x9001598) at glyphs.c:1341 #1 0x8132fe4 in image_instance_parent_glyph (ii=0x9001f70) at glyphs.c:1344 #2 0x81262a9 in mark_image_instance (obj=151002992) at glyphs.c:784 #3 0x8083ed9 in mark_object (obj=151002992) at alloc.c:2500 #4 0x80819e8 in mark_cons (obj=147492696) at alloc.c:877 #5 0x8083ed9 in mark_object (obj=147492696) at alloc.c:2500 #6 0x80dcd60 in mark_widget_value_mapper (val=0x8e11a10, closure=0x0) at gui-x.c:70 #7 0x81df98a in lw_map_widget_values (id=66403, mapfunc=0x80dcd4c <mark_widget_value_mapper>, closure=0x0) at lwlib.c:446 #8 0x80dcd41 in mark_popup_data (obj=151004664) at gui-x.c:90 #9 0x8083ed9 in mark_object (obj=147488124) at alloc.c:2500 #10 0x80819e8 in mark_cons (obj=147487788) at alloc.c:877 #11 0x8083ed9 in mark_object (obj=147335012) at alloc.c:2500 #12 0x80853c2 in garbage_collect_1 () at alloc.c:3449 #13 0x80b82dc in Feval (form=137298940) at eval.c:2938 #14 0x80bd6c6 in Fprogn (args=137535972) at eval.c:768 #15 0x80ae9f0 in Fsave_excursion (args=137535972) at editfns.c:400 #16 0x80b85b1 in Feval (form=137298928) at eval.c:2986 #17 0x80b994e in funcall_lambda (fun=137537544, nargs=0, args=0xbfffebe8) at eval.c:768 #18 0x80b91ab in Ffuncall (nargs=1, args=0xbfffebe4) at eval.c:3257 #19 0x80b88a2 in Feval (form=140180536) at eval.c:3040 #20 0x80b860b in Feval (form=140180524) at eval.c:3002 #21 0x80bdb18 in Fand (args=140180512) at eval.c:663 #22 0x80b85b1 in Feval (form=140180476) at eval.c:2986 #23 0x80bda8d in For (args=140180464) at eval.c:644 #24 0x80b85b1 in Feval (form=140180416) at eval.c:2986 #25 0x80b4e77 in Fif (args=140280800) at eval.c:683 #26 0x80b85b1 in Feval (form=140180404) at eval.c:2986 #27 0x80b5519 in FletX (args=140180392) at eval.c:768 #28 0x80b85b1 in Feval (form=140180080) at eval.c:2986 #29 0x80b994e in funcall_lambda (fun=140226592, nargs=0, args=0xbffff2b8) at eval.c:768 #30 0x80b8c00 in Feval (form=140179192) at eval.c:3120 #31 0x80b4e8b in Fif (args=140179180) at eval.c:684 #32 0x80b85b1 in Feval (form=140179156) at eval.c:2986 #33 0x80b994e in funcall_lambda (fun=140179588, nargs=0, args=0xbffff5fc) at eval.c:768 #34 0x80b91ab in Ffuncall (nargs=1, args=0xbffff5f8) at eval.c:3257 #35 0x80b9c93 in run_hook_with_args_in_buffer (buf=0x8f3abe0, nargs=1, args=0xbffff5f8, cond=RUN_HOOKS_TO_COMPLETION) at eval.c:3700 #36 0x80bc7d7 in run_hook_with_args (nargs=1, args=0xbffff5f8, cond=RUN_HOOKS_TO_COMPLETION) at eval.c:3713 #37 0x80be2ad in catch_them_squirmers_run_hook (hook_symbol=137055420) at eval.c:3567 #38 0x80ba63e in safe_run_hook_trapping_errors ( warning_string=0x821a320 "Error in `post-command-hook' (setting hook to nil)", hook_symbol=137055420, allow_quit=1) at eval.c:1640 #39 0x80f1f87 in post_command_hook () at event-stream.c:3932 #40 0x80f1d21 in execute_command_event (command_builder=0x8498690, event=140221840) at event-stream.c:3841 #41 0x80f279c in Fdispatch_event (event=140221840) at event-stream.c:4157 #42 0x809b65d in Fcommand_loop_1 () at cmdloop.c:579 #43 0x809b890 in command_loop_1 (dummy=136965764) at cmdloop.c:494 #44 0x80bd3ba in condition_case_1 (handlers=136965860, bfun=0x809b858 <command_loop_1>, barg=136965764,

2 participants
5 comments

Re: unrecognized selection-conversion type 24 years, 5 months

Mike Scheidler

"John" == John A Turner <turner(a)blueskystudios.com> writes: John> John> I'm still seeing the problem detailed in the attached msg - but I'm John> not so sure any more that it's related to virtual desktops - it also John> happens right after I save a buffer John> John> [...] John> John> no one else sees this? John> John> Signaling: (error "unrecognized selection-conversion type" nil John> #<INTERNAL OBJECT (XEmacs bug?) (opaque, size=4) 0x1063db60>) I've seen this very message, but under different circumstances with Sun Solaris 2.7. I get this same error when I select text while running the Clipboard application of WinDD. (WinDD is an app that displays a remote MS-Windows session on an X11 desktop. The Clipboard is a separate X11 program that allows cut-and-paste between the two desktops.) I have no problem at all with XEmacs when not running WinDD Clipboard. This problem was reported to me by another user at our site, who said it did not occur with XEmacs 19.11, but it does occur with 20.2 (we're a little behind the times here) if that's of any help. -- Mike Scheidler c23mts(a)eng.delcoelect.com

3 participants
2 comments

question 24 years, 5 months

Ashton Trey Belew

Hello, Can anyone tell me whom I should bother with my elisp checkers game? I am still in the process of writing it, but it is playable. I intend to add some network support into it in the next few days. Have fun, -Trey ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ashton Trey Belew Work Phone: 860 685 3142 Home phone: 860 983 1046 e-mail: trey(a)veggie.wesleyan.edu http://veggie.wesleyan.edu/trey/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ QOTD: "I used to be lost in the shuffle, now I just shuffle along with the lost."

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