From: Rand <rand.user@ymail.com>
To: emacs-devel@gnu.org
Subject: Re: split-window as a command
Date: Fri, 12 Apr 2013 19:44:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20130412T214228-407@post.gmane.org> (raw)
In-Reply-To: 51681696.7000405@gmx.at
Stephen Berman <stephen.berman <at> gmx.net> writes:
> The doc string of split-window says "Interactively, SIZE is the prefix
> argument." But in fact, invoking split-window with a prefix argument
> has no effect, because its interactive spec is "i". Maybe this is just
> a doc bug, since, when split-window was still a C function, its doc
> string said "Interactively, all arguments are nil." But I don't see why
> it is a command at all any more: invoked interactively, it has exactly
> the same effect as invoking split-window-below without a prefix
> argument, and since the latter does not ignore a prefix argument passed
> to it, it does more than interactively called split-window. So it
> appears to be superfluous for split-window to be a command. Or am I
> overlooking something?
It may be superfluous but it has always been a command and
removing the interactive form would break existing keybindings
and usage.
I think that:
* Fixing the doc-string would be better than removing the
interactive form.
* Changing the interactive form to use the prefix argument would
be better than fixing the doc-string.
--
Rand
next prev parent reply other threads:[~2013-04-12 19:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 7:58 split-window as a command Stephen Berman
2013-04-12 9:29 ` martin rudalics
2013-04-12 11:37 ` Stephen Berman
2013-04-12 14:13 ` martin rudalics
2013-04-12 19:44 ` Rand [this message]
2013-04-12 23:05 ` Xue Fuqiao
2013-04-12 23:31 ` Stephen Berman
2013-04-13 0:52 ` Xue Fuqiao
2013-04-13 1:54 ` Rand User
2013-04-13 2:46 ` Xue Fuqiao
2013-04-13 5:45 ` Rand User
2013-04-13 6:29 ` Xue Fuqiao
2013-04-13 1:44 ` Rand User
2013-04-13 8:03 ` martin rudalics
2013-04-13 2:10 ` Stefan Monnier
2013-04-13 14:45 ` Stephen Berman
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=loom.20130412T214228-407@post.gmane.org \
--to=rand.user@ymail.com \
--cc=emacs-devel@gnu.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 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).