From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Postponing messages
Date: 29 Oct 1998 11:51:17 +0100 [thread overview]
Message-ID: <m3r9vrabfe.fsf@sparky.gnus.org> (raw)
In-Reply-To: Chris Tessone's message of "28 Oct 1998 03:45:39 -600"
Chris Tessone <tessone@imsa.edu> writes:
> Yup. Same here. I suppose that having something like:
>
> (setq gnus-buffers-naming 'classic)
> or
> (setq gnus-buffers-naming 'newage)
Ok; I've now extended message-generate-new-buffers to have `unique'
and `unsent' as values. Defaults to the current behavior.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-10-29 10:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-24 23:17 Lars Magne Ingebrigtsen
1998-10-24 23:31 ` Chris Tessone
1998-10-24 23:53 ` Harry Putnam
1998-10-27 12:54 ` Robert Bihlmeyer
1998-10-27 16:06 ` Dan Christensen
1998-10-28 7:27 ` Lars Magne Ingebrigtsen
1998-10-28 9:17 ` Lee Willis
1998-10-29 10:39 ` Lars Magne Ingebrigtsen
1998-10-29 10:55 ` Lee Willis
1998-10-28 9:31 ` Hrvoje Niksic
1998-10-28 9:45 ` Chris Tessone
1998-10-29 10:51 ` Lars Magne Ingebrigtsen [this message]
1998-10-26 17:24 ` Hallvard B Furuseth
1998-10-26 21:10 ` Lars Magne Ingebrigtsen
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=m3r9vrabfe.fsf@sparky.gnus.org \
--to=larsi@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).