From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Cc: ding@ifi.uio.no
Subject: Re: Probs with mailreading.
Date: 09 Jun 1996 23:37:36 +0200 [thread overview]
Message-ID: <vafbuisirq7.fsf@ls6.informatik.uni-dortmund.de> (raw)
In-Reply-To: Jens Lautenbacher's message of 09 Jun 1996 00:00:57 +0200
>>>>> On 09 Jun 1996 00:00:57 +0200, Jens Lautenbacher
>>>>> <jens@lemcbed.lem.uni-karlsruhe.de> said:
Jens> b) I would like to have all replies, followups or postings in
Jens> my mail groups be saved to the group I'm posting or
Jens> replying from. E.g. if I post an article (or reply) to
Jens> jtl@tkm.physik.uni-karlsruhe.de, this message should be
Jens> stuffed into the "nnfolder+private:JTL" group. Is there any
Jens> reasonable way to achieve this? Mails out of the "Misc"
Jens> groups and newspostings should of course still be stuffed
Jens> into "nnfolder+archive: misc-mail" or "...misc-news"
I use the following setup.
,-----
| (defun kai-gnus-outgoing-message-group ()
| (cond ((and gnus-newsgroup-name
| (stringp gnus-newsgroup-name)
| (string-match "^nnml" gnus-newsgroup-name))
| gnus-newsgroup-name)
| (t "nnml:mail.misc")))
| (setq gnus-outgoing-message-group 'kai-gnus-outgoing-message-group)
`-----
You probably want to twiddle the method and the default group name, I
think.
I also have a nifty (but poorly implemented) function
(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")))))))
If I bind this to a key, something useful happens: If the Gcc header
is already in there, it will be deleted, if it isn't, a Gcc header
will be created that contains the `right' group name.
Suggestions for a cleaner implementation gladly accepted :-)
Whatcha think?
kai
--
Life is hard and then you die.
prev parent reply other threads:[~1996-06-09 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-08 22:00 Jens Lautenbacher
1996-06-08 22:35 ` Jens Lautenbacher
1996-06-09 4:14 ` Lars Magne Ingebrigtsen
1996-06-11 10:02 ` Jens Lautenbacher
1996-06-11 18:26 ` Lars Magne Ingebrigtsen
1996-06-12 8:13 ` Jens Lautenbacher
1996-06-12 18:13 ` Lars Magne Ingebrigtsen
1996-06-13 7:43 ` Jens Lautenbacher
1996-06-13 20:15 ` Lars Magne Ingebrigtsen
1996-06-14 0:41 ` Firebeard
1996-06-14 1:37 ` Lars Magne Ingebrigtsen
1996-06-09 21:37 ` Kai Grossjohann [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=vafbuisirq7.fsf@ls6.informatik.uni-dortmund.de \
--to=grossjoh@charly.informatik.uni-dortmund.de \
--cc=ding@ifi.uio.no \
/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).