From: Frank Haun <pille3003@fhaun.de>
Subject: Re: Proper Gnus rebuilding technique?
Date: Mon, 03 Mar 2003 01:01:00 +0100 [thread overview]
Message-ID: <u7kbhl3nn.fsf@pille.fhaun.de> (raw)
In-Reply-To: <uel5pl4zo.fsf@pille.fhaun.de>
Frank Haun <pille3003@fhaun.de> writes:
[gnus-unload]
> Seems to work.
Addition, I got:
mailcap-mime-info: Symbol's function definition is void:
mail-header-parse-content-type
so I have to load `mail-parse'.
,----[ C-h f gnus-unload RET ]
| [...]
| Use cautiously -- unloading may cause trouble.
`----
Yes.
Frank
prev parent reply other threads:[~2003-03-03 0:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 23:46 Envelope sender lost from sending after gnus-draft-edit-message Jesper Harder
2003-03-02 0:25 ` Andrew A. Raines
2003-03-02 0:50 ` Jesper Harder
2003-03-02 6:24 ` Andrew A. Raines
2003-03-02 16:47 ` Jesper Harder
2003-03-02 21:13 ` Proper Gnus rebuilding technique? (was: Envelope sender lost from sending after gnus-draft-edit-message) Andrew A. Raines
2003-03-02 22:19 ` Proper Gnus rebuilding technique? Jesper Harder
2003-03-02 23:32 ` Frank Haun
2003-03-02 23:47 ` Jesper Harder
2003-03-03 0:47 ` Michael Shields
2003-03-03 22:24 ` Frank Haun
2003-03-31 17:48 ` Lars Magne Ingebrigtsen
2003-03-03 0:01 ` Frank Haun [this message]
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=u7kbhl3nn.fsf@pille.fhaun.de \
--to=pille3003@fhaun.de \
--cc=news-reply@fhaun.de \
/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).