From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Bug? pgnus 0.95
Date: 28 Jul 1999 17:39:21 +0200 [thread overview]
Message-ID: <vafd7xclr6e.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: Lee Willis's message of "28 Jul 1999 14:28:15 +0100"
Lee Willis <lee@gbdirect.co.uk> writes:
> I tootle around and read my mail, then say for example I want to compose
> a new mail. I'm in the Group buffer with point over some indeterminate
> group (At this point I don't care and shouldn't have to care which!) and
> hit 'm' to compose a new message.
FWIW, I have the following instead of the gcc-self mechanism. It
pretty much does the same thing but provides a default. Maybe you
would like to avoid your problem altogether and use something like
this?
(defun kai-gnus-outgoing-message-group ()
(cond ((and gnus-newsgroup-name
(stringp gnus-newsgroup-name)
(not (string= "" gnus-newsgroup-name))
(string-match "^\\(nnml\\|nnimap\\):" gnus-newsgroup-name))
gnus-newsgroup-name)
((and gnus-newsgroup-name
(stringp gnus-newsgroup-name)
(string-match "^nntodo:" gnus-newsgroup-name))
nil)
(t "nnimap:INBOX")))
(setq gnus-outgoing-message-group 'kai-gnus-outgoing-message-group)
(defun message-toggle-gcc ()
(interactive)
(save-excursion
(save-restriction
(let ((pmin (progn (beginning-of-buffer) (point)))
(pmax (progn
(beginning-of-buffer)
(re-search-forward (concat "^" mail-header-separator
"$"))
(beginning-of-line)
(point))))
(beginning-of-buffer)
(narrow-to-region pmin pmax)
(if (re-search-forward "^gcc: .*" nil t)
(progn
(beginning-of-line)
(kill-line 1))
(goto-char pmax)
(insert (concat "Gcc: "
(kai-gnus-outgoing-message-group)
"\n")))))))
The last function is useful in the message buffer.
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~1999-07-28 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-28 12:13 Lee Willis
1999-07-28 13:17 ` David S. Goldberg
1999-07-28 13:28 ` Lee Willis
1999-07-28 15:39 ` Kai Großjohann [this message]
1999-07-29 8:17 ` Jaap-Henk Hoepman
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=vafd7xclr6e.fsf@petty.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).