Gnus development mailing list
 help / color / mirror / Atom feed
From: Paul Franklin <paul@cs.washington.edu>
Subject: Re: 'e' in the summary buffer leads to lost work
Date: 23 Feb 1998 15:20:24 -0800	[thread overview]
Message-ID: <r9qiuq57vt3.fsf@torigai.cs.washington.edu> (raw)
In-Reply-To: "Edward J. Sabol"'s message of "Mon, 23 Feb 1998 16:40:34 -0500"

>>>>> Edward J. Sabol writes:

 > Excerpts from mail: (23-Feb-98)
 > 'e' in the summary buffer leads to lost work by Matt Armstrong

 >> 3) Make 'e' create a new, non-*Article* buffer.

 > I like this solution the best. The buffer name should be based on various
 > header fields in the e-mail.

I like it too, though I think it should be named after the group and
article number, as a reminder that this is fundamentally different
than an attempt to send a message out.

--Paul


  reply	other threads:[~1998-02-23 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-23 21:30 Matt Armstrong
1998-02-23 21:40 ` Edward J. Sabol
1998-02-23 23:20   ` Paul Franklin [this message]
1998-02-24 15:48     ` jari.aalto
1998-02-27 11:57   ` Lars Magne Ingebrigtsen
1998-02-27  9:24     ` Harry Putnam

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=r9qiuq57vt3.fsf@torigai.cs.washington.edu \
    --to=paul@cs.washington.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).