From: martin rudalics <rudalics@gmx.at>
To: Vitalie Spinu <spinuvit@gmail.com>
Cc: 12943-done@debbugs.gnu.org
Subject: bug#12943: 24.2.50; switch to help buffer with > 3-window-split
Date: Thu, 25 Dec 2014 11:54:28 +0100 [thread overview]
Message-ID: <549BECE4.20004@gmx.at> (raw)
In-Reply-To: <877gpg1gsy.fsf@gmail.com>
> >> If I have only one window in a frame. C-h v ... RET opens a help buffer, but
> >> does not switch to it. Same with 2 windows in a frame.
> >>
> >> If I have a 3-window-split, C-h v ... RET pops to the help buffer. This
> >> is a bit annoying and might be indicative of some more severe underlying
> >> problem.
> >>
> >> I hope this is not an intended behavior.
>
> > See bug#11039.
>
> Hm, the default 'other of help-window-select is inconsistent and aims a
> very specific user pattern.
>
> From http://debbugs.gnu.org/db/11/11039.html:
>
> martin rudalics <rudalics <at> gmx.at> writes:
>
> > When the help window is one out of three windows on a frame and you do
> > _not_ select it, it's quite difficult to restore the state of the frame
> > before showing help. You would have to (1) manually switch to the help
> > window, (2) type "q" in it, and maybe (3) switch back to the previously
> > selected window. If, however, you _do_ select the help window, you can
> > simply type "q" in it and get back the old state of affairs.
>
>
> I might want to keep the help window open for long and keep working on
> my code while referencing the help. This is my 99% usage pattern.
>
> Now, when I open the help buffer I have to switch back to my working
> window all the way back through 3 other windows. Awful.
The default value of `help-window-select' is now nil on master/trunk.
Closing this bug.
Thanks, martin
prev parent reply other threads:[~2014-12-25 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 12:42 bug#12943: 24.2.50; switch to help buffer with > 3-window-split Vitalie Spinu
2012-11-20 14:19 ` martin rudalics
2012-11-20 14:37 ` Vitalie Spinu
2012-11-20 17:08 ` martin rudalics
2012-11-20 20:52 ` Dmitry Gutov
2014-12-25 10:54 ` martin rudalics [this message]
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=549BECE4.20004@gmx.at \
--to=rudalics@gmx.at \
--cc=12943-done@debbugs.gnu.org \
--cc=spinuvit@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).