From: Adrian.B.Robert@gmail.com
To: emacs-devel@gnu.org
Subject: Re: Casting as wide a net as possible
Date: Mon, 14 Dec 2015 15:05:19 +0200 [thread overview]
Message-ID: <866101faeo.fsf@gmail.com> (raw)
In-Reply-To: m2d1uenn4h.fsf@newartisans.com
John Wiegley <jwiegley@gmail.com> writes:
>>>>>> Drew Adams <drew.adams@oracle.com> writes:
>
>> My only point is that Lisp features really do make Emacs what it is. To
>> point out what Emacs is necessarily means pointing out some of those
>> features (IMO).
>
> I agree. The things that make Emacs great:
>
> 1. Highly consistent syntax.
> 2. Self-documenting.
> 3. Integrated debugger.
> 4. Ability to re-evaluate functions in a running environment.
> (i.e., everything that made Lisp Machines great)
> 5. Natural syntax for scoping resources (`with-temp-buffer ...')
> 6. Large and well documented API
> 7. Stable and mature concepts evolved over decades
> 8. Huge, HUGE community of cargo-cultable examples, for those just learning
These are all good, but, aside from #2 and #3, relatively deep and
sophisticated. The simpler aspects that keep driving me back to use Emacs
even as good IDEs and other tools proliferate, and the reasons I encourage
others to try it:
1. Do things that often *can't be done* in other editors:
- *everything* from the keyboard
- fast, low-overhead keyboard navigation (faster than any IDE)
- split windows for multiple spots in file or multiple files
- clean, complete l10n handling
- regex search/replace
- keyboard macros
2. Do things *more easily* than other editors
- discovery: M-x command completion and shortcut hinting (part
of self-documenting, means can learn to use keyboard easily)
- swiss-army knife: learn once, edit many types of content
(rather than dealing with a new tool for every job)
- works same on any desktop box
- works same on remote *nix machines as in a local desktop
(rather than suffering with vi etc.)
- emacsclient (big when working with command-line shells in a
desktop environment)
3. Better *customization* than other editors
- menu options plus straightforward simple customization
- full programmability for complex cases
- *easily* migrate customization from environment to environment
Overall, due to excellent design philosophy and a highly extensible
foundation, Emacs delivers an unparalleled environment for focusing on what
you want to do, rather than spending time fiddling and fighting with your
tools.
next prev parent reply other threads:[~2015-12-14 13:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 16:46 Casting as wide a net as possible (was: First draft of the Emacs website) John Yates
2015-12-10 17:31 ` Eli Zaretskii
2015-12-10 18:56 ` Drew Adams
2015-12-10 19:02 ` Casting as wide a net as possible John Wiegley
2015-12-10 19:07 ` Eli Zaretskii
2015-12-10 19:48 ` David Kastrup
2015-12-10 20:01 ` Eli Zaretskii
2015-12-10 20:17 ` David Kastrup
2015-12-10 20:19 ` John Wiegley
2015-12-10 20:50 ` David Kastrup
2015-12-11 7:09 ` Richard Stallman
2015-12-10 19:54 ` covici
2015-12-10 21:21 ` Marcin Borkowski
2015-12-14 13:05 ` Adrian.B.Robert [this message]
2015-12-14 16:21 ` raman
2015-12-14 18:21 ` John Wiegley
2015-12-11 7:08 ` Casting as wide a net as possible (was: First draft of the Emacs website) Richard Stallman
2015-12-11 16:14 ` Casting as wide a net as possible raman
2015-12-14 14:41 ` Filipp Gunbin
2015-12-14 15:01 ` Yuri Khan
2015-12-14 17:20 ` Filipp Gunbin
2015-12-14 17:59 ` Random832
2015-12-14 18:19 ` Yuri Khan
2015-12-15 18:12 ` Filipp Gunbin
2015-12-15 18:54 ` Random832
2015-12-15 19:03 ` Random832
[not found] <<CAJnXXogJywM4xRM9OEF1RKEwOib_G_JJvj=YThhsUwFn6gHviQ@mail.gmail.com>
[not found] ` <<fa45f69a-b8df-46f8-8fda-4735dc34e4dc@default>
[not found] ` <<m2d1uenn4h.fsf@newartisans.com>
[not found] ` <<83a8pi9l6o.fsf@gnu.org>
2015-12-10 19:15 ` Drew Adams
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=866101faeo.fsf@gmail.com \
--to=adrian.b.robert@gmail.com \
--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 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).