From: storm@cua.dk (Kim F. Storm)
Cc: lennart.borgman.073@student.lu.se, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: cua-mode and the tutorial
Date: Mon, 28 Aug 2006 13:21:10 +0200 [thread overview]
Message-ID: <m3ejv1ds2h.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <85hczxw4uw.fsf@lola.goethe.zz> (David Kastrup's message of "Mon, 28 Aug 2006 12:07:35 +0200")
David Kastrup <dak@gnu.org> writes:
> Richard Stallman <rms@gnu.org> writes:
>
>> You're the only one involved, in this scenario, so you're
>> not treating anyone else badly.
>>
>> But this is a special case, and you're the one who has told me that
>> some sysadmins set up Emacs in a nonstandard way for _other people_.
I didn't mean to say anyone actually does this.
We discussed whether it was worth the trouble to write code which
specifically tries to _remove_ CUA setting that the user may
not have installed himself.
So I tried to give examples where of ways it _can_ be done, that would
be non-trivial to remove (hoping that we could drop that idea and do
more important work).
>>
>> And what exactly do you intend to change? Enabling cua-mode,
>> viper-mode, delete-selection-mode, pc-selection-mode, glasses-mode,
>> .. any minor mode?
>>
>> Perhaps this should be done for whichever modes we find are often
>> being imposed on other users in this way.
I honestly don't think that there are any such modes which are _often_
imposed on other users through site-start.el etc.
In most cases, people who want to introduce someone to emacs may
give the newbee a copy of their own .emacs to look at and use
initially. We neither can nor should try to control what people
share in this way.
> We are interfering in that manner with the freedom of adapting Emacs
> to one's wishes. What next? Will we use DRM to ensure that all
> variables we consider worthy are left at standard settings?
>
> Emacs is free software. Part of the freedom is being able to do
> things that upstream did not think a good idea. I am strictly opposed
> to booby-trapping Emacs with code that reverts a consciously made
> decision downstream.
I agree with David -- but even if I didn't, I wouldn't spend as much
as one second writing the code necessary to impose such restrictions.
[and I've already spent way too much time discussion this (non-)issue].
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-08-28 11:21 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
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 [this message]
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
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=m3ejv1ds2h.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=rms@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).