From: Brent Busby <brent@jfi.uchicago.edu>
To: ding@gnus.org
Subject: Re: New option gnus-use-atomic-windows
Date: Mon, 23 Sep 2019 12:13:41 -0500 [thread overview]
Message-ID: <8xx5zljhr5m.fsf@jfi.uchicago.edu> (raw)
In-Reply-To: <87pnjruhvf.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 23 Sep 2019 16:55:48 +0100")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> I am struggling to see the advantage of gnus-use-atomic-windows. Can
> somebody (Eric?) illustrate a benefit (other than helm, as mentioned
> earlier, which I don't use)? In a day of testing so far, it has
> gotten in the way... Maybe (definitely) I'm missing the point.
My two cents:
Probably the benefit is just that unlike almost any other Emacs
application, Gnus doesn't let you use windows (in the Emacs sense of the
word, not frames) to use it at the same time while you're also looking
at something else. Any attempts to do that will be foiled just as soon
as you do just about anything in Gnus. When I want to do that, I
usually just open a new frame so Gnus can have one dedicated to it, but
I'm running Emacs in X, so it's nice that I have frames. If I were on a
VTY console, I'd have to just live with Gnus owning my whole display
when I'm using it.
gnus-use-atomic-windows seems to be an attempt to correct that, and let
Gnus share frame space nicely with the buffers of things that don't
belong to Gnus. But we've been living with this for so long that we've
sort of adapted to things the way they have always been (typical Emacs
users, huh?), and thus gnus-use-atomic-windows brings its own problems.
next prev parent reply other threads:[~2019-09-23 17:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 1:52 Eric Abrahamsen
2019-09-22 17:37 ` Eric S Fraga
2019-09-22 17:47 ` Eric Abrahamsen
2019-09-23 1:54 ` Eric Abrahamsen
2019-09-22 19:11 ` Sven Joachim
2019-09-23 15:55 ` Eric S Fraga
2019-09-23 17:13 ` Brent Busby [this message]
2019-09-23 17:26 ` Eric S Fraga
2019-09-23 18:39 ` Eric Abrahamsen
2019-09-23 18:34 ` Eric Abrahamsen
2019-09-23 20:23 ` Eric S Fraga
2019-09-23 16:34 ` dick
2019-09-23 18:30 ` 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=8xx5zljhr5m.fsf@jfi.uchicago.edu \
--to=brent@jfi.uchicago.edu \
--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).