May 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [21.1.2] Gnus, PGP, and MULE 26 years, 1 month

Jerry James

On 18 May 1999 at 13:20:14 -0400, nbecker(a)fred.net wrote: > rm ...xemacs-packages/lisp/tm/*.elc && C-u M-x > byte-recompile-directory fixed it for me. Okay, that fixed it for me, too. So it looks like a different set of elcs is needed for tm in the non-MULE and MULE SUMOs. Also, latex-math-symbol.el probably doesn't belong in the non-MULE SUMO (or, at least, you can't byte-compile it without MULE). Thanks, -- Jerry James Email: jerry(a)cs.ucsb.edu WWW: http://www.cs.ucsb.edu/~jerry/

1 participants
0 comments

Re: The new dumper 26 years, 1 month

Olivier Galibert

On Sat, May 15, 1999 at 07:04:03PM +0200, Hrvoje Niksic wrote: > Uhm, it feels sort of awkward to ask this (I don't want to create an > impression of pushing you), but what is the status of the new dumper? I'm finishing moving to the USA. It's almost done. Hi from Gaithersburg (near washington). BTW, the current code should work as good as before, and bugs[1] should be squashed out. The following patches will be ifdefable-out, so any existing bug is a real bug. OG. [1] I know of only two of them, the '\n' printed at the start and the leftover message in the message buffer. I think they may be related.

1 participants
0 comments

Re: [21.1.2] Gnus, PGP, and MULE 26 years, 1 month

Jan Vroonhof

nbecker(a)fred.net writes: > rm ...xemacs-packages/lisp/tm/*.elc && C-u M-x > byte-recompile-directory fixed it for me. So it is the apel defsubst problem then. What is the procedure for getting patches in APEL, mail them to Tomohiko? Jan

1 participants
0 comments

Redisplay crash 26 years, 1 month

Jan Vroonhof

I saw the XEmacs crash you reported in the bug tracking system. I cannot reproduce it. Have you used any recent betas from just before 21.2? There were a few redisplay changes that went in 21.2 as fixes for other bugs, I want to be able make sure it is or is not them. Is it feasible for you to reproduce this using an XEmacs running under a debugger so we can see at which code line it is crashing? Jan

1 participants
0 comments

Re: [Failure] 21.2b14 26 years, 1 month

Neal D. Becker

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> I (still) don't see this. sb> nbecker <nbecker(a)fred.net> writes in xemacs-beta(a)xemacs.org: >> 21.2b14 --no-mule i686-pc-linux-gnu >> Even manually fixing the scripts so that mule is detected as NIL, >> removing all .elc's from the source directory and rebuilding from >> scratch, C-x m gives: >> Symbol's value as variable is void: mime-charset-coding-system-alist >> Loading message... >> PGP version set to GPG. >> Loading mc-setversion...done >> Loading mc-setversion... >> ... sb> How did you install APEL? Did you install it from the -pkg.tar.gz on sb> ftp.xemacs.org, or did you build it yourself? Could you please get a sb> lisp stack backtrace by doing (setq debug-on-error t) and reproducing sb> the error? Thanks. I installed from the standard packaging. The same package files are being used by 21.2b13 (in which I'm typing this message) without any problem. 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) (lambda nil (require (quote tm-pgp)))() run-hooks((lambda nil (require (quote tm-pgp)))) 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>() run-hooks(#<compiled-function nil "...(4)" [require message-mime] 2>) byte-code("..." [run-hooks message-load-hook provide message] 2) load-internal("message" nil nil nil nil nil) load("message" nil nil nil) message-mail(nil nil nil nil nil nil nil) #<compiled-function (&optional to subject other-headers continue switch-function yank-action send-actions) "...(20)" [mail-user-agent composefunc function to subject other-headers continue switch-function yank-action send-actions] 9 730205 (list nil nil nil current-prefix-arg)>(nil nil nil nil) call-interactively(compose-mail)

2 participants
2 comments

Re: Assertion failure in mule-charset.h? 26 years, 1 month

Jan Vroonhof

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > >>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: > > However ... shouldn't we be pedantic and restrict the feature to > ASCII? The problem is what to do with stuff like x-iso8859-1.el then. Jan

1 participants
0 comments

Re: [21.1.2] Gnus, PGP, and MULE 26 years, 1 month

Neal D. Becker

rm ...xemacs-packages/lisp/tm/*.elc && C-u M-x byte-recompile-directory fixed it for me.

1 participants
0 comments

Re: [21.1.2] Gnus, PGP, and MULE 26 years, 1 month

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > jerry(a)cs.ucsb.edu (Jerry James) writes: > > > (defvar mime-article/coding-system-alist > > (list (cons 'mh-show-mode *noconv*) > > (cons t (mime-charset-to-coding-system default-mime-charset)) > > )) > > The problem seems to be that mime-charset-to-coding-system is a > defsubst which means that bytecompiling will inline it. Bad bad bad. defsubst'ing a function is almost always wrong. It should be done _only_ when you know there's a non-negligible impact on performance. mime-charset-to-coding-system doesn't sound like such a case at all.

1 participants
0 comments

Re: Assertion failure in mule-charset.h? 26 years, 1 month

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > 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. Martin Buchholz's patch available at <URL:http://www.xemacs.org/list-archives/xemacs-patches/9903/msg00041.html> should be applied to 21.0.

2 participants
1 comments

Re: [21.1.2] Gnus, PGP, and MULE 26 years, 1 month

Jan Vroonhof

jerry(a)cs.ucsb.edu (Jerry James) writes: > (defvar mime-article/coding-system-alist > (list (cons 'mh-show-mode *noconv*) > (cons t (mime-charset-to-coding-system default-mime-charset)) > )) The problem seems to be that mime-charset-to-coding-system is a defsubst which means that bytecompiling will inline it. However that is wrong in compatibility code. The packages are probably compiled using a Mule XEmacs as you guessed so the mule version gets in to the .elc. Recompiling _should_ work. If you 'rm lisp/tm/*.elc' and then M-x byte-recompile-directory, does the problem get away? Jan

1 participants
0 comments

2025

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