From: Stephen Berman <stephen.berman@gmx.net>
To: Rand <rand.user@ymail.com>
Cc: emacs-devel@gnu.org
Subject: Re: split-window as a command
Date: Sat, 13 Apr 2013 01:31:19 +0200 [thread overview]
Message-ID: <877gk7fhrs.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <loom.20130412T214228-407@post.gmane.org> (Rand's message of "Fri, 12 Apr 2013 19:44:31 +0000 (UTC)")
On Fri, 12 Apr 2013 19:44:31 +0000 (UTC) Rand <rand.user@ymail.com> wrote:
> 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.
Maybe in the early days there was no split-window-vertically and
split-window was the only window-splitting command (I don't know). But
at least since 18.59 (probably earlier) split-window has been redundant
as a command (and not documented in the Emacs manual), and has not had a
default key binding. So any breakage would be in user settings or
third-party packages. And the fix would simply be to add "-below" to
such occurrences of "split-window", which doesn't seem like much of a
hardship. As for usage, since split-window never acted on a prefix
argument, replacing it with split-window-below interactively instead can
only be a win.
> I think that:
>
> * Fixing the doc-string would be better than removing the
> interactive form.
That would perpetuate its mistaken current status as a command.
> * Changing the interactive form to use the prefix argument would
> be better than fixing the doc-string.
That would mean adding code from split-window-below to process the
prefix argument, though split-window-below itself calls split-window.
That doesn't seem very clean.
It would be nice if there were a make-obsolete-command function, so
invoking split-window would warn: "This function is obsolete as a
command since 24.4; use `split-window-below' instead.
Steve Berman
next prev parent reply other threads:[~2013-04-12 23:31 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
2013-04-12 23:05 ` Xue Fuqiao
2013-04-12 23:31 ` Stephen Berman [this message]
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=877gk7fhrs.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=rand.user@ymail.com \
/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).