From: martin rudalics <rudalics@gmx.at>
To: Barry Warsaw <barry@python.org>
Cc: 14829@debbugs.gnu.org
Subject: bug#14829: 24.3; split-window-keep-point breaks shell tab completion
Date: Fri, 12 Jul 2013 10:20:22 +0200 [thread overview]
Message-ID: <51DFBC46.6020709@gmx.at> (raw)
In-Reply-To: <20130708170808.555814cb@limelight.wooz.org>
> With `(setq split-window-keep-point t)` you will see the window split,
> with the top window scrolled to leave point just after the `a` in the
> middle of the window. The bottom window will have the completions for
> aa.txt and ab.txt
>
> With `(setq split-window-keep-point nil)` you will not get any window
> split, but point will jump someplace higher up in the window (e.g. for
> me it jumps to just after the gg.txt line).
`split-window-below' here does
(setq new-window (split-window nil size))
(unless split-window-keep-point
so I don't understand how setting `split-window-keep-point' can affect
the decisison whether to split the window.
Does anyone know where this behavior comes from?
martin
next prev parent reply other threads:[~2013-07-12 8:20 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
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 ` martin rudalics [this message]
2013-07-12 9:26 ` bug#14829: 24.3; split-window-keep-point breaks shell tab completion 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51DFBC46.6020709@gmx.at \
--to=rudalics@gmx.at \
--cc=14829@debbugs.gnu.org \
--cc=barry@python.org \
/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.