From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Can't post-followup or post-forward in nnml groups
Date: Wed, 01 Aug 2001 11:55:36 +0200 [thread overview]
Message-ID: <vaf8zh4cdev.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <yosu4rrswwdd.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 01 Aug 2001 07:45:50 +0900")
On Wed, 01 Aug 2001, Katsumi Yamaoka wrote:
> --- gnus-msg.el~ Wed Jul 25 22:17:04 2001
> +++ gnus-msg.el Tue Jul 31 22:43:02 2001
> @@ -649,7 +649,9 @@
> (defun gnus-post-method (arg group &optional silent)
> "Return the posting method based on GROUP and ARG.
> If SILENT, don't prompt the user."
> - (let ((group-method (gnus-find-method-for-group group)))
> + (let ((group-method
> + (or (car (gnus-group-find-parameter group 'gnus-post-method t))
> + (gnus-find-method-for-group group))))
> (cond
> ;; If the group-method is nil (which shouldn't happen) we use
> ;; the default method.
Up to now, the convention has been that special group parameters get
short names, and the gnus-foo names have just been local variables.
How about renaming that parameter to `post-method' and documenting it
along with all the other group parameters?
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2001-08-01 9:55 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
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 [this message]
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=vaf8zh4cdev.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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).