unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: 9350@debbugs.gnu.org
Subject: bug#9350: 23.3; File menu should contain "split window horizontally C-x 3"
Date: Sun, 23 Oct 2011 20:59:44 +0200	[thread overview]
Message-ID: <4EA46420.2040603@gmx.at> (raw)
In-Reply-To: <87d3dn7t7j.fsf@mail.jurta.org>

 >> I'd eventually want to rename `split-window' to `new-window' or
 >> `make-new-window' and give it a fourth argument - the buffer to show in
 >> the new window.
 >
 > Isn't this semantically equivalent to `switch-to-buffer-other-window'?

No.  `split-window' is low-level.  But you're right in the sense that
calls to it should be replaced by `switch-to-buffer' wherever possible.

 > And since this bug report is about menu items, another question:
 > after shifting the emphasis from windows/frames to just places where
 > to display buffers, wouldn't it make more sense to move window/frame
 > related menu items from the "File" menu to the "Buffers" menu?

Conceptually yes.  IIRC some of the buffer switching functions were in
files.el only until recently.  So the presence of window handling
function in the File menu is probably historically motivated.  But menus
are (also) for people who might not even know what buffers, windows or
frames are.  Most of them know what files are.

 > This will also balance these menus where the "File" menu is
 > currently overpopulated, and the size of the "Buffers" menu
 > is limited anyway (later it could be organized into submenus
 > grouped by modes etc.)

Doesn't the buffer menu get crowded when there are lots of live buffers?
I can't tell because I have (global-set-key [menu-bar buffer] nil) in my
.emacs for years.

martin





  reply	other threads:[~2011-10-23 18:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 13:54 bug#9350: 23.3; [usability] File menu should contain "split window horizontally C-x 3" Arne Babenhauserheide
2011-08-23 15:23 ` Eli Zaretskii
2011-08-24  9:51 ` Juri Linkov
2011-10-17 13:12 ` bug#9350: 23.3; " martin rudalics
2011-10-17 15:33   ` Stefan Monnier
2011-10-17 18:54     ` martin rudalics
2011-10-17 19:51       ` Stefan Monnier
2011-10-21  9:31         ` martin rudalics
2011-10-21 13:36           ` Stefan Monnier
2011-10-21 13:46             ` martin rudalics
2011-10-21 14:19               ` Stefan Monnier
2011-10-23 13:29       ` Juri Linkov
2011-10-23 18:59         ` martin rudalics [this message]
2011-10-24  5:19           ` Juri Linkov

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=4EA46420.2040603@gmx.at \
    --to=rudalics@gmx.at \
    --cc=9350@debbugs.gnu.org \
    --cc=juri@jurta.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).