From: Emanuel Berg via "Emacs development discussions." <emacs-devel@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Implicit assumptions in the latest discussions
Date: Fri, 18 Sep 2020 09:45:45 +0200 [thread overview]
Message-ID: <87h7rvle8m.fsf@ebih.ebihd> (raw)
In-Reply-To: 1bc3251a-7b36-f151-7fc6-9ecf2639bb9f@grinta.net
Daniele Nicolodi wrote:
> 2. Users are not drawn to try Emacs because what
> Emacs is and for his reputation, but because
> they expect Emacs to be like other editors.
>
> I think that who chooses Emacs, does so because of
> what Emacs is and what it has been in its long
> history, not because they expect something
> different. [...]
People really "expect" the way you describe?
I can only tell my experience.
I opened Emacs. The font lock, or syntax highlighting
as I'd call it at that point, looked cool.
I wanted to change a bunch of stuff, like
I always do. But unlike other software, with
a rudimentary config file - which is already awesome,
at that point - see my mpv stuff [1] - not that
I used mpv back then, if it was even around - ANYWAY
- I realized that Emacs didn't provide me with just
an .rc file where I could set a bunch of options that
it would parse, no, I was actually _programming_,
and in Lisp, which I considered cool (and still do).
The step from `setq's to `defun's, I don't know when
that happened, probably right away. I realized this
whole thing was an awesome window for my own
creativity. I didn't expect anything but realized
it instantly.
I've always been obsessed by tools: text editor or
revolving hole punch, it doesn't matter, I modify
them and spend time with them like other people do
their CD collections or whatever. (People don't
collect CDs anymore.)
I don't know what features or what is different with
modern editors or where they have the huge advantage.
What I saw before Emacs were idle, nano, notepad++,
Eclipse, Visual Studio, and a couple of others;
either they were super-simple (much, much too simple)
or they had the GUI/menu based style which I pretty
much came to programming because I _didn't_ like.
So if I expected anything, which I doubt,
I absolutely did not expect Emacs to be anything like
that. In fact, the more it _wasn't_ like that, the
more I'd like it...
Maybe today there are fundamentally different
editors, different compared to nano (simple), Emacs
(Emacs), and Eclipse (GUI/menu), and every other
editor I know. Yes, it would be interesting to have
a look at them...
But, instead of making Emacs more like them in
general, let's hear it, make a list of their three
killer features that they have, and we don't. We take
it from there :)
[1] https://dataswamp.org/~incal/conf/mpv/mpv.conf
https://dataswamp.org/~incal/conf/mpv/input.conf
BTW mpv is perhaps a poor example here because it
is also extendible, with Lua.
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
prev parent reply other threads:[~2020-09-18 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 13:30 Implicit assumptions in the latest discussions Daniele Nicolodi
2020-09-17 14:01 ` Robert Pluim
2020-09-17 14:45 ` Daniele Nicolodi
2020-09-17 15:04 ` Arthur Miller
2020-09-17 15:09 ` Daniel Martín
2020-09-17 15:29 ` Caio Henrique
2020-09-17 15:32 ` Robert Pluim
2020-09-17 17:41 ` Eli Zaretskii
2020-09-17 19:31 ` Mingde (Matthew) Zeng
2020-09-18 7:45 ` Emanuel Berg via Emacs development discussions. [this message]
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=87h7rvle8m.fsf@ebih.ebihd \
--to=emacs-devel@gnu.org \
--cc=moasenwood@zoho.eu \
/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.