May 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Toni Brkic

I read the Emacs vs XEmacs and I have an question that I am curious of. Emacs is based on FSF emacs19 which is gpl, doesnt that make XEmacs GPL? I have this question since Stallman is ranting about that emacs developer cant use code that is in XEmacs for emacs. Hope someone has time to answer my question.

1 participants
0 comments

ispell-comments-and-strings under XEmacs 24 years, 3 months

Hrvoje Niksic

[ If <ispell-el-bugs> is not the appropriate address for reporting XEmacs-specific ispell bugs, please let me know. ] Has anyone noticed that ispell-comments-and-strings doesn't work under XEmacs? At least it doesn't work for me, with XEmacs 21.2-b32, ispell v3.3. When I type the command in a C mode or a Lisp mode buffer, I get the following error (backtrace uncompiled intentionally): Signaling: (error "Unterminated string or comment") signal(error ("Unterminated string or comment")) cerror("Unterminated string or comment") apply(cerror "Unterminated string or comment") error("Unterminated string or comment") (if (or (nth 3 state) (nth 4 state)) (error "Unterminated string or comment")) ) (let ((start ...)) (setq state (parse-partial-sexp start ... nil nil state ...)) (if (or ... ...) (error "Unterminated string or comment")) (save-excursion (setq done ...))) ) (if (or (nth 3 state) (nth 4 state)) (let (...) (setq state ...) (if ... ...) (save-excursion ...))) ) (while (not done) (setq done t) (setq state (parse-partial-sexp ... ... nil nil state ...)) (if (or ... ...) (let ... ... ... ...))) ) (let (state done) (while (not done) (setq done t) (setq state ...) (if ... ...))) ) (lambda nil "Check comments and strings in the current buffer for spelling errors." (interactive) (goto-char (point-min)) (let (state done) (while ... ... ... ...)))() call-interactively(ispell-comments-and-strings) command-execute(ispell-comments-and-strings t) execute-extended-command(nil) call-interactively(execute-extended-command) I don't know enough about parse-partial-sexp to be able to tell whether the problem is with XEmacs or with ispell; I do have a version of that function that works fine using the `syntactically-sectionize' mechanism of XEmacs: (defun ispell-comments-and-strings () (interactive) (syntactically-sectionize (lambda (start end context depth) (when (or (eq context 'string) (eq context 'comment) (eq context 'block-comment)) (ispell-region start end))) (point-min) (point-max)))

1 participants
0 comments

Recurring set-window-configuration crashes 24 years, 3 months

Michael Sperber

This happens to me about 3 times a day with last weekend's CVS, in various contexts. This is pdump on FreeBSD 4.0. #0 0x284ba030 in kill () from /usr/lib/libc.so.4 #1 0x80b0c57 in fatal_error_signal (sig=6) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/emacs.c:514 #2 0xbfbfffac in ?? () #3 0x80b3c99 in assert_failed ( file=0x825bc00 "/afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/glyphs.c", line=590, expr=0x825bd04 "DOMAIN_LIVE_P (instance)") at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/emacs.c:3115 #4 0x811d294 in check_image_instance_structure (instance=143221632) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/glyphs.c:590 #5 0x8125165 in unmap_subwindow (subwindow=143221632) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/glyphs.c:4416 #6 0x8124cf8 in reset_frame_subwindow_instance_cache (f=0x84a5e00) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/glyphs.c:4184 #7 0x81c197c in Fset_window_configuration (configuration=146339840) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/window.c:5222 #8 0x80b8e83 in Ffuncall (nargs=2, args=0xbfbfe164) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:3214 #9 0x8090f53 in execute_optimized_program ( program=0xbfbfe1c0 "\bq\210Á\b!\210Â\023Ä \210\r«\023Æ\016\a!«\r\016\bÉ a«\006Ê\016\a!\210\r«\005Ë\r!\210Ë\016\f!\207\217\013\b\001", stack_depth=2, constants_data=0x2860a1f8) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/bytecode.c:747 #10 0x809379e in Fbyte_code (instructions=676498368, constants=677421544, stack_depth=5) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/bytecode.c:2406 #11 0x80b8451 in Feval (form=677165336) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:3014 #12 0x80be4d1 in Fprogn (args=677165348) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:768 #13 0x80bb90f in unbind_to_hairy (count=22) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:4654 #14 0x8090ff9 in execute_optimized_program ( program=0x8795010 "\b¬\022Á ÂV«\fÃ Ä a«\005ÅÆ!\210\016\a«\021\016\aÂV«\013Á \016\aY«\004È \210\016\t«\"\016\t9«\017Ê\016\t!¬\027ÅË\016\t\"\210ª\017Ê\016\t＠!¬\bÅË\016\t＠\"\210Ì «\tÍÎÏ\016\020!\"\210\016\021\036\022Ã \036\023Ô \036\025Ä \036\026Á Âa«\a×\016\026!ª\bØÙÚÁ \"!\036\eÜ\016\026!\211\036\035Ô a?\005Þ\016\035!\036\037Þ \036 \016\t\036!\016\"\036#ä\216å\016\e!q\210\016\022\026\021æç!\210è\026'æé!\210æê!\210æë!\210ì\026)í\026*\016.«\025æï"..., stack_depth=6, constants_data=0x28622318) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/bytecode.c:760 #15 0x8090bad in funcall_compiled_function (fun=677646608, nargs=7, args=0xbfbfe548) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/bytecode.c:519 #16 0x80b901f in Ffuncall (nargs=8, args=0xbfbfe544) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:3249 #17 0x8090f53 in execute_optimized_program ( program=0x83ae910 "\b\t\nÃa?\002ÃÄ\211\035\036\006\036\a\036\b\036\tÊ\016\013\016\f\n¬\005\016\rª\003\016\016Ä\016\017Ä\016\020&\a\211\025Ñ\230«\t\016\020«\005\016\020ª\002\r-\207", stack_depth=9, constants_data=0x28622528) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/bytecode.c:747 #18 0x8090bad in funcall_compiled_function (fun=677646748, nargs=2, args=0xbfbfe6a8) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/bytecode.c:519 #19 0x80b901f in Ffuncall (nargs=3, args=0xbfbfe6a4) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:3249 #20 0x8090f53 in execute_optimized_program ( program=0x88e1710 "ÀÁÂ «\004Ãª\002\fÅQÆ \"\211\036\aGÈU«\nÂ «\006Ã\026\aª\020\016\aGÈU«\006\f\026\aª\004\016\a\024É\016\aÆ \"\211\036\n¬\aË\016\aC!\210\016\f«\aÍ\016\a!ª\005Î\016\a!*\207", stack_depth=5, constants_data=0x8786090) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/bytecode.c:747 #21 0x8090bad in funcall_compiled_function (fun=142437448, nargs=1, args=0xbfbfe804) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/bytecode.c:519 #22 0x80b901f in Ffuncall (nargs=2, args=0xbfbfe800) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:3249 #23 0x809599b in Fcall_interactively (function=142455340, record_flag=676864912, keys=676864912) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/callint.c:946 #24 0x80b7728 in Fcommand_execute (cmd=142455340, record=676864912, keys=676864912) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:2652 #25 0x80eb851 in execute_command_event (command_builder=0x83f5900, event=145637960) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/event-stream.c:3836 #26 0x80ec241 in Fdispatch_event (event=145637960) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/event-stream.c:4203 #27 0x809a236 in Fcommand_loop_1 () at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/cmdloop.c:579 #28 0x809a4c9 in command_loop_1 (dummy=676864912) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/cmdloop.c:494 #29 0x80be219 in condition_case_1 (handlers=676864720, bfun=0x809a48c <command_loop_1>, barg=676864912, hfun=0x809a538 <cmd_error>, harg=676864912) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:1640 #30 0x809a627 in command_loop_2 (dummy=676864912) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/cmdloop.c:256 #31 0x80be11c in internal_catch (tag=676697080, func=0x809a5ec <command_loop_2>, arg=676864912, threw=0x0) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/eval.c:1306 #32 0x8099b6f in initial_command_loop (load_me=676864912) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/cmdloop.c:305 #33 0x80b203f in xemacs_21_2_b33_i386_unknown_freebsdelf4_0 (argc=1, argv=0xbfbfed3c, envp=0xbfbfed44, restart=0) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/emacs.c:2147 #34 0x80b3e16 in main (argc=1, argv=0xbfbfed3c, envp=0xbfbfed44) at /afs/informatik.uni-tuebingen.de/home/sperber/build/xemacs-21.2/src/emacs.c:2514 #35 0x8080111 in _start () -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Test release of pcl-cvs-1.46-pkg.tar.gz 24 years, 3 months

Andreas Jaeger

>>>>> Paul Krause writes: Paul> Looks great so far. One nuisance is that cvs-set-cvsroot doesn't let you set cvsroot Paul> to a remote root. The code below fixes that. If xemacs-beta thinks this is a Paul> reasonable fix, I will submit a patch. Paul> Where should I send the patch? >From pcl-cvs.texi: If you find a bug or misfeature, don't hesitate to tell us! Send email to ＠samp{pcl-cvs＠(a)cyclic.com}. We prefer discussing one thing at a time. If you find several unrelated bugs, please report them separately. That way our bug-tracking software will work better. If you report several problems in a single email we might miss one or two of them. If you are running pcl-cvs under XEmacs, you should also send a copy of bug reports to ＠samp{xemacs-beta＠(a)xemacs.org}. [...] Paul> Also, I don't understand why efs file-name completion works with interactive F but Paul> not D. Paul> Could this be an XEmacs bug? Mike, what do you think? Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.inka.de

1 participants
0 comments

Test release of pcl-cvs-1.46-pkg.tar.gz 24 years, 3 months

Andreas Jaeger

I've uploaded pcl-cvs-1.46-pkg.tar.gz to the usual place. This is an update to version 2.9.9. Please test this package before I release it to the public. Thanks to Mike Sperber for checking this in, Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.inka.de

2 participants
1 comments

ilisp - Never mind the never mind... 24 years, 3 months

Karl M. Hegbloom

Ok, ok, ok... I changed my mind again. It's just that it's going to be more work than I thought. I don't know just how much yet, of course. I'll try to budget some time for this... (promises promises...) <URL:http://www.intra/~cvsweb/cvsweb.cgi/ilisp/?cvsroot=X?Emacs_Lisp_Hacks> It's meant to be checked out where the cvs.xemacs.org version sits inside a full checkout of the `xemacs-packages'. cd ${xemacs-packages}/os <edit CVS/Entries and remove the ilisp that's there from cvs.xemacs.org> rm -rf ilisp (or copy it aside -- whatever) export CVSROOT=:pserver:anoncvs＠bittersweet.inetarena.com:/var/cvs/emacsen cvs login <blank password - I encrypted the empty string> cvs -z3 checkout ilisp Mail me patches if you like, and I'll commit them. I'm vendor tracking them, so any changes I (or maybe we) make can maybe go back upstream to the `ilisp' group at cons.org. -- Those who do not study Lisp are doomed to reimplement it - Poorly. A few months in the laboratory often saves several hours at the library. mailto:karlheg＠debian.org (Karl M. Hegbloom)

1 participants
0 comments

ilisp.el - never mind. 24 years, 3 months

Karl M. Hegbloom

Never mind, something came up, I won't have the time.

1 participants
0 comments

ilisp 5.10.1 24 years, 3 months

Karl M. Hegbloom

I've been working on getting `ilisp' 5.10.1 working, and have it mostly working, plugged into my checkout of the `xemacs-packages' from CVS. I'm back to studying Lisp and Scheme again, and will be using Ilisp some with cmulisp and with guile... (I might try and create an ilisp dialect definition for Maxima as well, though at this point don't know if there's any advantage in using ilisp for that over the plain comint based mode I cobbled together for it last week.) The trouble is that there's some stuff in "ilisp/extra/" that, according to the README there, is `contrib' -- it's not totally GPL compatible since it relies on the online HyperSpec, which is `non-free' (and not redistributable, afaik) What should I do with that? I can make `ilisp' not load it by default, but if, for instance, a Debian package is made of `ilisp', that stuff is maybe supposed to go in a separate package. (blah! What a PITA.) I don't think there's any restriction on redistribution or modification of `hyperspec.el', but it depends on the non-free Common Lisp Hyperspec, I guess. Maybe I should just clam up and put it in the package anyway. Would anyone on earth _really_ freak about that? There is also an issue with the ilisp licence. It's not completely GPL, _yet_... Will someone on the XEmacs Development Team please have a look at it? I'll mail it to you if you like -- I won't include it here. I do not currently have writes to that section of the repository. I think that a patch will be quite large. I can upload a tarball for someone else to commit, or will commit myself if given writes. I will of course make a copy available for approval prior to making that checkin, and think that I'd like for someone who uses `ilisp' to do that. I don't want to check something in that others think of as broken and get people angry with me. I have not even begun to read the `ilisp' codes or even the manual yet. It will take me some time, I imagine. There are a few things needing done with it. They changed the pop up message thing to use a separate frame rather than a popup window. When you load "ilisp", it opens two new frames, rudely. That frame needs a configurable frame properties plist, and there should be an option to make it use a window like it used to. Likely other things should be done. -- Those who do not study Lisp are doomed to reimplement it - Poorly. A few months in the laboratory often saves several hours at the library. mailto:karlheg＠debian.org (Karl M. Hegbloom)

1 participants
0 comments

Re: Themes and specifier fallbacks... 24 years, 3 months

Daniel Pittman

On 16 May 2000, William M. Perry <wmperry(a)aventail.com> wrote: > So, I just implemented this really gross hack/feature. :) [... themes dynamically change colors ...] > So the question is - does this seem like sane behaviour to people? > Well, ok, maybe it doesn't have to be sane. How about 'expected from a > theme-able application'? That's what I would expect to happen, myself. It would just 'do what I mean' in pretty much every case. Daniel -- No story is the same to us after the lapse of time; or rather we who read it are no longer the same interpreters. -- George Eliot

1 participants
0 comments

Themes and specifier fallbacks... 24 years, 3 months

William M. Perry

So, I just implemented this really gross hack/feature. :) Right now, no fallbacks are specified for any of the faces in faces.c like they are for the other types of windowing systems. I delay that until the 'style_set' method of the GtkXEmacs widget is called for the first time. Then I use set_specifier_fallback to add style-specific fallbacks. Soooooo... just for giggles I removed the 'only do it once' guard. So that way if you are using the Gnome theme selector and change your theme, the fallbacks will change. This means that if you have specified changes to the faces, they will still be in effect, but if you just use the 'defaults', then the frame will dynamically update to reflect the new color scheme of the theme. So the question is - does this seem like sane behaviour to people? Well, ok, maybe it doesn't have to be sane. How about 'expected from a theme-able application'? -Bill P.

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