From: Juri Linkov <juri@jurta.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 2282@emacsbugs.donarmstrong.com, "Alfred M. Szmidt" <ams@gnu.org>
Subject: bug#2282: Bug#2282: rmail-summary splits frame into three parts
Date: Tue, 10 Nov 2009 09:48:46 +0200 [thread overview]
Message-ID: <87pr7q95wh.fsf@mail.jurta.org> (raw)
In-Reply-To: <4gmy2vxh8z.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 09 Nov 2009 21:09:48 -0500")
> The behaviour described in the original report happens if you make the
> Emacs frame wider than `split-width-threshold'. Setting that variable
> to nil will prevent it.
>
> I don't know what to do about this. There are lots of pop-to-buffers
> in rmailsum.el, and any of them could cause such behaviour.
>
> See the confusion in bug#1806.
With the current CVS after `M-x rmail-summary' I see
+---------------+---------------+
| | |
| RMAIL-summary | RMAIL |
| | |
+---------------+---------------+
| |
| RMAIL-summary |
| |
+-------------------------------+
I think for RMAIL both following layouts make equal sense
on a wide frame:
+---------------+---------------+
| | |
| RMAIL-summary | RMAIL |
| | |
| | |
| | |
| | |
| | |
+---------------+---------------+
and
+-------------------------------+
| |
| RMAIL-summary |
| |
+-------------------------------+
| |
| RMAIL |
| |
+-------------------------------+
The question is what options are necessary to be able to configure RMAIL
window layouts? Maybe like `gnus-buffer-configuration' in Gnus?
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-11-10 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 2:09 bug#2282: Bug#2282: rmail-summary splits frame into three parts Glenn Morris
2009-11-10 7:48 ` Juri Linkov [this message]
2009-11-10 17:59 ` Stefan Monnier
2009-11-11 17:22 ` Alfred M. Szmidt
2009-11-12 7:24 ` Glenn Morris
2009-11-12 8:19 ` martin rudalics
2009-11-12 15:42 ` Stefan Monnier
2009-11-12 15:41 ` Stefan Monnier
2009-11-12 17:40 ` martin rudalics
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pr7q95wh.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=2282@emacsbugs.donarmstrong.com \
--cc=ams@gnu.org \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).