all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Barry Warsaw <barry@python.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 14829@debbugs.gnu.org
Subject: bug#14829: (no subject)
Date: Mon, 22 Jul 2013 13:42:22 -0400	[thread overview]
Message-ID: <20130722134222.72c122d3@limelight.wooz.org> (raw)
In-Reply-To: <51ED6DC3.6040501@gmx.at>

[-- Attachment #1: Type: text/plain, Size: 312 bytes --]

On Jul 22, 2013, at 07:37 PM, martin rudalics wrote:

>It happens because \\[split-window-below] gets substituted by C-x 2.
>
>Why not declare `split-window-keep-point' obsolete and always keep
>point?

Please no!  C-x 2 with split-window-keep-point nil is a *really* important
feature, to me at least.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-07-22 17:42 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130722134222.72c122d3@limelight.wooz.org \
    --to=barry@python.org \
    --cc=14829@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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.