unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Binding F11 and F12 to buffer-switching and file-saving bydefault
Date: Thu, 01 Feb 2007 15:04:04 -0500	[thread overview]
Message-ID: <g69veil8x1n.fsf@dhcp-65-162.kendall.corp.akamai.com> (raw)
In-Reply-To: E1HCPUj-0001Vu-DA@fencepost.gnu.org

On 31 Jan 2007, rms@gnu.org wrote:

>>> Multiplying bindings for common commands adds confusion IMHO.
>>
>> Hmm. Perhaps that is true. (To the rest of you: Do you agree?)
>
> FWIW, I do. And it does more than add confusion: it raises a shaggy mane
> against Occam's Razor.
>
> I don't think it is useful to argue about this.  The way I plan to
> deal with this issue is based on whether there is any general pattern
> of usage of these keys in other apps.  (That's why I asked.)
> Unless there is one, I'm going to leave these undefined.

Based on my experience, everyone loves to redefine F keys.  They are
very handy, and Emacs shouldn't touch them.

Common usage has no pattern for those keys.  F1 is "help," of course.
F2 is often "save."  The classic Norton Commander gave us file
operations on the F keys that are nice:

F3 = view
F4 = edit
F5 = copy
F6 = move
F7 = mkdir
F8 = delete
F10 = quit

A lot of users like those bindings (myself included) and they are in
the GNU Midnight Commander and in mc.el/nc.el (neither is a part of
Emacs).  They could be useful as an optional feature in Dired, for
example.

> Anyway, now is not the time to change it.

Agreed, I just wanted to mention some "classic" keybindings.

Ted

  reply	other threads:[~2007-02-01 20:04 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
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 [this message]
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=g69veil8x1n.fsf@dhcp-65-162.kendall.corp.akamai.com \
    --to=tzz@lifelogs.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).