From: Jason Spiro <jasonspiro4+news@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Binding F11 and F12 to buffer-switching and file-saving by default
Date: Tue, 30 Jan 2007 05:52:36 -0500 [thread overview]
Message-ID: <8764ao3hxn.fsf@localhost.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: f7ccd24b0701300059l3f4af2f1w67f36e71125c49ba@mail.gmail.com
Hi Juanma,
You make many good points. However, I have replies to each of them. :-)
"Juanma Barranquero" <lekktu@gmail.com> wrote:
> You'd have to define "practical"
I define it as "the benefits to new Emacs users with no .emacs file
outweigh the costs." IMO, it is important that new users enjoy Emacs
as soon as possible. If they enjoy it, they will continue using it
forever.
> Not all keyboards have F11 and F12
That's OK. People without those keys can use C-x C-s and C-x b.
> I don't think there's much agreement about the best way to switch
> buffers (I don't use iswitchb-buffer, for example, but bs-cycle-next,
> so your proposed binding is of no use to me)
We should pick one method. People who don't like it can rebind the key.
> next-buffer and previous-buffer are already in C-x <left|right>
iswitchb-buffer is not bound to anything :-)
> save-buffer is in C-x C-s
On second thought, C-x C-s isn't that hard to type. OK, so let's bind
M-x recompile to F11 instead? Buffer switching can be bound to F12.
> Whether a command is used/useful enough to merit a one-key binding
> is highly subjective (I don't use save-buffer often enough to consider
> C-x C-s a burden, for example)
Agreed.
> It's easy for users to do their own bindings
True, but it can be handy to have useful bindings preset by default.
So, do the benefits to newbies outweigh the costs?
--Jason
next prev parent reply other threads:[~2007-01-30 10:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 8:47 Binding F11 and F12 to buffer-switching and file-saving by default Jason Spiro
2007-01-30 8:59 ` Juanma Barranquero
2007-01-30 10:52 ` Jason Spiro [this message]
2007-01-30 11:43 ` Juanma Barranquero
2007-01-30 20:43 ` Jason Spiro
2007-01-31 1:51 ` Juanma Barranquero
2007-01-31 1:55 ` Jason Spiro
2007-01-31 2:15 ` Juanma Barranquero
2007-01-31 7:52 ` Andreas Roehler
2007-01-31 7:47 ` David Kastrup
2007-01-31 18:58 ` Jiri Pejchal
2007-02-01 12:35 ` Stephen Leake
2007-02-01 19:49 ` Ted Zlatanov
2007-01-31 2:19 ` Stefan Monnier
2007-02-01 12:29 ` Stephen Leake
2007-01-31 16:51 ` Binding F11 and F12 to buffer-switching and file-saving bydefault Drew Adams
2007-02-01 0:08 ` Richard Stallman
2007-02-01 20:04 ` Ted Zlatanov
2007-01-30 20:27 ` Binding F11 and F12 to buffer-switching and file-saving by default Eli Zaretskii
2007-01-30 20:45 ` Jason Spiro
2007-01-30 20:25 ` Richard Stallman
2007-01-30 15:09 ` Stefan Monnier
2007-01-31 15:21 ` Stephen Leake
2007-02-01 3:47 ` Daniel Brockman
2007-02-01 1:09 ` JD Smith
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=8764ao3hxn.fsf@localhost.i-did-not-set--mail-host-address--so-tickle-me \
--to=jasonspiro4+news@gmail.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).