From: Drew Adams <drew.adams@oracle.com>
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: Fri, 24 Jan 2014 07:06:11 -0800 (PST) [thread overview]
Message-ID: <90f208e1-9ab5-4b8c-9e4c-2dddf8c1868b@default> (raw)
In-Reply-To: <m1d2jhet1b.fsf@gmail.com>
> > Huh? What's this about? Why on Earth would we deprecate
> > `with-output-to-temp-buffer'? How about some reasons for such a
> > proposal?
> >
> > My code and other 3rd-party libraries use `with-output-to-temp-buffer'
> > all over the place.
> >
> > But I have no code that uses `with-temp-buffer-window'. And googling
> > for it shows one hit to the Elisp manual and the rest are hits to
> > Emacs bugs! I do not see zillions of users of
> > `with-temp-buffer-window', which was not introduced until Emacs 24.3.
>
> We are trying to consolidate the features of the two macros into one so
> no feature is lost.
Yes, clearly. I got that. But why would you even consider
`with-temp-buffer-window', rather than `with-output-to-temp-buffer', as
the end target of your consolidation?
Incorporate whatever you feel you need to into
`with-output-to-temp-buffer', as long as "no feature is lost" from it.
But please do not consider deprecating `with-output-to-temp-buffer'.
It was that possibility that was mentioned and that I replied to.
If you feel that you need to deprecate something here, deprecate the
new addition, `with-temp-buffer-window', which has hardly been used
anywhere.
next prev parent reply other threads:[~2014-01-24 15:06 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90f208e1-9ab5-4b8c-9e4c-2dddf8c1868b@default \
--to=drew.adams@oracle.com \
--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 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.