From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: Re: hit r on message you haven't opened yet, go ahead, do it, just do it
Date: 19 Jan 2003 11:11:23 +0800 [thread overview]
Message-ID: <87znpx96lg.fsf@jidanni.org> (raw)
> Guess what, in the group buffer enter a group with RET, now move down
> and answer a message with r. Great, one window is the reply you are
> composing, the other window is some gnus dirty internal underware
> "article copy" buffer, which BTW if you accidentally type into, you
> can't undo, not that it matters.
>
> The problem is Lards never thought one would hit r on a message he
> hasn't opened yet :-)
<If course I have thought of that. I do that all the time. Do you
<see any problems in connection with that?
Why don't you just present the *Article* buffer, like Kester said,
which you have spent such a large amount of work making pretty? Leave
the underware buffer for the pros to hit C-u g on if they need to.
BTW, I need another key.
You see I want to send a mail to dweebowitz and there is a mail from
him right there in the summary buffer, but I don't want to read or
otherwise mark or disturb that old mail. if I hit r then indeed i can
start sending a mail to him, but that disturbs the state of that
message and even generates references, etc. Anyway, my cursor is
sitting on his name in the summary buffer. Add a functionality to gnus
to do this...
hmm, for me
m runs the command gnus-summary-mail-other-window
why dont you make giving an arg to cause it to examine what is beneath
the cursor...
--
http://jidanni.org/ Taiwan(04)25854780
next reply other threads:[~2003-01-19 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 3:11 Dan Jacobson [this message]
2003-01-21 4:43 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2003-01-26 4:53 Dan Jacobson
[not found] <87bs2h2b3j.fsf@jidanni.org>
[not found] ` <yqradhzzv9b.fsf@cs.york.ac.uk>
2003-01-17 22:36 ` Nevin Kapur
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=87znpx96lg.fsf@jidanni.org \
--to=jidanni@dman.ddts.net \
/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).