Subject: Re: bug#14829: (no subject)

From: Stefan Monnier <[email-masked]>
Date: Mon, 22 Jul 2013 13:18:20 -0400

> 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