From: martin rudalics <rudalics@gmx.at>
To: Nick Helm <nick@tenpoint.co.nz>, Eli Zaretskii <eliz@gnu.org>
Cc: 30792@debbugs.gnu.org
Subject: bug#30792: 26.0.91; improve docstring of with-help-window
Date: Wed, 14 Mar 2018 09:14:33 +0100 [thread overview]
Message-ID: <5AA8D9E9.2090204@gmx.at> (raw)
In-Reply-To: <m2k1ufldqs.fsf@tenpoint.co.nz>
>> It strikes me that instead of repeating most of what
>> with-temp-buffer-window's doc string says, it might be better to
>> simply refer to there. Like this:
>>
>> Display the output produced by evaluating BODY, like
>> `with-temp-buffer-window' does, then put the window in
>> `help-mode' [...]
Neither `with-temp-buffer-window' nor `help-mode' are of any relevance
here. The distinctive aspect of `with-help-window' is provided by
`help-window-setup' which sets up the help window for quitting it
later. Earlier macros failed miserably in this regard. (I have to
admit that many people are still ignorant of this fact and believe
they could resolve the quitting problem by saving and restoring window
configurations. So the old doc-string probably failed to provide this
rather crucial information as well.)
> +This construct is like `with-current-buffer-window' but unlike that
IIUC it does not make the buffer current when running BODY.
martin
next prev parent reply other threads:[~2018-03-14 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 9:39 bug#30792: 26.0.91; improve docstring of with-help-window Nick Helm
2018-03-13 10:17 ` martin rudalics
2018-03-13 10:31 ` Nick Helm
2018-03-13 16:53 ` Eli Zaretskii
2018-03-14 0:09 ` Nick Helm
2018-03-14 8:14 ` martin rudalics [this message]
2018-03-14 16:18 ` Eli Zaretskii
2018-03-14 20:05 ` martin rudalics
2018-03-14 23:12 ` Nick Helm
2018-03-15 8:20 ` martin rudalics
2018-03-18 11:19 ` Nick Helm
2018-03-20 12:28 ` Eli Zaretskii
2018-03-14 15:56 ` Eli Zaretskii
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=5AA8D9E9.2090204@gmx.at \
--to=rudalics@gmx.at \
--cc=30792@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=nick@tenpoint.co.nz \
/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).