[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#14829: (no subject)
From: |
Stefan Monnier |
Subject: |
bug#14829: (no subject) |
Date: |
Mon, 22 Jul 2013 13:18:20 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
> This fixes it for me.
> ;; Work around a bug in split-window-keep-point and completion.
> (defadvice completion-at-point (around completion-at-point-around)
> "Point safe completion"
> (let ((split-window-keep-point t))
> ad-do-it))
> (ad-activate 'completion-at-point)
Hmm... looking at it further I see that:
- split-window-keep-point defaults to t.
- the problem could affect other cases than completion.
Basically, I'm leaning towards forcing split-window-keep-point to t in
display-buffer, since AFAICT a value of nil only makes sense when you
split a window into two so that they both show the same buffer, whereas
in the case of display-buffer, you always want the current buffer's
point to stay put.
Why do you (and other people) set split-window-keep-point to nil?
What is the expected behavior from it?
The docstring seems to indicate it's only meant to affect C-x 2 rather
than all cases where we create a new window. Martin?
Stefan
- bug#14829: 24.3; split-window-keep-point breaks shell tab completion, Barry Warsaw, 2013/07/08
- bug#14829: (no subject), Barry Warsaw, 2013/07/11
- bug#14829: (no subject),
Stefan Monnier <=
- bug#14829: (no subject), Stefan Monnier, 2013/07/22
- bug#14829: (no subject), martin rudalics, 2013/07/23
- bug#14829: (no subject), Stefan Monnier, 2013/07/23
- bug#14829: (no subject), Barry Warsaw, 2013/07/23
- bug#14829: (no subject), martin rudalics, 2013/07/25
- bug#14829: (no subject), Barry Warsaw, 2013/07/26
- bug#14829: (no subject), martin rudalics, 2013/07/27