From: Francis Moreau <francis.moro@gmail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: david.goldberg6@verizon.net (Dave Goldberg), ding@gnus.org
Subject: Re: buffer layout when composing
Date: Mon, 14 Feb 2011 12:39:23 +0100 [thread overview]
Message-ID: <m2d3mukfpw.fsf@gmail.com> (raw)
In-Reply-To: <87pqquvqkd.fsf@member.fsf.org> (Tassilo Horn's message of "Mon, 14 Feb 2011 11:49:38 +0100")
Tassilo Horn <tassilo@member.fsf.org> writes:
[...]
>
> Following up to a message with yank will make the message-buffer be
> shown in one and only window. However, when sending off the message,
> the complete window config is restored again, which is the most
> important thing IMO.
>
For me both are important.
>
> Following up without yank will produce a 2 window config with the
> article buffer above and the message buffer below.
>
But it still replaces all other (no gnus) windows.
>
> Basically, that's pretty good, but I agree that it would be even
>better if Gnus would only remove Gnus windows.
Hmm, I really find it annoying and I would love see it fixed.
Why don't Gnus always use the summary window layout as basis to
calculate article, message window layout ?
Why does it take the full window ?
--
Francis
next prev parent reply other threads:[~2011-02-14 11:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 14:40 Francis Moreau
2011-02-13 19:25 ` Lars Ingebrigtsen
2011-02-13 20:01 ` Francis Moreau
2011-02-13 23:45 ` Dave Goldberg
2011-02-14 8:26 ` Francis Moreau
2011-02-14 9:20 ` Tassilo Horn
2011-02-14 10:21 ` Francis Moreau
2011-02-14 10:49 ` Tassilo Horn
2011-02-14 11:39 ` Francis Moreau [this message]
2011-02-14 20:38 ` Lars Ingebrigtsen
2011-02-14 22:17 ` Francis Moreau
2011-02-14 22:34 ` Lars Ingebrigtsen
2011-02-15 8:09 ` Francis Moreau
2011-02-15 22:39 ` Dave Goldberg
2011-02-16 22:16 ` Lars Ingebrigtsen
2011-02-19 11:17 ` Francis Moreau
2011-02-20 1:23 ` Lars 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=m2d3mukfpw.fsf@gmail.com \
--to=francis.moro@gmail.com \
--cc=david.goldberg6@verizon.net \
--cc=ding@gnus.org \
--cc=tassilo@member.fsf.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).