From: Jon Allen Boone <tex@delamancha.org>
Subject: Re: latest CVS won't forward messages
Date: Sat, 21 Jul 2001 14:59:10 -0400 [thread overview]
Message-ID: <m3n15yds75.fsf@amicus.delamancha.org> (raw)
In-Reply-To: <vxk3d7qtans.fsf_-_@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Sat, 21 Jul 2001 14:11:19 -0400")
Karl Kleinpaste <karl@charcoal.com> writes:
> Jon Allen Boone <tex@delamancha.org> writes:
>> This seems to work Ok for me. I tried calling it via M-x
>> gnus-summary-mail-forward and using the key-binding S-o-m. The only
>> difference seems to be that I'm using XEmacs 21.1 patch 14 and
>> you're using a newer one. Do you think that this could be an XEmacs
>> bug?
>
> Doesn't look like it.
>
> Since you said it works for you, I tried it a few more times. It
> seems to be the case that the very first forwarding I do in a single
> XEmacs works. Every subsequent attempt gives me that same error.
I get the same behavior after the first forwarding.
-jon
--
------------------
Jon Allen Boone
tex@delamancha.org
next prev parent reply other threads:[~2001-07-21 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-21 14:27 Karl Kleinpaste
[not found] ` <m3g0bqfbwz.fsf@amicus.delamancha.org>
2001-07-21 18:11 ` Karl Kleinpaste
2001-07-21 18:59 ` Jon Allen Boone [this message]
2001-07-21 20:20 ` ShengHuo ZHU
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=m3n15yds75.fsf@amicus.delamancha.org \
--to=tex@delamancha.org \
/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).