[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#12943: 24.2.50; switch to help buffer with > 3-window-split
From: |
martin rudalics |
Subject: |
bug#12943: 24.2.50; switch to help buffer with > 3-window-split |
Date: |
Thu, 25 Dec 2014 11:54:28 +0100 |
> >> 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 in Thread] |
Current Thread |
[Next in Thread] |
- bug#12943: 24.2.50; switch to help buffer with > 3-window-split,
martin rudalics <=