From: Lee Willis <lee@gbdirect.co.uk>
Subject: Request ....
Date: 11 Dec 1998 10:14:29 +0000 [thread overview]
Message-ID: <lzemq7kmt6.fsf@landlord.gbdirect.co.uk> (raw)
Well in the true nature of awkward customers I'm going to request
something that I requested the exact opposite of before :)
A while ago I mentioned here that when replying to articles which had
buttons the button text was included which was, for that situation a
messy thing to do, I've now however found a situation where it would be
useful to have a command gnus-summary-reply-buttonized or something
similar.
To justify this I have a message which contains only a MIME attachment
(A sound file ...) and I wish to reply to the message (To say thank you,
I enjoyed etc. etc.). As it is it makes no sense to reply as there is no
idincation (Other than In-Reply-To: etc headers) of what I'm replying
to. I think it'd be nice if they got a reply something like below
Someone (foo@bar.baz.bat) writes:
> [application/octet-stream foo.wav 1024]
>
My comments go here :)
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next reply other threads:[~1998-12-11 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-11 10:14 Lee Willis [this message]
1998-12-13 2:29 ` Request Justin Sheehy
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=lzemq7kmt6.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).