From: Jose E. Marchesi <jemarch@gnu.org>
To: emacs-devel@gnu.org, emacs-devel-request@gnu.org
Subject: Re: Emacs-devel Digest, Vol 77, Issue 62
Date: Sun, 11 Jul 2010 13:54:31 +0200 (CEST) [thread overview]
Message-ID: <20100711.135431.300715226.jemarch@gnu.org> (raw)
In-Reply-To: <20100711111123.94F0946D172@chapters.gnu.org>
Why should they spend time to configure such basic things to try
an obscure editor? They won't do that and that's why with time
emacs will probably be more and more an obscure editor.
It's sad, because it's such a great tool, and I don't want to see
it fade away in obscurity. But if easy of entry is not increased
for casual users then it is the most probable future for our
beloved editor.
Is really Emacs fading away? In that case, how it comes it did not
fade away before in more than 20 years of history?
I mean, are we sure we are talking about a real problem? After a lot
of years suggesting people to run the Emacs tutorial I never got a
single complaint about C-c and C-v not working "as expected". Maybe I
was extremely lucky.
The Bauer Principle is applicable here, IMHO. In Van Wijngaarden
words: "Who does not want to use complex facilities, does not pay for
them. If the user wants to use them, he has to pay a little."
But really, in this specific case the "payment" is as little as
reading a paragraph in the tutorial explaining the usage of the
kill-ring and C-y. Anyone with the minimum amount of interest should
be able to pass through it.
parent reply other threads:[~2010-07-11 11:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20100711111123.94F0946D172@chapters.gnu.org>]
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=20100711.135431.300715226.jemarch@gnu.org \
--to=jemarch@gnu.org \
--cc=emacs-devel-request@gnu.org \
--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 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.