unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 40773@debbugs.gnu.org
Subject: bug#40773: newsticker documentation
Date: Wed, 29 Apr 2020 12:34:25 +0300	[thread overview]
Message-ID: <83v9lizlcu.fsf@gnu.org> (raw)
In-Reply-To: <20200429091213.rtyoo537qgccbccz@E15-2016.optimum.net> (message from Boruch Baum on Wed, 29 Apr 2020 05:12:13 -0400)

> Date: Wed, 29 Apr 2020 05:12:13 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: ulf.jasper@web.de, 40773@debbugs.gnu.org
> 
> > We mention the most important of them in the Emacs manual, but we
> > cannot possible mention all of them.
> 
> Why not? It's --only-- 58. They likely don't change very often. After
> the initial work, which I'm guessing will amount 58 text lines in a
> single .texi file (is that how it works?), how often will it need to be
> changed?

I don't think a single line for a package will do.  Compare with the
descriptions we do have for the manuals we do mention in the Emacs
manual.

> > > Further, as a corollary, I suggest that packages bundled in the default
> > > emacs distribution should NOT have info nodes in the emacs section of
> > > the root info index, ie. no duplication. Either the emacs section of the
> > > root info index should be restricted to non-default emacs packages, or
> > > there shouldn't exist such a section at all, and the emacs manual should
> > > have a section for external packages.
> >
> > I don't think I understand what you propose here.  What is "the root
> > info index"? is that the Emacs menu in the DIR file
> 
> That sounds right. I meant  what I see when I type `C-h i'.

Then I don't understand the rationale for removing the entries from
there.  What useful purpose would that serve?





  reply	other threads:[~2020-04-29  9:34 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 [this message]
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
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=83v9lizlcu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=40773@debbugs.gnu.org \
    --cc=boruch_baum@gmx.com \
    /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).