July 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: pgnus commandeers emacs to check mail 25 years, 4 months

Rajesh Godbole

Is threading on the roadmap/TODO list? Is someone actively working on this? IMHO it would be a very desirable feature. >>>>> Stainless Steel Rat writes: SSR> Emacs is not threaded (and it probably will never be, at SSR> least not in its current incarnation).

3 participants
2 comments

Re: pgnus commandeers emacs to check mail 25 years, 4 months

Rajesh Godbole

>>>>> Olivier Galibert writes: OG> What for ? Most people don't care about multithreading, they OG> only want xemacs to stop blocking while gnus reads the active OG> file. Implementing a fully-fledged multithreading for _that_ OG> is way overkill. if the feature becomes available, apps can be written to it, like parallel fetches with nntp/nnimap/nnml backends in gnus. multiple non-blocking apps in different frames. You build it, they'll come.

1 participants
0 comments

[offtopic] CLI, Emacs, or IDE? 25 years, 4 months

Colin Rafferty

Linux development: CLI, Emacs, or IDE? LinuxWorld columnist Joe Barr gets few equivocal answers from leading developers http://www.software.ibm.com/developer/library/dev-linux.html

1 participants
0 comments

crypt++.el and folding.el 25 years, 4 months

Guido Van Hoecke

This error only occurs with xemacs: - XEmacs 21.2 (beta18) "Toshima" [Lucid] (i586-pc-win32) of Thu Jul 15 1999 on NEVERYON) - crypt++.el v2.87 (from ftp://ftp.cs.umb.edu/pub/misc/crypt++.el) - folding.el v2.61 (from ftp://ftp.csd.uu.se/pub/users/andersl/beta/folding.el). When I find an encrypted file that uses folding mode, I get following error: Signaling: (error "Cannot fold whole buffer -- extraneous end-fold mark") signal(error ("Cannot fold whole buffer -- extraneous end-fold mark")) byte-code("..." [kill-buffer buf signal data] 3) find-file-noselect("c:\\notes") ad-Orig-find-file("c:\\notes" nil) (setq ad-return-value (ad-Orig-find-file filename codesys)) ) (let (ad-return-value) (setq ad-return-value (ad-Orig-find-file filename codesys)) ad-return-value) ) find-file("c:\\notes") #<compiled-function (&optional filename) "...(100)" [ffap-require-prefix current-prefix-arg nil call-interactively ffap-file-finder filename ffap-prompter string t case-fold-search ffap-url-regexp string-match ffap-url-fetcher ffap-dired-wildcards dired ffap-newfile-prompt file-exists-p y-or-n-p "File does not exist, create buffer? " expand-file-name signal file-error "Opening file buffer" "no such file or directory"] 5 ("c:\\XEmacs\\xemacs-packages\\lisp\\xemacs-base\\ffap.elc" . 29425) nil>() call-interactively(find-file-at-point) This problem does not occur with emacs (neither on unix nor on nt, using the same crypt++.el and folding.el). If I open a non-encrypted version of the file, folding occurs correctly. Guido.

1 participants
0 comments

completions vs. space in dir name 25 years, 4 months

Neal D. Becker

It seems that completions won't work if a dir has a space in the name.

1 participants
0 comments

assertion failed, insdel.c (21.2.18, linux) 25 years, 4 months

Karl Kleinpaste

This is one I've never seen before. At the time, I was editing a Gnus score expression in the minibuf. Fatal error: assertion failed, file insdel.c, line 607, ( newmin) > BI_BUF_BEG (buf) && newmin <= BI_BUF_Z (buf) #0 0x2ad2a811 in __kill () #1 0x2ad2a63f in raise (sig=6) at ../sysdeps/posix/raise.c:27 #2 0x2ad2b84f in abort () at ../sysdeps/generic/abort.c:83 #3 0x808e0ab in assert_failed (file=0x8216430 "insdel.c", line=607, expr=0x82164b3 "( newmin) > BI_BUF_BEG (buf) && newmin <= BI_BUF_Z (buf)") at emacs.c:2668 #4 0x812d9ff in bufpos_to_bytind_func (buf=0x830a1e0, x=0) at insdel.c:607 #5 0x812e3b3 in bufpos_to_bytind (buf=0x830a1e0, x=0) at buffer.h:977 #6 0x819699c in scan_words (buf=0x830a1e0, from=1, count=-1) at syntax.c:427 #7 0x8196cd2 in Fforward_word (count=-1, buffer=137112340) at syntax.c:476 #8 0x8094c2f in Ffuncall (nargs=3, args=0x7fffe8d4) at eval.c:3189 #9 0x8063404 in execute_optimized_program ( program=0x8a4ec24 "À\t[\n\"\207¨\b", stack_depth=3, constants_data=0x83d38a0) at bytecode.c:747 #10 0x8062d15 in funcall_compiled_function (fun=138225500, nargs=1, args=0x7fffe9e0) at bytecode.c:523 #11 0x8094d89 in Ffuncall (nargs=2, args=0x7fffe9dc) at eval.c:3221 #12 0x8069a1a in Fcall_interactively (function=138210068, record_flag=137112340, keys=137112340) at callint.c:949 #13 0x8093413 in Fcommand_execute (cmd=138210068, record=137112340, keys=137112340) at eval.c:2623 #14 0x80e02a2 in execute_command_event (command_builder=0x83531d0, event=146245096) at event-stream.c:4345 #15 0x80e10de in Fdispatch_event (event=146245096) at event-stream.c:4684 #16 0x8073320 in Fcommand_loop_1 () at cmdloop.c:578 #17 0x807309d in command_loop_1 (dummy=137112340) at cmdloop.c:493 #18 0x8091741 in condition_case_1 (handlers=137112436, bfun=0x807304c <command_loop_1>, barg=137112340, hfun=0x80724d0 <cmd_error>, harg=137112340) at eval.c:1640 #19 0x8072994 in call_command_loop (catch_errors=137112364) at cmdloop.c:255 #20 0x814b0b8 in Fread_minibuffer_internal (prompt=145592476) at minibuf.c:188 #21 0x8094c1c in Ffuncall (nargs=2, args=0x7fffed4c) at eval.c:3189 #22 0x8063404 in execute_optimized_program ( program=0x7fffed98 "À Á V«\013Â\211\e\034Å\016\006!*\207Å\016\006!\207Ô*ÌfÚ* $Ú*\234\226#\b \204¬\b\b\013$\b8$Ú*\024+,\b\"", stack_depth=2, constants_data=0x83f1bd8) at bytecode.c:747 #23 0x806748c in Fbyte_code (instructions=138302212, constants=138353608, stack_depth=5) at bytecode.c:2406 #24 0x80941f6 in Feval (form=138353008) at eval.c:2986 #25 0x809131c in internal_catch (tag=137200580, func=0x809393c <Feval>, arg=138353008, threw=0x0) at eval.c:1315 #26 0x8063f34 in execute_rare_opcode (stack_ptr=0x7fffefc8, program_ptr=0x8a45244 "æa«\f\201H", opcode=Bcatch) at bytecode.c:1253 #27 0x80631a8 in execute_optimized_program ( program=0x8a450d4 "\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!â\216ã\016\e!q\210\016\022\026\021äå!\210æ\026%äç!\210äè!\210äé!\210ê\026'ë\026(\016,«\025äí!\210\016-"..., stack_depth=6, constants_data=0x83f4490) at bytecode.c:657 #28 0x8062d15 in funcall_compiled_function (fun=138289016, nargs=5, args=0x7ffff0d8) at bytecode.c:523 #29 0x8094d89 in Ffuncall (nargs=6, args=0x7ffff0d4) at eval.c:3221 #30 0x8063404 in execute_optimized_program ( program=0x8a2472c "À\031Â\013\f\rÀ\016\006%)\207(", stack_depth=6, constants_data=0x83f3b10) at bytecode.c:747 #31 0x8062d15 in funcall_compiled_function (fun=138359588, nargs=2, args=0x7ffff1e8) at bytecode.c:523 #32 0x8094d89 in Ffuncall (nargs=3, args=0x7ffff1e4) at eval.c:3221 #33 0x8063404 in execute_optimized_program ( program=0x8ab96c4 "\bÁa«\003Â\020\bÂa¬\013\bÃa¬\006\bÄa«\037\r«\030\r\036\006ÇÈ\016\006\"«\t\016\006É\225ÄOª\003\016\006)ª\002Ê\025ª\n\bËa«\005Ì\r!\025Í\016\016!ÏÐ\016\021\227\"Ä\036\022\036\021\036\016\016\023«/ÔÏÕ\016\026×a«\004Øª\n\016\026;«\004Ùª\002Ú\016\021\016\016ÉW«\004Ûª\002Ü$\r§«\006Ý\r!ª\002\r\"\025ÏÐ\r\"\025Þß\016\021\016 \"8áa«\005â\r!\025\016\026×a\204æ", stack_depth=7, constants_data=0x8a2c590) at bytecode.c:747 #34 0x8062d15 in funcall_compiled_function (fun=143570136, nargs=8, args=0x7ffff2fc) at bytecode.c:523 #35 0x8094d89 in Ffuncall (nargs=9, args=0x7ffff2f8) at eval.c:3221 #36 0x8063404 in execute_optimized_program ( program=0x8d0c51c "À\t!\211\032ÃW«\004Äª\002Å\036\006\nÃV\036\aÈ\036\tÊ\036\013\016\f\036\rÎÏ ÐEÑÒE\036\023\016\024\036\025\016\026\a×\016\026!ÃH\036\030\016\031\a×\016\031!ÃH\036\032\016\e\a×\016\e!ÃH\036\034Ý\036\036Ý\036\037Ý\036 Ý\036!Ý\036\"ã\216\016\030¬>\016\025«\räå!\210æç\016\006\"\210ª\023æè\016\a«\004éª\002êëì\016\tí##\210î \211\026\030ïU¬\a\016\030ðU«ÌÝ\026\030ñò\016\tå#\210ªÀó \210\016\030\227\016\t·\211\026\036¬\023\016\025«\013ôõ\016\006\016\030#\210ª\005ôö!\210\016\030\227\016\030U"..., stack_depth=10, constants_data=0x8a2c228) at bytecode.c:747 #37 0x8062d15 in funcall_compiled_function (fun=143569996, nargs=2, args=0x7ffff41c) at bytecode.c:523 #38 0x8094d89 in Ffuncall (nargs=3, args=0x7ffff418) at eval.c:3221 #39 0x8063404 in execute_optimized_program ( program=0x8d2a41c "ÀÁ\n![\013\"\207\t ", stack_depth=3, constants_data=0x8a2a148) at bytecode.c:747 #40 0x8062d15 in funcall_compiled_function (fun=143569800, nargs=2, args=0x7ffff51c) at bytecode.c:523 #41 0x8094d89 in Ffuncall (nargs=3, args=0x7ffff518) at eval.c:3221 #42 0x809546a in Fapply (nargs=2, args=0x7ffff560) at eval.c:3456 #43 0x8095c8e in apply1 (fn=143569800, arg=146722424) at eval.c:3808 #44 0x8067ee4 in Fcall_interactively (function=141483844, record_flag=137112340, keys=137112340) at callint.c:397 #45 0x8093413 in Fcommand_execute (cmd=141483844, record=137112340, keys=137112340) at eval.c:2623 #46 0x80e02a2 in execute_command_event (command_builder=0x83531d0, event=144459644) at event-stream.c:4345 #47 0x80e10de in Fdispatch_event (event=144459644) at event-stream.c:4684 #48 0x8073320 in Fcommand_loop_1 () at cmdloop.c:578 #49 0x807309d in command_loop_1 (dummy=137112340) at cmdloop.c:493 #50 0x8091741 in condition_case_1 (handlers=137112436, bfun=0x807304c <command_loop_1>, barg=137112340, hfun=0x80724d0 <cmd_error>, harg=137112340) at eval.c:1640 #51 0x8073538 in command_loop_2 (dummy=137112340) at cmdloop.c:255 #52 0x809131c in internal_catch (tag=137186628, func=0x8073504 <command_loop_2>, arg=137112340, threw=0x0) at eval.c:1315 #53 0x8072937 in initial_command_loop (load_me=137112340) at cmdloop.c:304 #54 0x808cf5d in xemacs_21_2_b18_i686_pc_linux (argc=5, argv=0x7ffff9d4, envp=0x7ffff9ec, restart=0) at emacs.c:1759 #55 0x808d6e9 in main (argc=5, argv=0x7ffff9d4, envp=0x7ffff9ec) at emacs.c:2184 uname -a: Linux beaver.jprc.com 2.2.10-ac10 #1 SMP Tue Jul 13 13:23:27 EDT 1999 i686 unknown ./configure '--with-pop' '--with-mule' '--with-png' XEmacs 21.2-b18 "Toshima" configured for `i686-pc-linux'. Where should the build process find the source code? /home/karl/src/x/xemacs-21/xemacs-21.2.18 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 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 Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using POP for mail access. Compiling in extra code for debugging. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: ---------------------------------------------------------

1 participants
0 comments

Undesirable behavior by new mailcrypt package 25 years, 4 months

Kevin Oberman

I pulled in the new gpg friendly mailcrypt 2.00 and hit a big snag. It now pops up a window reporting that the signature was OK for each signed message. The window titled "Question" just sits there until it's acked with a click or a RET.. This is probably OK for mail, but for network news and NoCeM it's a royal pain. Hitting the OK for a few thousand signed messages. I looked for some way to turn this off, but I have not found any. Is there a way to get rid of these annoying messages? It may be worse than getting all of the spam in net news! R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634

1 participants
0 comments

Re: Problem w/ ILISP 5.8 + XEmacs 20.4 + Allegro 4.3.1 25 years, 4 months

Jan Vroonhof

William Deakin <willd(a)pindar.com> writes: > Also, when running under debug I have got the a message like "concat is > no longer supported with compiled code after version 20.3." I am running > ilisp compiled and there 129 concat's in the lisp. Could this be the > problem. Could mail a backtrace. i.e. 1. load all the ilisp files as uncompiled lisp by using M-x load-file RET "filename.el" RET (or simply remove the .elc's and restart XEmacs). 2. set debug-on-error to t and reproduce. Then mail the complete contents of the *Backtrace* buffer, not just the error. Jan

1 participants
0 comments

Re: Problem w/ ILISP 5.8 + XEmacs 20.4 + Allegro 4.3.1 25 years, 4 months

Raymond Toy

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Marco Antoniotti <marcoxa(a)copernico.parades.rm.cnr.it> writes: >> > Having installed the inferior lisp package with xemacs 21.1-p3, I cannot get >> > ilisp to work with CLISP. >> >> If anybody has any clue about what is happening with XEmacs/ILISP, >> please let me know or write to ILISP mailing list. (for the time >> being, but not much longer, <ilisp(a)naggum.no>). Jan> Well. I am not sure whose problem this is exactly, but for me the Jan> problem seems to be with something (i.e. either XEmacs or Clisp[1]) not Jan> flushing pipe buffers correctly. The patch below "fixes" the problem Jan> for me. I can run Clisp now and evaluate "(+ 1 2)", define a function Jan> and have it complete the function name in a call. One other thing: I think you're supposed to use the -I option when running clisp with ilisp. I'm vaguely remember the -I option being added exactly for this purpose. I causes clisp to flush it's buffers at the right time, or something like that. Clisp works fine for me, without Jan's patch. (Well, except it can't autoload clisp-hs from ilisp-chs.el, but that's a different issue.) Ray

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: > The next thing to figure out now is why Steve can duplicate the > problem even when allow-deletion-of-last-visible-frame is t. Note that this doesn't apply for me. When I set a-d-o-l-v-f (sic!) to t, I don't see the problem.

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