From: martin rudalics <rudalics@gmx.at>
To: Leo Liu <sdl.web@gmail.com>
Cc: 16038@debbugs.gnu.org
Subject: bug#16038: 24.3; latest change to with-help-window makes temp-buffer-browse useless
Date: Sat, 11 Jan 2014 15:01:03 +0100 [thread overview]
Message-ID: <52D14E9F.5030001@gmx.at> (raw)
In-Reply-To: <m1haaqq9z7.fsf@gmail.com>
> with-help-window has been changed to use with-temp-buffer-window.
> temp-buffer-window-show has special treatment for
> temp-buffer-resize-mode but not temp-buffer-browse-mode (in GNU ELPA).
>
> There seems to be a significant overlap between with-temp-buffer-window
> and with-output-to-temp-buffer. I wonder if there is a better design of
> with-temp-buffer-window that re-use/blend with
> with-output-to-temp-buffer. I also find the similar hooks (setup/show
> hooks) between these macros confusing.
`with-help-window' does some things differently which I could not put
into `with-output-to-temp-buffer' due to compatibility issues. Can't
you put `temp-buffer-browse-mode' on `temp-buffer-window-show-hook'?
> Maybe what need isn't a macro close to with-output-to-temp-buffer but
> one (e.g with-temp-window) close to with-temp-buffer.
The idea of `with-temp-buffer' is to create a temporary buffer where you
evaluate things and _kill_ that buffer immediately afterwards. The idea
of `with-temp-buffer-window' is to show the buffer and keep it around at
least until you quit the window.
martin
next prev parent reply other threads:[~2014-01-11 14:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 14:34 bug#16038: 24.3; latest change to with-help-window makes temp-buffer-browse useless Leo Liu
2014-01-11 14:01 ` martin rudalics [this message]
2014-01-11 14:32 ` Leo Liu
2014-01-11 15:41 ` martin rudalics
2014-01-11 16:31 ` Leo Liu
2014-01-12 9:53 ` martin rudalics
2014-01-14 0:23 ` Leo Liu
2014-01-14 1:47 ` Stefan Monnier
2014-01-14 4:42 ` Leo Liu
2014-01-14 21:38 ` Stefan Monnier
2014-01-14 21:55 ` Drew Adams
2014-01-14 23:46 ` Leo Liu
2014-01-22 2:14 ` Leo Liu
2014-01-22 3:02 ` Stefan Monnier
2014-01-22 3:32 ` Leo Liu
2014-01-22 13:44 ` Stefan Monnier
2014-01-23 10:03 ` Leo Liu
2014-01-23 17:48 ` Drew Adams
2014-01-24 7:30 ` Leo Liu
2014-01-24 15:06 ` Drew Adams
2014-01-24 15:45 ` martin rudalics
2014-01-24 16:29 ` Drew Adams
2014-01-25 9:21 ` martin rudalics
2014-01-25 16:34 ` Drew Adams
2014-01-25 16:48 ` martin rudalics
2014-01-25 17:33 ` Drew Adams
2014-01-25 18:25 ` martin rudalics
2014-01-25 20:19 ` Drew Adams
2014-01-26 11:24 ` martin rudalics
2014-01-26 17:52 ` Drew Adams
2014-01-27 8:21 ` martin rudalics
2014-01-27 15:14 ` Drew Adams
2014-01-22 3:07 ` Glenn Morris
2014-07-08 1:54 ` Glenn Morris
2014-07-08 2:04 ` Glenn Morris
2014-07-08 5:59 ` Glenn Morris
2014-07-08 13:57 ` Drew Adams
2014-07-08 22:24 ` Leo Liu
2014-07-10 7:20 ` Glenn Morris
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=52D14E9F.5030001@gmx.at \
--to=rudalics@gmx.at \
--cc=16038@debbugs.gnu.org \
--cc=sdl.web@gmail.com \
/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).