From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Jean Louis <bugs@gnu.support>
Cc: 43636@debbugs.gnu.org
Subject: bug#43636: 28.0.50; About Emacs, shall be descriptive and point to Info file
Date: Sun, 27 Sep 2020 12:14:04 -0700 (PDT) [thread overview]
Message-ID: <9c2cd7e8-7baf-4b9d-893e-ea182bd1eebc@default> (raw)
In-Reply-To: <<83zh5bof2y.fsf@gnu.org>>
> > For me it is: general computing environment
>
> That sounds too general and abstract to be useful. E.g., I could say
> the same about any modern OS.
Yes. IMO, nearly any list of general labels won't
be very helpful. It might suffice to say at the
outset that you can do lots of things with Emacs -
it is a text editor and more. IOW, the old "kitchen
sink".
It's by examples (even descriptions of examples)
that we can convey the breadth of "what you can do"
with Emacs. A list of labels won't help anyone
much, IMO.
next parent reply other threads:[~2020-09-27 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<courier.000000005F6FA714.00005079@protected.rcdrun.com>
[not found] ` <<833633pvuw.fsf@gnu.org>
[not found] ` <<20200927065215.GB13324@protected.rcdrun.com>
[not found] ` <<83zh5bof2y.fsf@gnu.org>
2020-09-27 19:14 ` Drew Adams [this message]
2020-09-26 20:39 bug#43636: 28.0.50; About Emacs, shall be descriptive and point to Info file Jean Louis
2020-09-27 6:38 ` Eli Zaretskii
2020-09-27 6:52 ` Jean Louis
2020-09-27 7:26 ` Eli Zaretskii
2020-09-27 15:48 ` Jean Louis
2020-09-28 3:44 ` Richard Stallman
2021-12-05 0:53 ` Lars Ingebrigtsen
2021-12-05 1:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-05 1:59 ` Lars Ingebrigtsen
2021-12-05 2:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-05 19:54 ` Lars Ingebrigtsen
2021-12-05 9:20 ` Juri Linkov
2021-12-05 19:54 ` Lars Ingebrigtsen
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=9c2cd7e8-7baf-4b9d-893e-ea182bd1eebc@default \
--to=drew.adams@oracle.com \
--cc=43636@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=eliz@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).