From: storm@cua.dk (Kim F. Storm)
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
Subject: Re: cua-mode and the tutorial
Date: Sat, 26 Aug 2006 00:12:15 +0200 [thread overview]
Message-ID: <m3pseobh34.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1GGiEo-0004HU-JA@fencepost.gnu.org> (Richard Stallman's message of "Fri, 25 Aug 2006 16:25:10 -0400")
Richard Stallman <rms@gnu.org> writes:
> > But we should make it offer to delete the customization
> > in case the user was not asked about it.
>
> Too complex for very little benefit IMHO.
>
> We don't know what method was used to enable CUA-mode. It could be a
> customization, but it could also be an explicit call to CUA-mode in
> emacs. So that is not trivial to do right in all cases.
>
> It is pretty easy to recognize those two methods and DTRT for them.
In one case, it is set system wide in site-load.el.
In another case, it is set in a shared file loaded from .emacs.
In a third case, it is set in another user's .emacs file invoked
through --user option.
Besides, I doubt that very many users would want to disable CUA-mode
if they got their .emacs file from a collegue or friend -- such persons
are often "in sync" with respect to their tools and habits.
I still think this is too complex for very little benefit.
In any case, I will definitely not write the necessary code!
> It is also pretty easy to recognize when neither of those methods was used,
> In the case of Viper, I would rather have it say "You enabled Viper
> mode" and not list the specific differences (there would be too many
> of them, right?).
I suppose so, and the message would only list those keys which correspond
to keys used in the tutorial, so it would not be complete anyway.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-08-25 22:12 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44C8F069.1070002@student.lu.se>
2006-08-22 13:12 ` cua-mode and the tutorial Kim F. Storm
2006-08-22 13:26 ` Kim F. Storm
2006-08-22 14:30 ` Lennart Borgman
2006-08-22 15:02 ` Kim F. Storm
2006-08-22 15:57 ` Lennart Borgman
2006-08-22 18:17 ` Richard Stallman
2006-08-23 4:06 ` Richard Stallman
2006-08-23 4:37 ` Lennart Borgman
2006-08-24 5:20 ` Richard Stallman
2006-08-23 7:21 ` Kim F. Storm
2006-08-24 5:20 ` Richard Stallman
2006-08-24 7:30 ` Kim F. Storm
2006-08-25 20:25 ` Richard Stallman
2006-08-25 22:12 ` Kim F. Storm [this message]
2006-08-26 12:22 ` Richard Stallman
2006-08-26 12:44 ` David Kastrup
2006-08-27 14:34 ` Richard Stallman
2006-08-26 14:19 ` Stefan Monnier
2006-08-26 15:07 ` Drew Adams
2006-08-26 21:15 ` Kim F. Storm
2006-08-27 14:34 ` Richard Stallman
2006-08-27 15:06 ` David Kastrup
2006-08-28 22:09 ` Richard Stallman
2006-08-27 21:30 ` Kim F. Storm
2006-08-26 21:14 ` Kim F. Storm
2006-08-28 9:52 ` Richard Stallman
2006-08-28 10:07 ` David Kastrup
2006-08-28 11:21 ` Kim F. Storm
2006-08-29 17:18 ` Richard Stallman
2006-08-27 8:35 ` Lennart Borgman
2006-08-28 9:52 ` Richard Stallman
2006-08-28 10:17 ` Slawomir Nowaczyk
2006-08-29 17:18 ` Richard Stallman
2006-08-29 17:55 ` Drew Adams
2006-08-29 18:13 ` Lennart Borgman
2006-08-28 22:32 ` Lennart Borgman
2006-08-29 17:18 ` Richard Stallman
2006-08-31 15:10 ` Lennart Borgman
2006-09-21 14:24 ` Kim F. Storm
2006-08-22 14:05 ` Lennart Borgman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3pseobh34.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.