From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: Can't post-followup or post-forward in nnml groups
Date: Tue, 31 Jul 2001 12:30:46 -0500 [thread overview]
Message-ID: <q6md76hngzd.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <vafu1ztnr1a.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 31 Jul 2001 15:53:37 +0200")
>>>>> On Tue, 31 Jul 2001 15:53:37 +0200,
>>>>> Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> (kg) writes:
kg> (setq gnus-parameters
kg> `(("^nnml:" (gnus-post-method ,gnus-select-method))))
Cool! I never knew about this. Guess I overlooked it in the past.
Occasionally I would wonder if there was a way to set '(display
. all) on all my IMAP folders. This looks to be the trick.
Do group-specific parameters override gnus-parameters?
Now if only I could supply a default response to
gnus-large-newsgroup to these IMAP folders as well. (Always open
say the last 100 or so messages, rather than getting prompted for a
message count each time. I could set this gnus-large-newsgroup
variable to something really huge so I'm not prompted, but
considering the size of some of my/our IMAP folders, that would be a
drag. ;-)
--
Amos
next prev parent reply other threads:[~2001-07-31 17:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 9:01 Katsumi Yamaoka
2001-07-31 11:07 ` Kai Großjohann
2001-07-31 12:28 ` Katsumi Yamaoka
2001-07-31 13:53 ` Kai Großjohann
2001-07-31 17:30 ` Amos Gouaux [this message]
2001-07-31 17:51 ` Kai Großjohann
2001-08-05 17:34 ` Amos Gouaux
2001-08-05 20:04 ` Kai Großjohann
2001-08-05 20:56 ` Amos Gouaux
2001-08-05 21:35 ` Kai Großjohann
2001-07-31 22:45 ` Katsumi Yamaoka
2001-08-01 0:53 ` ShengHuo ZHU
2001-08-01 8:43 ` Didier Verna
2001-08-01 9:55 ` Kai Großjohann
2001-08-01 10:18 ` Katsumi Yamaoka
2001-08-01 11:04 ` Kai Großjohann
2001-08-01 11:38 ` Katsumi Yamaoka
2001-08-02 10:59 ` Katsumi Yamaoka
2001-08-03 4:57 ` ShengHuo ZHU
2001-08-03 7:03 ` Katsumi Yamaoka
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=q6md76hngzd.fsf@spartacus.utdallas.edu \
--to=amos+lists.ding@utdallas.edu \
/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).