From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17671@debbugs.gnu.org
Subject: bug#17671: 24.3.91; RET on a link in *Help* buffer resizes *Help*
Date: Tue, 03 Jun 2014 11:41:53 +0200 [thread overview]
Message-ID: <538D9861.6070608@gmx.at> (raw)
In-Reply-To: <837g4ya0yf.fsf@gnu.org>
>> `temp-buffer-resize-mode' would do that automatically.
>
> Then perhaps we should turn on that mode by default.
ISTR that some people dislike `temp-buffer-resize-mode'.
> So this means that as long as the links in *Help* point to the same
> file which is already displayed in the window above *Help*, the size
> will stick,
... because in that case the window already shows that buffer ...
> but as soon as another file is displayed in the window
> above *Help*, we get a resize, is that right?
Only if that window was used by `display-buffer' before. That window
could have been made very small, for example, when used for displaying
*Help* and in such case people would probably protest that we use a
ridiculously small LRU-window for displaying a buffer. There was at
least one bug report bemoaning that IIRC.
> That's a really
> annoying inconsistency, IMO.
> Is it possible to do something special for the specific scenario I
> described, i.e. when a *Help* link causes a buffer to be displayed?
Usually, doing so causes a problem in another area soon. Maybe we
should not _decrease_ the size of a window when displaying another
buffer in it - this would take care of your use case.
> Or maybe the window showing *Help* should be small by default; taking
> half of its frame is really gross, IMO. It is especially annoying in
> "emacs -Q", which starts with a small frame.
This is really what `temp-buffer-resize-mode' is for.
martin
next prev parent reply other threads:[~2014-06-03 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 18:45 bug#17671: 24.3.91; RET on a link in *Help* buffer resizes *Help* Eli Zaretskii
2014-06-03 7:21 ` martin rudalics
2014-06-03 7:47 ` Eli Zaretskii
2014-06-03 9:41 ` martin rudalics [this message]
2014-06-03 10:54 ` Eli Zaretskii
2014-06-03 12:40 ` martin rudalics
2014-06-03 16:32 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=538D9861.6070608@gmx.at \
--to=rudalics@gmx.at \
--cc=17671@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.