From: martin rudalics <rudalics@gmx.at>
To: Lukasz Pawelczyk <havner@gmail.com>
Cc: "16909@debbugs.gnu.org" <16909@debbugs.gnu.org>
Subject: bug#16909: 24.3; scrolling *Completions* window with tab sometimes chooses a wrong window
Date: Sat, 01 Mar 2014 20:18:17 +0100 [thread overview]
Message-ID: <53123279.6070203@gmx.at> (raw)
In-Reply-To: <CACL4Mm_3-AkZq5NBGeNdsMOi+MakM_8Vn5CMLMwTOjkceAGivw@mail.gmail.com>
>> (1) Kill the *Completions* buffer when we're done so it won't be
>> inadvertently displayed by `other-window-for-scrolling'.
>
>
> How is this supposed to work?
> The problem is _during_ the Completions buffer is shown, when we're hitting
> Tab, not when we're done. Besides its window is usually closed
> automatically.
We have to detect the moment when the window is closed automatically
anyway. At that time we can either kill the buffer or reset
`other-window-scroll-buffer'.
> Killing the buffer won't make the scroll-other-window work
> the usuall way.
How comes? Ahh... I see. If `other-window-scroll-buffer' is non-nil
and the buffer was killed in the meantime `display-buffer' throws an
arg out of range error. That's silly ... should be fixed now.
>> (2) Bind `other-window-scroll-buffer' temporarily only as long as the
>> *Completions* buffer is shown.
>
>
> This would work I imagine. But don't do this in general when the
> Completions buffer is shown, but only when we use autocomplete
> functionality with Tab _and_ the buffer is shown.
Could you try doing that? I have no idea where to start.
martin
next prev parent reply other threads:[~2014-03-01 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 16:41 bug#16909: 24.3; scrolling *Completions* window with tab sometimes chooses a wrong window Lukasz Pawelczyk
2014-02-28 18:24 ` martin rudalics
2014-02-28 18:28 ` Lukasz Pawelczyk
2014-03-01 11:54 ` martin rudalics
2014-03-01 12:11 ` Lukasz Pawelczyk
2014-03-01 19:18 ` martin rudalics [this message]
2014-03-04 23:22 ` Lukasz Pawelczyk
2014-03-05 7:26 ` martin rudalics
2014-03-05 9:48 ` Lukasz Pawelczyk
2014-03-05 14:03 ` martin rudalics
2014-03-06 10:43 ` Lukasz Pawelczyk
2014-03-06 17:27 ` martin rudalics
2022-02-13 9:16 ` Lars Ingebrigtsen
2022-03-13 20:35 ` Lars Ingebrigtsen
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=53123279.6070203@gmx.at \
--to=rudalics@gmx.at \
--cc=16909@debbugs.gnu.org \
--cc=havner@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.