unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37812@debbugs.gnu.org, Richard Stallman <rms@gnu.org>,
	Nicholas Drozd <nicholasdrozd@gmail.com>
Subject: bug#37812: Update Emacs manual intro with more compelling features
Date: Sat, 19 Oct 2019 09:47:32 +0200	[thread overview]
Message-ID: <875zkl5g8b.fsf@gmx.de> (raw)
In-Reply-To: <83sgnp6wbq.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 19 Oct 2019 10:14:33 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> The introduction to the Emacs manual says, right near the beginning:
>> "We call Emacs 'advanced' because it can do much more than simple
>> insertion and deletion of text.  It can control subprocesses, indent
>> programs automatically, show multiple files at once, and more."
>>
>> This text has been around for a long time*. Maybe it's time for an
>> update? Indenting programs automatically and showing multiple files at
>> once aren't very compelling features these days. My go-to example of a
>> remarkable Emacs-y feature is EWW, so maybe "browse the Web" could be
>> added? Or something to do with Org mode? I don't know exactly, but
>> listing "shows multiple files" as a feature is like describing someone
>> as "punctual" in a reference letter -- it could signal that the person
>> has no other important qualities.
>
> EWW and Org are very high-level Lisp applications, they aren't
> examples of basic features of Emacs as an editor.  So I'm not sure
> they are appropriate in that introductory section.

We could say that Emacs is able to edit remote files like they were
local files. I'm biased, of course :-)

Best regards, Michael.





  reply	other threads:[~2019-10-19  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 17:50 bug#37812: Update Emacs manual intro with more compelling features Nicholas Drozd
2019-10-19  7:14 ` Eli Zaretskii
2019-10-19  7:47   ` Michael Albinus [this message]
2019-10-19  9:30     ` Eli Zaretskii
2019-10-19 13:27       ` Michael Albinus
2019-10-19 16:14     ` 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=875zkl5g8b.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=37812@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=nicholasdrozd@gmail.com \
    --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).