From: Juri Linkov <juri@jurta.org>
To: jay.p.belanger@gmail.com
Cc: 3419@debbugs.gnu.org
Subject: bug#3419: 23.0.94; calc, calendar and temp-buffer-resize-mode
Date: Tue, 01 Nov 2011 11:27:20 +0200 [thread overview]
Message-ID: <87y5w02s2n.fsf@mail.jurta.org> (raw)
In-Reply-To: <87y5w12dny.fsf@vh213601.truman.edu> (Jay Belanger's message of "Mon, 31 Oct 2011 13:56:17 -0500")
>> When I type `M-x calc RET h h', it displays the *Help* window in the
>> Calc window that is too small to read comfortably the Help buffer.
>>
>> That's because I have in .emacs:
>> (add-to-list 'same-window-buffer-names "*Help*")
>>
>> Is it possible to display the Help buffer in another window in this case
>> when `h h' is typed in the Calc window?
>
> I'm not sure what you want, since you are explicitly telling Emacs to
> display Help in the same window. Is that line from your .emacs for some
> other *Help* buffer, and you never want the Calc help to appear in the
> same window? Perhaps if the Calc help were named "*Calc Help*" (or
> better, perhaps, using a variable to determine the name,
> `calc-help-buffer-name' or somesuch). That wouldn't be hard, but
> perhaps should wait until after 24.1.
Some modes bind `same-window-buffer-names' to nil when it makes no sense
to display the *Help* or *Info* buffer in the same window when it is
too small, thus overridding the user's settings.
IIUC, with the new window rules, the right way to do this is to bind
`display-buffer-overriding-action' to `display-buffer-pop-up-window'.
But this doesn't work as expected:
(let ((display-buffer-overriding-action '(display-buffer-pop-up-window)))
(with-output-to-temp-buffer "*Help*"
(princ "GNU Emacs Calculator.\n")))
It still displays the *Help* buffer in the same window when
(add-to-list 'same-window-buffer-names "*Help*") is presented in .emacs.
next prev parent reply other threads:[~2011-11-01 9:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 19:03 bug#3419: 23.0.94; calc, calendar and temp-buffer-resize-mode Leo
2009-05-29 23:46 ` Jay Belanger
2009-05-30 1:43 ` Leo
2009-05-30 2:15 ` Jay Belanger
2009-05-30 9:51 ` martin rudalics
2009-05-30 10:58 ` Leo
2009-05-30 12:19 ` martin rudalics
2009-05-30 18:21 ` Glenn Morris
2009-05-30 22:37 ` Leo
2011-10-24 11:07 ` Leo
2011-10-24 16:15 ` martin rudalics
2011-10-25 2:17 ` Leo
2011-10-25 2:47 ` Jay Belanger
2011-10-25 15:20 ` Leo
2011-10-31 10:34 ` Juri Linkov
2011-10-31 18:56 ` Jay Belanger
2011-11-01 9:27 ` Juri Linkov [this message]
2011-11-01 14:38 ` martin rudalics
2011-11-01 20:00 ` Stefan Monnier
2011-11-01 21:54 ` Juri Linkov
2011-11-02 1:21 ` Stefan Monnier
2011-11-02 9:35 ` Juri Linkov
2011-11-02 10:04 ` martin rudalics
2011-11-03 9:05 ` Juri Linkov
2011-11-03 10:07 ` martin rudalics
2011-11-03 10:17 ` Juri Linkov
2011-11-03 12:26 ` Stefan Monnier
2011-11-03 19:44 ` Juri Linkov
2011-11-03 21:07 ` Stefan Monnier
2011-11-04 9:38 ` Juri Linkov
2011-11-04 9:39 ` martin rudalics
2011-11-04 10:12 ` Juri Linkov
2011-11-04 13:55 ` martin rudalics
2011-11-03 13:59 ` martin rudalics
2011-11-03 19:45 ` Juri Linkov
2011-11-04 9:39 ` martin rudalics
2011-11-04 13:12 ` Stefan Monnier
2011-11-06 21:09 ` Jay Belanger
2011-11-02 12:37 ` Stefan Monnier
2009-06-02 15:57 ` Leo
2009-06-02 19:20 ` Jay Belanger
2009-06-02 21:28 ` Leo
2012-10-04 13:18 ` 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=87y5w02s2n.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=3419@debbugs.gnu.org \
--cc=jay.p.belanger@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.