From: Francis Moreau <francis.moro@gmail.com>
To: david.goldberg6@verizon.net (Dave Goldberg)
Cc: ding@gnus.org
Subject: Re: buffer layout when composing
Date: Mon, 14 Feb 2011 09:26:58 +0100 [thread overview]
Message-ID: <m2d3mvkoml.fsf@gmail.com> (raw)
In-Reply-To: <84oc6fwlay.fsf@davestoy.home> (Dave Goldberg's message of "Sun, 13 Feb 2011 18:45:41 -0500")
david.goldberg6@verizon.net (Dave Goldberg) writes:
>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>> Francis Moreau <francis.moro@gmail.com> writes:
>>>
>>>> Is there an easy way for doing that ?
>>>
>>> Sure. See the Window Layout section in the manual.
>
>> Well, I was expecting this answer but I did try to understand what's
>> written in this section but failed. At least to achieve what I'm trying
>> to do (replacing the article window by the composing one).
>
>> I can see how to configure a general layout but it won't replace the
>> article window only in my setting.
>
>> Could you give me a hint how to do that ?
>
> Somewhere in your gnus-buffer-configuration you should have a member
> like this (mine is customized, so yours, presumably the default, won't
> look quite the same):
>
> ((article
> (horizontal 1.0
> (vertical 84
> (summary 0.25 point)
> (article 1.0))
> (vertical 1.0
> (group 1.0)))))
>
> What you want to do is add similar members for at least message, and
> possibly 'reply, forward and others that might be used for message
> generation (there's a bunch, but many aren't used so often that
> perhaps it's not worth worrying about them) with the same structure
> with 'message where you see 'article.
Ok but I don't think I can achieve what I want with this.
What I want is to _reuse_ the article buffer when composing emails
whatever the current window layout.
For example, let say I have this current setting:
+---------+---------+
| Summary | |
+---------+ |
| | ERC |
| Article | |
| | |
+---------+---------+
When composing a new email, I want it to become:
+---------+---------+
| Summary | |
+---------+ |
| | ERC |
| Compose | |
| | |
+---------+---------+
And with my setting, I get this
+-------------------+
| Summary |
+-------------------+
| |
| Compose |
| |
+-------------------+
My current setting is:
(gnus-add-configuration
'(article
(vertical 1.0
(summary 0.25 point)
(article 1.0))))
(gnus-add-configuration
'(message
(vertical 1.0
(summary 0.25)
(message 1.0 point))))
(setq gnus-use-full-window nil)
In general, I find Gnus always using the full window for server,
compose... buffers which I find annoying.
Thanks
--
Francis
next prev parent reply other threads:[~2011-02-14 8:26 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 [this message]
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
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=m2d3mvkoml.fsf@gmail.com \
--to=francis.moro@gmail.com \
--cc=david.goldberg6@verizon.net \
--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).