From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 35873@debbugs.gnu.org
Subject: bug#35873: Add atomic window support to Gnus
Date: Sat, 22 Jun 2019 09:41:44 -0700 [thread overview]
Message-ID: <87imsxy3lj.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m3y31tg7hi.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 22 Jun 2019 13:55:05 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> The attached patch adds atomic window support with a new customization
>> option, `gnus-use-atomic-windows', defaulting to nil. If t, a
>> multi-window Gnus layout will be treated as a single window when other
>> code pops up buffers. Ie, your completions buffer won't end up squished
>> between the summary and article buffers.
>
> I'm not familiar with the atomic window stuff at all -- I don't use
> pop-up windows and all the newfangled stuff kids today use -- but the
> feature sounds sensible to me, so go ahead and apply (unless you wanted
> to do this in another way, which you alluded to in a subsequent
> message)...
Well, but even *Completion* buffers are pop-up buffers... Maybe helm
users, in particular, would be bothered by this.
I do want to pursue the other avenue a bit, but if that doesn't work out
or looks like too much effort, I'll push this.
Thanks,
Eric
next prev parent reply other threads:[~2019-06-22 16:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 20:45 bug#35873: Add atomic window support to Gnus Eric Abrahamsen
2019-06-21 9:10 ` Noam Postavsky
2019-06-21 15:11 ` Eric Abrahamsen
2019-06-22 11:55 ` Lars Ingebrigtsen
2019-06-22 16:41 ` Eric Abrahamsen [this message]
2019-09-16 21:05 ` Lars Ingebrigtsen
2019-09-16 22:42 ` Eric Abrahamsen
2019-09-16 22:43 ` Lars Ingebrigtsen
2019-09-19 17:21 ` Eric Abrahamsen
2019-09-20 8:13 ` martin rudalics
2019-09-20 18:12 ` Eric Abrahamsen
2019-09-20 19:28 ` Eric Abrahamsen
2019-09-20 20:19 ` Lars Ingebrigtsen
2019-09-20 20:41 ` Eric Abrahamsen
2019-09-28 18:00 ` Lars Ingebrigtsen
2019-09-20 20:49 ` Eric Abrahamsen
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=87imsxy3lj.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=35873@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.