unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Roehler <andreas.roehler@easy-emacs.de>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Binding F11 and F12 to buffer-switching and file-saving by	default
Date: Wed, 31 Jan 2007 08:52:43 +0100	[thread overview]
Message-ID: <45C04ACB.9030707@easy-emacs.de> (raw)
In-Reply-To: <f7ccd24b0701301815k9d0d6fbic7b9fa06c32c2a66@mail.gmail.com>

>
>
>> Could we at least bind compile/recompile to some key combo, even if 
>> not to F12?
>
> I have no opinion on that.
>

Enhancing Emacs' usability is a good idea. Respecting
better the needs of none-programmers could gain support
from a growing community.

At the other hand: Don't see it could be done that way
Emacs is developed usually: it can't be done by
judgement of one or two persons alone for several
reasons:

- if this person is a skilled one, it will ignore the
  needs of beginners more or less

- if it's a beginner, he will not be able to overview
  the functioning of the whole.

Also habits, tastes of beginners and advanced users
alike are very different: there is no way as in
programming to conclude by logic alone. It needs
systematic research, collecting habits and weighting it
etc.

This work must not be done by core-developers, as it's
a process of collecting users informations, where every
user may take part.

Suggest to create a group of interested persons, which
collect the needed data to make
proposals based on them afterwards.




__
Andreas Roehler

  reply	other threads:[~2007-01-31  7: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
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 [this message]
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=45C04ACB.9030707@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.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).