[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs learning curve
From: |
Óscar Fuentes |
Subject: |
Re: Emacs learning curve |
Date: |
Tue, 13 Jul 2010 02:18:24 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
"Alfred M. Szmidt" <address@hidden> writes:
> You are conflating two separate issue, one of terminology, and one of
> non-working features, so are many people in this thread.
Not really. The terminology is just a small part of the whole issue,
which is the kind of people Emacs development should target. Here on the
Bikeshedding Paradise (a.k.a. emacs-devel) it is understandable that
people tend to see this as a debate on terminology and ignore the really
important issue, but let's try to not do that.
[snip]
> Regarding features, this is infact what people are having problems
> with, like yourself and _not_ about terminology. The most basic
> prerequisite for any feature is that it should work without any
> configuration, one shouldn't have to define what a tetromino is to
> play tetris even though your tetromino might be different from mine.
I'm glad you think like this. I have the impression that some prominent
hackers here think that it is a good thing and a show of distinction to
produce systems that require reading a manual and do quite a bit of
tinkering before usage. This is a symptom of the hacker's limitations,
of course. He implicitly acknowledges that designing the system on a way
that does not require that burden from the user was too much for him
(there is no derogatory intention towards any Emacs hacker here)
> In your case, CEDET not working out of the box, and being hard to
> configure on top of that. This is a bug, could you file a bug report
> so that the problem can be looked at? If people don't report problems
> they experience, then they won't be known.
I'm afraid that the problem was on the third party Elisp package that
provided C# support to CEDET. It required tweaks here and there to make
compile with the CEDET that is distributed with Emacs, lacked detailed
instructions and smelled like unmaintained since a few years ago.
Again, this is not the real issue. The lesson here is that Emacs can
learn a lot from other projects wrt how to behave towards its potential
audience.
- Re: CEDET, (continued)
- Re: Emacs learning curve, Sean Sieger, 2010/07/13
- RE: Emacs learning curve, Drew Adams, 2010/07/13
- Re: Emacs learning curve, Sean Sieger, 2010/07/13
- Re: Emacs learning curve, Uday S Reddy, 2010/07/14
- RE: Emacs learning curve, Drew Adams, 2010/07/14
- Re: Emacs learning curve, David Kastrup, 2010/07/14
- Re: Emacs learning curve, Alfred M. Szmidt, 2010/07/12
- Re: Emacs learning curve,
Óscar Fuentes <=
- Re: Emacs learning curve, Uday S Reddy, 2010/07/13
- Re: Emacs learning curve, Richard Stallman, 2010/07/13
- Re: Emacs learning curve, christian.lynbech, 2010/07/13
- Re: Emacs learning curve, David Kastrup, 2010/07/13
- Re: Emacs learning curve, joakim, 2010/07/13
- Re: Emacs learning curve, immanuel litzroth, 2010/07/13
- Re: Emacs learning curve, Eric M. Ludlam, 2010/07/13
- Re: Emacs learning curve, Óscar Fuentes, 2010/07/13
- Re: Emacs learning curve, Eli Zaretskii, 2010/07/13
- Developer contributions / was: Re: Emacs learning curve, David Reitter, 2010/07/13