From: Rand User <rand.user@ymail.com>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: split-window as a command
Date: Fri, 12 Apr 2013 18:44:43 -0700 (PDT) [thread overview]
Message-ID: <1365817483.22022.YahooMailNeo@web141205.mail.bf1.yahoo.com> (raw)
In-Reply-To: <877gk7fhrs.fsf@rosalinde.fritz.box>
From: Stephen Berman <stephen.berman@gmx.net>
> 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.
To my knowledge, that's all correct.
I kinda figured that `split-window' was made a command since its easier
to do `M-x split-window' than `M-x split-window-vertically'.
> So any breakage would be in user settings or third-party packages.
That's the worst kind of breakage. Emacs shouldn't break user code
for minor namespace cleanup.
> 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 agree that `split-window-below' works better interactively than `split-window'
does. Breaking backward compatibility is not a win however.
>> 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.
I don't think `split-window' was mistakenly made 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.
The window splitting code in general doesn't seem very clean... :)
Maybe you could move some of the functionality in split-window-below
to split-window?
Cheers,
Rand
next prev parent reply other threads:[~2013-04-13 1: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
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 [this message]
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=1365817483.22022.YahooMailNeo@web141205.mail.bf1.yahoo.com \
--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).