unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Lars Hansen <larsh@math.ku.dk>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Default Emacs keybindings (was: Re: Menu suggestion)
Date: 27 Apr 2004 13:25:13 +0200	[thread overview]
Message-ID: <x57jw17jdy.fsf@lola.goethe.zz> (raw)
In-Reply-To: <jkllkh3ck3.fsf@glug.org>

Thien-Thi Nguyen <ttn@glug.org> writes:

> David Kastrup <dak@gnu.org> writes:
> 
>    As long as the superuser can't with a good conscience throw
>    Emacs at his users, he is not free to use the editor he
>    prefers.
> 
> because naked emacs may be seen as an unkindness in some cultures,
> the crafty superuser throws instead an emacs wrapped in session-,
> site-, or user-specific customizations.

It is not only in a closed shop that my expertise is appreciated.
For example, I am a frequent poster in comp.text.tex and other Usenet
groups.  I can start advice with "if you use Emacs, it is a matter
of..."  I can't start advice with "if you happen to have a service
contract with me and I installed and maintain your copy of Emacs, you
could..."

It is the difference between "with Emacs, you could" and "with my
Emacs, I can".  The latter is gloating rather than helping.

And I don't think we should strive for superuser lock-in: painful
experiences whenever users switch between administrators.  Emacs
should by and large be delivered in a useful state for everyone
without the need for serious reconfiguration.  The better we can
achieve that goal, the more universal Emacs experience becomes.

>    If somebody asks me about a text manipulation problem, and I tell
>    him "just use this one-liner in Emacs" and he says "Forget it.  I
>    don't have a week to spare.  How do I do this in KEdit?", this
>    ultimately forces me to acquire skills with inferior tools in
>    order to kludge along.
> 
> or you could write the one-liner into a file, add five lines of
> comment and/or docstring, and place the file in some shared
> directory where it can be accessed in the future, and studied and
> improved as time permits.  this can be done by all users.

They will still need to use Emacs.

>    The question "is it really worth it?" should, if possible, not
>    come up again and again.
> 
> IMHO, that kind of question is always pertinent.  the answer
> may gradually shift from no to yes, as the environment (which
> includes machines, regular users, and any superusers floating
> in the vicinity) changes.  if the answer does not shift and
> the superusers floating in the vicinity do not effect change,
> that says more about those superusers than the question.

Superusers stand on the shoulders of developers.  On the shoulder of
giants, even dwarfs can look far.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2004-04-27 11:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26 11:33 Default Emacs keybindings (was: Re: Menu suggestion) Lars Hansen
2004-04-26 13:26 ` Jan D.
2004-04-27  6:45   ` Eli Zaretskii
2004-04-27  7:23     ` Jan D.
2004-04-27  8:43       ` Steven Tamm
2004-04-27 15:17         ` Kim F. Storm
2004-04-27 16:46           ` Steven Tamm
2004-04-27 15:27       ` Piet van Oostrum
2004-04-27  8:24 ` Richard Stallman
2004-04-27  9:36   ` Lars Brinkhoff
2004-04-27 10:42     ` Jan Nieuwenhuizen
2004-04-27  9:54   ` David Kastrup
2004-04-27 10:23     ` Default Emacs keybindings Lars Hansen
2004-04-27 11:06     ` Default Emacs keybindings (was: Re: Menu suggestion) Thien-Thi Nguyen
2004-04-27 11:25       ` David Kastrup [this message]
2004-05-02 23:31         ` Thien-Thi Nguyen
2004-04-27 13:03     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2004-04-23 21:24 Menu suggestion David Kastrup
2004-04-24 23:02 ` Kim F. Storm
2004-04-25 23:35   ` Richard Stallman
2004-04-26  8:23     ` Default Emacs keybindings (was: Re: Menu suggestion) Per Abrahamsen
2004-04-26 13:35       ` Luc Teirlinck
2004-04-26 13:44       ` Alan Mackenzie
2004-04-26 15:16         ` David Kastrup
2004-04-26 22:33           ` Kim F. Storm
2004-04-26 21:36             ` David Kastrup
2004-04-26 23:06               ` Luc Teirlinck
2004-04-27 14:04               ` Stefan Monnier
2004-04-27 14:22                 ` David Kastrup
2004-04-29 19:42                   ` Stefan Monnier
2004-05-24 14:08               ` Richard Stallman
2004-05-26 16:18                 ` Stefan Monnier
2004-05-26 17:01                   ` David Kastrup
2004-05-27 23:53                   ` Richard Stallman
2004-05-28 21:06                   ` Stefan Monnier

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=x57jw17jdy.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsh@math.ku.dk \
    --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).