unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Question about display-buffer-overriding-action
Date: Fri, 18 Mar 2022 01:56:25 -0300	[thread overview]
Message-ID: <CADs++6hMf4MWAfxK4qRx=kCbX3fPYrfC1b-hjPThqp2-OYCLew@mail.gmail.com> (raw)
In-Reply-To: <87r170mdkh.fsf@web.de>

Hi Michael,

> Note that `man' is a special (and rare) case: Emacs `man' works
> asynchronously; when the buffer has been rendered and the result gets
> displayed, your `let' is long gone.
>
> See `Man-notify-when-ready' and `Man-notify-method' for how the buffer
> gets displayed.
>
> You probably need an appropriate man buffer specific entry in the
> top-level binding of `display-buffer-alist' to get what you want.

I spent a lot of time trying to decypher man's code a few
years ago and I think that the right way to do that is with
a "(let ((Man-notify-method ...)) ...)", as in:

  (let ((Man-notify-method 'pushy))
    (man "cat"))

See the comments and links here:

  (find-eev "eev-blinks.el" "find-man")
  http://angg.twu.net/eev-current/eev-blinks.el.html#find-man

> Maybe it works for women?

Do you use woman? Most people only mention woman for jokes...
Man and woman handle windows differently. I tried this - and
its interactive version, of course - and woman opened the
manpage in the current window:

  (woman-find-file "/usr/share/man/man1/cat.1.gz")

Cheers,
  Eduardo
  http://angg.twu.net/#eev



  reply	other threads:[~2022-03-18  4:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16  1:34 Question about display-buffer-overriding-action Eduardo Ochs
2022-03-16  1:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-16  2:08   ` Eduardo Ochs
2022-03-16  2:12     ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-17 20:19       ` Eduardo Ochs
2022-03-17 21:04       ` Eduardo Ochs
2022-03-17 22:14         ` Michael Heerdegen
2022-03-18  4:56           ` Eduardo Ochs [this message]
2022-03-19  1:30             ` Michael Heerdegen
2022-03-25  9:38       ` dal-blazej
2022-03-25 17:59         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-25 22:56           ` dal-blazej
2022-03-26  1:10         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-16  2:16     ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-16 13:51     ` Eric S Fraga

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='CADs++6hMf4MWAfxK4qRx=kCbX3fPYrfC1b-hjPThqp2-OYCLew@mail.gmail.com' \
    --to=eduardoochs@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.
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).