From: martin rudalics <rudalics@gmx.at>
To: Nicolas Richard <youngfrog@members.fsf.org>
Cc: "21649@debbugs.gnu.org" <21649@debbugs.gnu.org>
Subject: bug#21649: 25.0.50; [PATCH] Allow M-x man to reuse an existing window
Date: Thu, 22 Oct 2015 17:34:24 +0200 [thread overview]
Message-ID: <56290200.1000700@gmx.at> (raw)
In-Reply-To: <86wpufc8n8.fsf@members.fsf.org>
> Thanks for the hint. That's a very long thread however. I read the first
> few messages but gave up for now for the following reason : I'd like to
> address my bug report first, and it isn't about how difficult
> display-buffer-alist is, even though I did mention that.
That thread explains why ‘display-buffer’ works as it does now. It's
not useful to explain how ‘display-buffer’ works now. So you did good
to give up soon ;-)
> My concern is about making a *Man ...* window reusable. It can be done:
> - by adding a new choice to Man-notify-method (which is what my patch does)
> - by asking the user to customize display-buffer-alist, but in this case
> I think someone has to write a new function (similar to
> display-buffer-reuse-window except that it's not the same buffer, but
> another *Man ...* buffer -- e.g.
> display-buffer-reuse-window-with-matching-major-mode).
> - maybe some other way
>
> If the question is of interest, which answer is the best ? If it's the
> second, I could write such a function. Then we also somehow need to
> advertise display-buffer-alist in the docstring of Man-notify-method.
Sorry, I must have missed your patch. Probably I got confused by the
current state of emacs-devel. Also I hardly ever use ‘man’ so I'm not
very competent to comment such an addition anyway.
How about writing an action function, say ‘man-display-buffer-my-way’, and
adding a clause like
(`my-way
(and (frame-live-p saved-frame)
(select-frame saved-frame))
(display-buffer man-buffer
'((man-display-buffer-my-way ...)
. nil)))
to ‘Man-notify-when-ready’? This would hardly harm, satisfy anyone
asking for customization and likely introduce the first instance of an
action function outside of window.el.
And please don't drop 21649@debbugs.gnu.org from the list of recipients!
martin
next prev parent reply other threads:[~2015-10-22 15:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 15:54 bug#21649: 25.0.50; [PATCH] Allow M-x man to reuse an existing window Nicolas Richard
2015-10-09 14:37 ` Kaushal Modi
[not found] ` <86r3l09t3u.fsf@members.fsf.org>
2015-10-12 15:06 ` Kaushal Modi
2015-10-13 22:10 ` Nicolas Richard
2015-10-13 22:19 ` Kaushal Modi
2015-10-14 8:49 ` martin rudalics
[not found] ` <86wpufc8n8.fsf@members.fsf.org>
2015-10-22 15:34 ` martin rudalics [this message]
2015-10-22 19:21 ` Nicolas Richard
2015-10-23 8:01 ` martin rudalics
2016-03-01 15:49 ` Nicolas Richard
2016-03-01 17:04 ` martin rudalics
2016-03-10 9:55 ` Nicolas Richard
2016-03-10 10:32 ` martin rudalics
2016-03-10 13:49 ` Nicolas Richard
2015-10-27 11:30 ` Nicolas Richard
2015-10-28 9:55 ` 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=56290200.1000700@gmx.at \
--to=rudalics@gmx.at \
--cc=21649@debbugs.gnu.org \
--cc=youngfrog@members.fsf.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.