From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20020@debbugs.gnu.org
Subject: bug#20020: 25.0.50; `info-display-manual' should reuse existing window where buffer is displayed
Date: Sun, 13 Oct 2019 20:22:27 +0200 [thread overview]
Message-ID: <87r23ga4kc.fsf@gnus.org> (raw)
In-Reply-To: <83y2xrprlw.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Oct 2019 12:18:51 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> > If this is the change, then I think it should be an opt-in change. We
>> > don't behave like that with any other buffers, why should Info buffers
>> > be an exception by default?
>>
>> That's true. Off the top of my head, I can't recall any other commands
>> that work this way, so it's odd for `info-display-manual' to do so.
>>
>> Should I just revert the change?
>
> It'd be fine with me, but probably not with Drew. having an opt-in
> defcustom is a good compromise, I think.
I don't know much about how dedicated windows work, but couldn't Drew
set that up to have Emacs pop up that window instead of having special
code for this in `info-display-manual'? I had forgotten about that when
I wrote the patch.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-13 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 19:15 bug#20020: 25.0.50; `info-display-manual' should reuse existing window where buffer is displayed Drew Adams
2019-10-09 2:12 ` Lars Ingebrigtsen
2019-10-09 16:54 ` Eli Zaretskii
2019-10-09 17:51 ` Lars Ingebrigtsen
2019-10-09 18:08 ` Eli Zaretskii
2019-10-11 8:07 ` Lars Ingebrigtsen
2019-10-11 9:18 ` Eli Zaretskii
2019-10-13 18:22 ` Lars Ingebrigtsen [this message]
2019-10-09 20:38 ` Juri Linkov
2019-10-10 9:16 ` martin rudalics
2019-10-11 8:09 ` Lars Ingebrigtsen
2019-10-11 8:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r23ga4kc.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20020@debbugs.gnu.org \
--cc=eliz@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 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.