unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Nordin <tomasn@posteo.net>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>, 40888@debbugs.gnu.org
Subject: bug#40888: M-x man: don't redraw good pages when not finding bad pages
Date: Mon, 27 Apr 2020 10:33:12 +0200	[thread overview]
Message-ID: <877dy1ba5z.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87tv15etv2.8.fsf@jidanni.org>

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:

> $ emacs -q
> M-x man cat
> M-x man dog
>
> Why does it have to redraw the entire cat man page, before just saying
> it can't find dog? Why can't it just say it can't find dog?
> Just leave the good page there undisturbed.

I think it is fixed to work like that, it does here with 28.0.50.

Maybe this news item is relevant

*** New function 'display-buffer-reuse-mode-window' is an action function
suitable for use in 'display-buffer-alist'.  For example, to avoid
creating a new window when opening man pages when there's already one,
use

(add-to-list 'display-buffer-alist
     '("\\`\\*Man .*\\*\\'" .
       (display-buffer-reuse-mode-window
        (inhibit-same-window . nil)
        (mode . Man-mode))))

under the super heading * Lisp Changes in Emacs 26.1.

> emacs-version "26.3".

Confusing then. But maybe that function was used later for the man
rendering.





  reply	other threads:[~2020-04-27  8:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 22:59 bug#40888: M-x man: don't redraw good pages when not finding bad pages 積丹尼 Dan Jacobson
2020-04-27  8:33 ` Tomas Nordin [this message]
2020-04-27 14:54   ` 積丹尼 Dan Jacobson
2020-04-27 15:07     ` Stefan Kangas
2020-04-27 20:25       ` Tomas Nordin
2020-08-05 11:28       ` Lars Ingebrigtsen
2020-08-06  5:32         ` 積丹尼 Dan Jacobson
2020-08-06  7:17           ` Lars Ingebrigtsen
2020-08-06 13:40           ` Eli Zaretskii
2020-08-06 17:39             ` 積丹尼 Dan Jacobson
2020-08-06 17:41               ` Lars Ingebrigtsen
2022-02-20 14:17                 ` Lars Ingebrigtsen

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=877dy1ba5z.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me \
    --to=tomasn@posteo.net \
    --cc=40888@debbugs.gnu.org \
    --cc=jidanni@jidanni.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).