From: David Kastrup <dak@gnu.org>
Subject: Re: Missing custom-defs for SOUP
Date: Fri, 05 Jan 2007 21:02:19 +0100 [thread overview]
Message-ID: <858xghdyyc.fsf@lola.goethe.zz> (raw)
In-Reply-To: <v9ejq966b1.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri\, 05 Jan 2007 12\:50\:42 +0100")
Reiner Steib <reinersteib+from-uce@imap.cc> writes:
> On Fri, Jan 05 2007, David Kastrup wrote:
>
>> (info "(gnus) Soup commands")
> [...]
>> There are a few variables to customize where Gnus will put all these
>> thingies:
>>
>> but none of the mentioned variables are actually known to
>> `customize'. That would be worth fixing.
>
> I have installed a change in Emacs CVS (and Gnus v5-10). As I don't
> use SOUP at all, could you please check and fix when needed? Thanks.
Well, it will get little testing since I could only do the CVS update
now that my internet provider has finally managed to get me online
again, and so my need for soup evaporated pretty much.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2007-01-05 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86ps9tkbo3.fsf@lola.quinscape.zz>
2007-01-05 11:50 ` Reiner Steib
2007-01-05 20:02 ` David Kastrup [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=858xghdyyc.fsf@lola.goethe.zz \
--to=dak@gnu.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).