From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: mime XEmacs (no-mule) bugs
Date: 15 Nov 1998 17:00:43 -0500 [thread overview]
Message-ID: <vxkvhkgsjjo.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Wes Hardaker's message of "15 Nov 1998 13:43:06 -0800"
Wes Hardaker <wjhardaker@ucdavis.edu> writes:
> (defun mm-find-charset-region (b e) '(ascii))
> (defun find-charset-region (b e) '(ascii))
Thanx for the interim workaround.
> (And the .47 patch didn't fix all the problems Lars, only once
> instance of this)
Aye. I'm still desperately trying to be able to `B m' some messages
around, and the next level of difficulty is:
Signaling: (void-variable current-language-environment)
mm-find-charset-region(1 1295)
mm-encode-body()
mml-generate-mime-1((part (type . "text/plain") (contents . "[content deleted]")))
mml-generate-mime()
message-encode-message-body()
gnus-request-accept-article("nnml:tomb" nil t)
eval((gnus-request-accept-article "nnml:tomb" (quote nil) t))
nnml-request-move-article(30701 "mailer-daemon" "" (gnus-request-accept-article "nnml:tomb" (quote nil) t) t)
gnus-request-move-article(30701 "nnml:mailer-daemon" "" (gnus-request-accept-article "nnml:tomb" (quote nil) t) t)
gnus-summary-move-article(nil)
call-interactively(gnus-summary-move-article)
With Wes' quick fix above in place, I am able to do a `B m', however
the resulting message in the new group is _tripled_ (as I reported
yesterday, when reporting p0.46 DOA under non-MULE XEmacs), and
contains an erroneous opening newline.
next prev parent reply other threads:[~1998-11-15 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-15 21:43 Wes Hardaker
1998-11-15 22:00 ` Karl Kleinpaste [this message]
1998-11-15 22:53 ` Lars Magne Ingebrigtsen
1998-11-16 0:48 ` Chris Tessone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vxkvhkgsjjo.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).