May 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [21.1.2] Gnus, PGP, and MULE 25 years, 6 months

Jason R Mastaler

I'm getting the same type of errors with 21.1.2 and the 05-13 non-mule SUMO. With (load "gnus-setup" t t) in my .emacs I get the following backtrace when launching XEmacs. XEmacs 21.1 "20 Minutes to Nikko" [Lucid] (i386-pc-solaris2.7) of Sun May 16 1999 on ashanti Signaling: (void-variable mime-charset-coding-system-alist) byte-code("..." [boundp mime-article/coding-system-alist mh-show-mode *noconv* t default-mime-charset nil lbt charset intern mime-charset-coding-system-alist cs format "%s-%s" CRLF dos LF unix CR mac find-coding-system mime-charset-to-coding-system-default-method current-load-list MULE mime-article::write-region #<compiled-function (start end file) "...(19)" [major-mode mime-article/coding-system-alist t file-coding-system write-region start end file] 4> featurep mule #<compiled-function (start end file) "...(19)" [major-mode mime-article/coding-system-alist t coding-system-for-write write-region start end file] 4> NEMACS #<compiled-function (start end file) "...(19)" [major-mode mime-article/kanji-code-alist t kanji-fileio-code write-region start end file] 4> defalias write-region] 10) load-internal("tm-play" nil t nil nil nil) load("tm-play" nil t nil) require(tm-play) load-internal("tm-pgp" nil t nil nil nil) load("tm-pgp" nil t nil) require(tm-pgp) #<compiled-function nil "...(4)" [require tm-pgp] 2>() run-hooks(#<compiled-function nil "...(4)" [require tm-pgp] 2>) byte-code("..." [provide tm-view run-hooks tm-view-load-hook] 2) load-internal("tm-view" nil t nil nil nil) load("tm-view" nil t nil) require(tm-view) byte-code("..." [require sendmail mail-utils mel tl-list tm-view tm-ew-e signature "$Id: tm-edit.el,v 7.108 1997/05/27 03:22:55 morioka Exp $" mime-editor/RCS-ID current-load-list get-version-string mime-editor/version "tm-edit " mime-editor/version-name] 2) load-internal("tm-edit" nil t nil nil nil) load("tm-edit" nil t nil) require(tm-edit) byte-code("..." [require tm-edit mime-make-tag "message" "rfc822" "\n" message-forward-start-separator "" message-forward-end-separator string-match message-included-forward-headers "Mime-Version:" "\\|^Mime-Version:" "Content-Type:" "\\|^Content-Type:" "Content-Transfer-Encoding:" "\\|^Content-Transfer-Encoding:"] 3) load-internal("message-mime" nil t nil nil nil) load("message-mime" nil t nil) require(message-mime) #<compiled-function nil "...(4)" [require message-mime] 2>() call-after-loaded(message #<compiled-function nil "...(4)" [require message-mime] 2>) byte-code("..." [boundp epoch::version add-hook message-setup-hook mime/editor-mode message-maybe-setup-default-charset message-send-hook mime-editor/maybe-translate message-header-hook mime/encode-message-header call-after-loaded message #<compiled-function nil "...(4)" [require message-mime] 2> provide mime-setup run-hooks mime-setup-load-hook] 3) load-internal("mime-setup" nil nil nil nil nil) load("mime-setup") byte-code("..." [gnus-use-installed-gnus gnus-gnus-lisp-directory load-path require message gnus-use-tm gnus-use-installed-tm gnus-tm-lisp-directory featurep mime-setup load "mime-setup" gnus-use-mailcrypt gnus-use-installed-mailcrypt gnus-mailcrypt-lisp-directory autoload mc-install-write-mode "mailcrypt" nil t mc-install-read-mode add-hook message-mode-hook gnus-summary-mode-hook gnus-use-mhe mh-folder-mode-hook mh-letter-mode-hook gnus-use-bbdb gnus-bbdb-lisp-directory bbdb "bbdb-com" "Insidious Big Brother Database" bbdb-name bbdb-company bbdb-net bbdb-notes gnus-use-vm bbdb-insinuate-vm "bbdb-vm" "Hook BBDB into VM" gnus-use-rmail bbdb-insinuate-rmail "bbdb-rmail" "Hook BBDB into RMAIL" rmail-mode-hook bbdb-insinuate-mh "bbdb-mh" "Hook BBDB into MH-E" bbdb-insinuate-gnus "bbdb-gnus" ...] 6) load-internal("gnus-setup" t t nil nil nil) load("gnus-setup" t t) load-internal("~/.emacs" t t t nil nil) load("~/.emacs" t t t) load-user-init-file("") load-init-file() command-line() normal-top-level()

1 participants
0 comments

Assertion failure in mule-charset.h? 25 years, 6 months

Stephen J. Turnbull

21.0 "Pyrenean63" XEmacs Lucid (beta63) just dumped core for me on the following: xemacs -vanilla & M-: ?\x2020 Repeatable for me. I'm too beat to follow this up tonight, and won't have time until the weekend, so here's what I have. Lisp backtrace follows: prin1(Fatal error: assertion failed, file mule-charset.h, line 485, RECORD_TYPEP (_obj, lrecord_charset) || MARKED_RECORD_P (_obj) gdb where: GNU gdb 4.17.19981224.m68k.objc.threads.hwwp.fpu.gnat Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... Core was generated by `xemacs -vanilla'. Program terminated with signal 6, Aborted. Reading symbols from /lib/nfslock.so.0...done. Reading symbols from /usr/lib/libaudio.so.2...done. Reading symbols from /usr/lib/libcanna.so.1...done. Reading symbols from /usr/lib/libRKC.so.1...done. Reading symbols from /usr/X11R6/lib/Xaw3d/libXaw.so.6...done. Reading symbols from /usr/lib/libcompface.so.1...done. Reading symbols from /usr/lib/libtiff.so.3...done. Reading symbols from /usr/lib/libpng.so.2...done. Reading symbols from /usr/lib/libjpeg.so.62...done. Reading symbols from /usr/lib/libz.so.1...done. Reading symbols from /usr/X11R6/lib/libXpm.so.4...done. Reading symbols from /usr/X11R6/lib/libXmu.so.6...done. Reading symbols from /usr/X11R6/lib/libXt.so.6...done. Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Reading symbols from /usr/X11R6/lib/libSM.so.6...done. Reading symbols from /usr/X11R6/lib/libICE.so.6...done. Reading symbols from /lib/libdl.so.2...done. Reading symbols from /lib/libdb.so.2...done. Reading symbols from /usr/lib/libgdbm.so.1...done. Reading symbols from /lib/libncurses.so.4...done. Reading symbols from /lib/libm.so.6...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. Reading symbols from /lib/libnss_files.so.2...done. Reading symbols from /lib/libnss_compat.so.2...done. Reading symbols from /lib/libnsl.so.1...done. Reading symbols from /lib/libnss_dns.so.2...done. Reading symbols from /lib/libresolv.so.2...done. #0 0x40354b21 in kill () (gdb) where #0 0x40354b21 in kill () #1 0x4035477f in raise () #2 0x40355ec8 in abort () #3 0x80c44ce in assert_failed (file=0x82598ee "mule-charset.h", line=485, expr=0x82598af "RECORD_TYPEP (_obj, lrecord_charset) || MARKED_RECORD_P (_obj)") at emacs.c:2608 #4 0x80f141a in non_ascii_set_charptr_emchar (str=0xbfffee2d "P=\b(I"(B", c=8224) at mule-charset.h:733 #5 0x819f7a7 in print_internal (obj={gu = {type = Lisp_Type_Char, val = 8224}, s = {bits = 0, val = 16449}, u = {bits = 0, val = 16449}, ui = 32898, i = 32898, v = 0x8082, cv = 0x8082}, printcharfun={gu = { type = Lisp_Type_Record, val = 34559003}, s = {bits = 0, val = 69118006}, u = {bits = 0, val = 69118006}, ui = 138236012, i = 138236012, v = 0x83d506c, cv = 0x83d506c}, escapeflag=1) at print.c:1131 #6 0x819dba0 in Fprin1 (object={gu = {type = Lisp_Type_Char, val = 8224}, s = {bits = 0, val = 16449}, u = {bits = 0, val = 16449}, ui = 32898, i = 32898, v = 0x8082, cv = 0x8082}, stream={gu = { type = Lisp_Type_Record, val = 34559003}, s = {bits = 0, val = 69118006}, u = {bits = 0, val = 69118006}, ui = 138236012, i = 138236012, v = 0x83d506c, cv = 0x83d506c}) at print.c:506 #7 0x80d0858 in Fbacktrace (stream={gu = {type = Lisp_Type_Record, val = 34559003}, s = {bits = 0, val = 69118006}, u = {bits = 0, val = 69118006}, ui = 138236012, i = 138236012, v = 0x83d506c, cv = 0x83d506c}, detailed={gu = {type = Lisp_Type_Record, val = 34531798}, s = {bits = 0, val = 69063596}, u = {bits = 0, val = 69063596}, ui = 138127192, i = 138127192, v = 0x83ba758, cv = 0x83ba758}) at eval.c:4936 #8 0x80c1c2c in fatal_error_signal (sig=6) at emacs.c:245 #9 <signal handler called> #10 0x0 in ?? () (gdb) quit -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."

1 participants
0 comments

Problems with etags in 21.2.14 25 years, 6 months

Peter B. West

When I try to find a tag in 21.2.14, I get a "... not a valid tags file" message. The problem does not occur in 21.0.67, with the same tags-table-alist entries. In 0.67 I am asked if I want to build a completion table. I don't get that far (understandably, I suppose) in 2.14. -- __ /__ Peter B. West p.west(a)uq.net.au / http://www.uq.net.au/~zzpwest / "Lord, to whom shall we go?"

1 participants
0 comments

Re: Accessing /:path in XEmacs 25 years, 6 months

Michael Sperber

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: Stephen> The file system interface is harder, since it's an every minute of Stephen> every day interface; but maybe we should bite the bullet and try to Stephen> rationalize it. Just FYI, I've had a student working on this for a term project. (Hard problem ...) It'll be a while until it's ready for primetime, but a prototype is already working. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: how to debug .emacs? 25 years, 6 months

Stephen Tse

"T. Kurosaka - Sun Professional Services" <kuro(a)Japan.Sun.COM> writes: I once wrote a little hack for parenthesis checking. I am not sure if this'd be helpful to you. ------------ (defun pbug () "Check parenthesis bugs or similar horrors. Even with Emacs advanced programming facilities, checking mismatching parenthesis or missing quote (so called \"pbug\") is no less annoying than pointer chasing in C. This function divides the buffer into regions and tries evaluating them one by one. It stops at the first region where it fails to evaluate because of pbug or any other errors. It sets point and mark (and highlights if `transient-mark-mode' is on) on the failing region and center its first line. \"^def\" is used to define regions. You may also `eval-region' right after pbug is done to let lisp parse pinpoint the bug. No more \"End of file during parsing\" horrors!" (interactive) (let ((point (point)) (region-regex "^(def..") defs beg end) (goto-char (point-min)) (setq defs (loop while (search-forward-regexp region-regex nil t) collect (point-at-bol))) ;; so it evals last definition (nconc defs (list (point-max))) (setq beg (point-min)) (while defs (goto-char beg) (setq end (pop defs)) ;; to be cool, uncomment these to see pbug doing step by step ;; (message "checking pbug from %s to %s..." beg end) ;; (sit-for 1) (when (eq (condition-case nil (eval-region beg (1- end)) (error 'pbug-error)) 'pbug-error) (push-mark end 'nomsg 'activate) (goto-char beg) (recenter) (error "a pbug found from %s to %s" beg end)) (setq beg end)) (goto-char point) (message "no pbug found"))) (define-key emacs-lisp-mode-map [(super c) p] 'pbug) > I finally managed to build and install XEmacs 21.2.13 but > starting up xemacs gives me the "internal input stream" error > in the window. I still can edit but would like to fix > the problem. The lisp stack trace, when run with > -debug-init is as followings. What could cause this > error? Running xemacs with -q doesn't show any error > so the problem must be in my .emacs. I'd like to know > if there is any easy way to locate the offending line. > > Signaling: (end-of-file "internal input stream") > load-internal("~/.emacs" t t t undecided) > load("~/.emacs" t t t) > load-user-init-file("") > load-init-file() > command-line() > normal-top-level() > > -kuro

1 participants
0 comments

Re: [21.1] Important NT process fix 25 years, 6 months

Jason R Mastaler

Andy Piper <andy(a)xemacs.org> writes: > This is a fixed version of the patch I posted last week. I think it is > important that this patch makes it into the mswindows binary kit as things > like jde rely on the behviour it enables (besides the bugs it fixes). Okay, then we will use a 21.1 release that has this patch incorporated as a base for the ms-windows binary-kits.

1 participants
0 comments

how to debug .emacs? 25 years, 6 months

T. Kurosaka - Sun Professional Services

I finally managed to build and install XEmacs 21.2.13 but starting up xemacs gives me the "internal input stream" error in the window. I still can edit but would like to fix the problem. The lisp stack trace, when run with -debug-init is as followings. What could cause this error? Running xemacs with -q doesn't show any error so the problem must be in my .emacs. I'd like to know if there is any easy way to locate the offending line. Signaling: (end-of-file "internal input stream") load-internal("~/.emacs" t t t undecided) load("~/.emacs" t t t) load-user-init-file("") load-init-file() command-line() normal-top-level() -kuro

2 participants
3 comments

Re: Accessing /:path in XEmacs 25 years, 6 months

Hrvoje Niksic

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > > Is this a serious proposal or a quick hack suggestion? I'd > > rather do it right than introduce ugly hacks. > > I consider it serious. I don't want this stuff hacked into the > guts of Fexpand_file_name or something like that. I've had to > hack extraneous filename munging out of Emacs in the past. > //path had a special meaning (...) But /: is designed exactly to solve these problems. In your case, you would access // as /:// and things would just work. /: is not yet another special meaning, it *removes* special meanings.

4 participants
3 comments

[21.1.2] Gnus, PGP, and MULE 25 years, 6 months

Jerry James

I am not familiar with MULE at all, and can't say that I read bytecode, so I'm asking for a little guidance here. I compiled XEmacs 21.1.2 without MULE (on Irix 6.2 and various flavors of Solaris), installed the non-MULE SUMO, and have been putting the result through its paces. At one point, I tried to file a bug report. I got an error instead, "Symbol's value as variable is void: mime-charset-coding-system-alist". Somewhat surprised, I just did a setq of that variable to nil and continued. Then I got "Symbol's function definition is void: find-coding-system". Digging a little further, I see the following chain of events. I am a Gnus user. I am also a PGP user. So when my .gnus is loaded, tm-pgp.el gets loaded as well in support of the PGP-related hooks. In turn, tm-pgp.el loads tm-play.el. Poking around in tm-play.el, I found that evaluation led to two errors. First, this definition on line 271: (defvar mime-article/coding-system-alist (list (cons 'mh-show-mode *noconv*) (cons t (mime-charset-to-coding-system default-mime-charset)) )) produces the message "defvar treated as defconst". Second, everything above this point is defined; neither this variable nor anything below it is defined. Evaluating the body of this variable definition in *scratch* leads to the unsurprising result: ((mh-show-mode) (t . iso-8859-1)) However, look at the first part of this Lisp backtrace (manually wrapped): Signaling: (void-variable mime-charset-coding-system-alist) byte-code("..." [boundp mime-article/coding-system-alist mh-show-mode *noconv* t default-mime-charset nil lbt charset intern mime-charset-coding-system-alist cs format "%s-%s" CRLF dos LF unix CR mac find-coding-system mime-charset-to-coding-system-default-method current-load-list MULE mime-article::write-region #<compiled-function (start end file) "...(19)" [major-mode mime-article/coding-system-alist t file-coding-system write-region start end file] 4> featurep mule #<compiled-function (start end file) "...(19)" [major-mode mime-article/coding-system-alist t coding-system-for-write write-region start end file] 4> NEMACS #<compiled-function (start end file) "...(19)" [major-mode mime-article/kanji-code-alist t kanji-fileio-code write-region start end file] 4> defalias write-region] 10) load-internal("tm-play" nil t nil nil nil) load("tm-play" nil t nil) require(tm-play) load-internal("tm-pgp" nil t nil nil nil) load("tm-pgp" nil t nil) require(tm-pgp) It looks to me like this file was byte-compiled with a MULE-enabled XEmacs. Am I right? I'm not certain, because I tried to recompile it and got the same error message out of the byte compiler. Am I barking up the wrong tree? Any direction is much appreciated. Thanks, -- Jerry James Email: jerry(a)cs.ucsb.edu WWW: http://www.cs.ucsb.edu/~jerry/

1 participants
0 comments

Re: New mailcrypt status -- GNUPG-0.9.6 is broken 25 years, 6 months

Andrew Hobson

On Sat, 15 May 1999 08:00:35 -0500, "William M. Perry" <wmperry(a)aventail.com> said: > Welcome to digital unix - it sucks, and the linker sucks worse. IMHO, it's not a problem with digital unix, but a problem with a poorly written configure script. This patch to configure.in fixes the compile for me. I don't use gnupg, so I can't tell if it's working correctly or not. Drew -- There followed a period of embarrassment as the rumour went round London that Joey Mellen had trepanned himself, whereas in fact he had failed to do so.

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 1999