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: Thu, 06 Mar 2014 18:27:26 +0100 [thread overview]
Message-ID: <5318AFFE.20509@gmx.at> (raw)
In-Reply-To: <CACL4Mm_CrU=cs0otw29YCW=vcQuP9ZaV7S3hJ=cax8aHL9B0cA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]
> Yes, I just have (for the first time, my bug report was about 24.3).
> And 2 things:
>
> 1. I still get invalid buffer, Meaning:
> - (setq other-window-scroll-buffer "*Completions*")
> - C-M-v always scrolls Completions buffer as it should
> - kill the completions buffer
> - C-M-v -> "Invalid buffer'
I checked in another fix. Try now with emacs -Q
(progn
(with-current-buffer (get-buffer-create "*foo*")
(dotimes (i 100)
(insert "foo......\n\n....foo....\n\n......foo\n\n....foo...."))
(goto-char (point-min)))
(display-buffer "*foo*")
(with-current-buffer (get-buffer-create "*bar*")
(dotimes (i 100)
(insert "bar......\n\n....bar....\n\n......bar\n\n....bar...."))
(goto-char (point-min)))
(set-window-buffer (split-window) "*bar*")
(setq other-window-scroll-buffer (get-buffer "*foo*")))
and do C-M-v. It should scroll *foo*'s window. Next do
(kill-buffer "*foo*")
It should scroll *bar*'s window now.
> 2. But most interestingly, on the latest trunk I cannot reproduce my
> original issue anymore.
> Contrary to 24.3 TAB for auto-complete seems to work just fine. I'll
> investigate this more
> to make sure it really is as it should and will report my findings.
> If it's just a coincidence (my local work environment is playing tricks on
> me) I'll
> try to implement some fix this weekend.
>
> Were you ever able to reproduce this issue on trunk? If so, when?
Always. On the attached screenshot you see the selected window at the
bottom right and the *Completions* window at the bottom left. I can't
scroll the *Completions* window via C-M-v from the selected window. So
I'm afraid you still have to look into this.
martin
[-- Attachment #2: completions.png --]
[-- Type: image/png, Size: 17725 bytes --]
next prev parent reply other threads:[~2014-03-06 17:27 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
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 [this message]
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=5318AFFE.20509@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.