From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 14829@debbugs.gnu.org, Barry Warsaw <barry@python.org>
Subject: bug#14829: (no subject)
Date: Mon, 22 Jul 2013 19:37:07 +0200 [thread overview]
Message-ID: <51ED6DC3.6040501@gmx.at> (raw)
In-Reply-To: <jwvsiz6wmbj.fsf-monnier+emacs@gnu.org>
> 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.
With `inhibit-same-window' t one might want to show the same buffer in the
new window.
> 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?
It happens because \\[split-window-below] gets substituted by C-x 2.
Why not declare `split-window-keep-point' obsolete and always keep
point?
martin
next prev parent reply other threads:[~2013-07-22 17:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 21:08 bug#14829: 24.3; split-window-keep-point breaks shell tab completion Barry Warsaw
2013-07-11 19:37 ` bug#14829: (no subject) Barry Warsaw
2013-07-22 17:18 ` Stefan Monnier
2013-07-22 17:37 ` martin rudalics [this message]
2013-07-22 17:42 ` Barry Warsaw
2013-07-23 7:10 ` martin rudalics
2013-07-22 18:56 ` Stefan Monnier
2013-07-23 7:10 ` martin rudalics
2013-07-23 13:09 ` Stefan Monnier
2013-07-23 13:38 ` Barry Warsaw
2013-07-25 10:05 ` martin rudalics
2013-07-27 2:52 ` Barry Warsaw
2013-07-27 8:18 ` martin rudalics
2013-07-29 16:56 ` martin rudalics
2013-07-25 10:04 ` martin rudalics
2013-07-22 17:41 ` Barry Warsaw
2013-07-12 8:20 ` bug#14829: 24.3; split-window-keep-point breaks shell tab completion martin rudalics
2013-07-12 9:26 ` Eli Zaretskii
2013-07-12 10:12 ` martin rudalics
2013-07-12 14:18 ` Barry Warsaw
2013-07-12 14:12 ` Barry Warsaw
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51ED6DC3.6040501@gmx.at \
--to=rudalics@gmx.at \
--cc=14829@debbugs.gnu.org \
--cc=barry@python.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).