Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@iskon.hr>
Subject: Re: Suggested features
Date: 16 Nov 1999 10:31:46 +0100	[thread overview]
Message-ID: <9t9n1seok8t.fsf@mraz.iskon.hr> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "16 Nov 1999 10:10:07 +0100"

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> > > However, I would much prefer to have that automated to some
> > > degree - eg push keystroke that corresponds to 'attach message',
> > > which will allow you to browse and select a message that you
> > > want to attach. Maybe this is easier said then done.
> > 
> > I can't imagine how to do this.
> 
> Allow the user to enter any group and select any article.  Upon the
> user pressing some key, insert the *Article* buffer into the message
> being composed.

Even better, the command should follow the process/prefix convention,
so that you can attach several articles of your choice, *after* you
start composing a message.  I've always missed this feature.

> Is there already a command for attaching a buffer?  Maybe that would
> be sufficient.

Attaching an *Article* buffer is a bad idea because it's already
washed.  Original article text (which is stored in a separate buffer)
is what you'd have to attach.


  reply	other threads:[~1999-11-16  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-15  0:37 Mr Brian May
1999-11-15 19:55 ` Lars Magne Ingebrigtsen
1999-11-15 23:43   ` Brian May
1999-11-16 16:53     ` Lars Magne Ingebrigtsen
1999-11-16  9:10   ` Kai Großjohann
1999-11-16  9:31     ` Hrvoje Niksic [this message]
1999-11-16 16:53       ` Lars Magne Ingebrigtsen
1999-11-16 16:57         ` Hrvoje Niksic
1999-11-16 17:04         ` Kai Großjohann
1999-11-17  8:26           ` Hrvoje Niksic
1999-12-01 14:58           ` 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=9t9n1seok8t.fsf@mraz.iskon.hr \
    --to=hniksic@iskon.hr \
    /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).