From: Boruch Baum <boruch_baum@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40773@debbugs.gnu.org
Subject: bug#40773: newsticker documentation
Date: Wed, 29 Apr 2020 15:13:01 -0400 [thread overview]
Message-ID: <20200429191300.3456vbbluowhap54@E15-2016.optimum.net> (raw)
In-Reply-To: <83v9lizlcu.fsf@gnu.org>
On 2020-04-29 12:34, Eli Zaretskii wrote:
> Then I don't understand the rationale for removing the entries from
> there. What useful purpose would that serve?
I hit 'send' too soon; no corrections necessary, but some additional
comments follow...
1] The section for emacs add-ons should make clear that for features
FSF/GNU/emacs has no control over the content and its licensing, can't
be depended to offer support, and whatever mumble mumble lawyers
insist on including.
2] The proposal neatly divides default emacs from extensions, and is a
nice solution, but it is 'lazy' and 'easy' at the expense of trying
to provide a single integrated manual that organizes ALL components
of any single user's individual emacs by related subject. This more
difficult alternative would be a cross between an info index page and
the output of M-x info-display-manual. In that case, the root info
page would just have a single entry for emacs, maybe even not
justifying a separate section labeled emacs.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2020-04-29 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 15:55 bug#40773: newsticker documentation Boruch Baum
2020-04-28 13:08 ` Ulf Jasper
2020-04-29 4:18 ` Boruch Baum
2020-04-29 7:58 ` Eli Zaretskii
2020-04-29 9:12 ` Boruch Baum
2020-04-29 9:34 ` Eli Zaretskii
2020-04-29 18:55 ` Boruch Baum
2020-04-29 19:14 ` Eli Zaretskii
2020-04-29 19:25 ` Boruch Baum
2020-04-29 19:13 ` Boruch Baum [this message]
2022-02-07 1:19 ` 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=20200429191300.3456vbbluowhap54@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=40773@debbugs.gnu.org \
--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).