unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 09 Oct 2019 19:51:29 +0200	[thread overview]
Message-ID: <87wodd7qou.fsf@gnus.org> (raw)
In-Reply-To: <83eezlvoyn.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Oct 2019 19:54:56 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> I don't really understand what you did and what was the original
> problem, because info-display-manual already behaves for me like the
> OP wanted.  It has behaved like that from day one, because I wrote it
> to do so.  It only displays in *info* if there's not already an
> *info*<N> buffer showing the requested manual (and in my Emacs
> sessions, I never have *info* for long, I either kill it or rename to
> *info*<N>.

Yes, it reuses the buffer.  But the bug report is about window
behaviour.

> Maybe the problem is that the OP did this in dedicated windows?
> That's the only factor I could think of that is different from what I
> do.

Try this in Emacs 26:

M-: (info-display-manual "Coreutils")
C-x 2
C-x b *scratch*
M-: (info-display-manual "Coreutils")

You'll now have two windows displaying the same Info buffer, and that
was what the user didn't want (and I agree that it's not optimal
behaviour).  In the user's case, it was exacerbated by having the window
displayed in a different frame, but that's just a detail.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-09 17:51 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 [this message]
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
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

  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=87wodd7qou.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 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).