From: Noam Postavsky <npostavs@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 35873@debbugs.gnu.org
Subject: bug#35873: Add atomic window support to Gnus
Date: Fri, 21 Jun 2019 05:10:33 -0400 [thread overview]
Message-ID: <874l4jwbg6.fsf@gmail.com> (raw)
In-Reply-To: <87h89kuch2.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 23 May 2019 13:45:13 -0700")
severity 35873 wishlist
tags 35873 + patch
quit
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 pretty sure I've done the elisp manual cross reference incorrectly.
> +windows (@pxref{Atomic Windows, , Atomic Windows, elisp}).
I believe the correct form would be:
(@pxref{Atomic Windows,,, elisp, The Emacs Lisp Reference Manual})
That is, no need to repeat the topic title, as it's the same as the node
name. But the printed manual name is needed as the last argument. See
(info "(texinfo) Four and Five Arguments"), and grep for xref.*elisp in
doc/ for similar examples.
I guess the code part of the patch is alright, but I'm not too familiar
with how atomic windows work.
next prev parent reply other threads:[~2019-06-21 9:10 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 [this message]
2019-06-21 15:11 ` Eric Abrahamsen
2019-06-22 11:55 ` Lars Ingebrigtsen
2019-06-22 16:41 ` Eric Abrahamsen
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
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=874l4jwbg6.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=35873@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
/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).