Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: david.goldberg6@verizon.net (Dave Goldberg)
Cc: ding@gnus.org
Subject: Re: buffer layout when composing
Date: Mon, 14 Feb 2011 10:20:15 +0100	[thread overview]
Message-ID: <87sjvrvupc.fsf@member.fsf.org> (raw)
In-Reply-To: <m2d3mvkoml.fsf@gmail.com> (Francis Moreau's message of "Mon, 14 Feb 2011 09:26:58 +0100")

Francis Moreau <francis.moro@gmail.com> writes:

Hi Francis,

> 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       |
>           |                   |
>           +-------------------+
>
> In general, I find Gnus always using the full window for server,
> compose... buffers which I find annoying.

Ah, your central point is that Gnus shouldn't use the full frame and
destroy your window config, right?

,----[ C-h v gnus-use-full-window RET ]
| gnus-use-full-window is a variable defined in `gnus-win.el'.
| Its value is t
| 
| Documentation:
| *If non-nil, use the entire Emacs screen.
| 
| You can customize this variable.
`----

You might want to set that to nil.  That should make the ERC window
survive composing new mail (at least in theory).

Bye,
Tassilo
-- 
Sent from my Emacs



  reply	other threads:[~2011-02-14  9:20 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 [this message]
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=87sjvrvupc.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --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).