From: Jeff Clough <jeff@chaosphere.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs User Friendliness Question/Hope
Date: Fri, 16 Jul 2010 11:26:01 -0400 [thread overview]
Message-ID: <1279293961.2135.143.camel@logrus.localdomain> (raw)
In-Reply-To: <AANLkTinkKz4kSp57HiBh7lxr6DAIhsD1cpacLpo20M88@mail.gmail.com>
On Fri, 2010-07-16 at 16:38 +0200, Deniz Dogan wrote:
> > I don't think it's unreasonable for a new "usability" feature to check a
> > global setting before doing it's magic. Or to otherwise be disabled
> > unless either enabled specifically or enabled via a global "make Emacs
> > work like Notepad" command. Make it on by default, but give me a way to
> > turn it off with one line, as opposed to having one to three lines for
> > every one of these enhancements.
> >
>
> But that's easier said than done, isn't it? Where should we draw the
> line between what's "new" and Notepad-ish and what's "old" and
> Emacs-y? To be honest, it sounds like you're looking to add a function
> to Emacs which makes it act exactly as the way you want it to. Every
> Emacs user has their own taste, which is why the init files exist in
> the first place. Let's not start adding what is essentially custom
> user configurations to Emacs.
>
I think you have over-generalized what I was asking for.
If you look through some of the recent (and not-so-recent) discussions
on emacs-devel, you will see a number of
proposed/implemented/soon-to-be-implemented changes, the primary (if not
*only*) justification for which is making Emacs behave more like a
typical window-based application.
It's my hope that *those* changes can be easily turned off, not on a
per-enhancement basis, but through a convenient variable. Look at it as
an exercise in bundling these enhancements into something analogous to a
compatibility mode like those that exist for vi in one form or another.
Put the mode on by default, but let the people who want to turn it off.
Your statements concerning "a function which makes emacs act exactly as
I want" and "adding what is essentially custom user configurations to
Emacs" are definitely *not* describing what I am requesting.
Jeff
next prev parent reply other threads:[~2010-07-16 15:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 10:48 Emacs User Friendliness Question/Hope Jeff Clough
2010-07-16 14:07 ` Uday S Reddy
2010-07-16 14:30 ` Jeff Clough
2010-07-16 14:38 ` Deniz Dogan
2010-07-16 15:26 ` Jeff Clough [this message]
2010-07-16 17:01 ` Chad Brown
2010-07-16 22:50 ` Phil Hagelberg
2010-07-17 0:16 ` Fernando C.V.
2010-07-17 1:41 ` Christoph
2010-07-17 2:11 ` Miles Bader
2010-07-17 3:08 ` Óscar Fuentes
2010-07-17 3:34 ` Miles Bader
2010-07-18 12:36 ` Stephen J. Turnbull
2010-07-18 12:59 ` Deniz Dogan
2010-07-18 13:20 ` Geoff Gole
2010-07-18 14:10 ` Stephen J. Turnbull
2010-07-19 14:37 ` Geoff Gole
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=1279293961.2135.143.camel@logrus.localdomain \
--to=jeff@chaosphere.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).