From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Better handling of reply configuration
Date: 16 Mar 2000 00:43:21 +0100 [thread overview]
Message-ID: <vaf3dprkdeu.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Reid Rivenburgh's message of "15 Mar 2000 15:05:13 -0700"
Reid Rivenburgh <reid@lanl.gov> writes:
> The problem is that when replying, the reply buffer takes over the
> frame.
Not true for me. I haven't changed the default settings concerning
windows.
When I hit `R' or `F', the original article buffer disappears and the
reply buffer takes the whole frame. This is okay, since the original
article is quoted in the reply and can therefore be seen.
When I hit `r' or `f', the frame is split, showing both the original
article and the reply.
Did you change the frame/window configuration?
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2000-03-15 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 22:05 Reid Rivenburgh
2000-03-15 23:43 ` Kai Großjohann [this message]
2000-03-15 23:51 ` Reid Rivenburgh
2000-03-16 0:20 ` Kai Großjohann
2000-03-16 18:03 ` David S. Goldberg
2000-03-16 22:42 ` Reid Rivenburgh
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=vaf3dprkdeu.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@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).