From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43633@debbugs.gnu.org
Subject: bug#43633: 28.0.50; Include definitions in glossary for: extensible, customizable, self-documenting, real-time display editor
Date: Sat, 26 Sep 2020 23:33:29 +0300 [thread overview]
Message-ID: <20200926203329.GA20474@protected.rcdrun.com> (raw)
In-Reply-To: <83v9g0pif7.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2020-09-26 20:17]:
> > From: Jean Louis <bugs@gnu.support>
> > Date: Sat, 26 Sep 2020 19:06:18 +0200
> >
> >
> > When one goes into Info file, there is sentence:
> >
> > Emacs is the extensible, customizable, self-documenting real-time
> > display editor.
> >
> > In my opinion, those terms are special in Emacs, and should be
> > described as terms in the Glossary section of Emacs Info file.
>
> I don't understand: these terms are explained right there in the
> section which starts with that sentence. Why would we need to explain
> them in the Glossary?
By the sole definition of what glossary represents.
> I also don't understand how these terms are special in Emacs, I think
> we use them in their usual meaning.
The Intro section defines the words. Those definitions are definitely
technical, special definitions relating to Emacs, and are special in
Emacs. If you don't see, I cannot help, I see special technical
definitions that relate to Emacs.
Glossary is looked upon at any time. One cannot assume that a
hyperlinked info document is read in some order. Glossary shall
contain all terms and definitions used in the info to help an user
clarify the meanings.
If necessary, just as with other terms, it can point back or hyperlink
to various info sections.
Jean
next prev parent reply other threads:[~2020-09-26 20:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 17:06 bug#43633: 28.0.50; Include definitions in glossary for: extensible, customizable, self-documenting, real-time display editor Jean Louis
2020-09-26 17:16 ` Eli Zaretskii
2020-09-26 20:33 ` Jean Louis [this message]
2020-09-27 6:05 ` Eli Zaretskii
2020-09-27 2:42 ` Richard Stallman
2020-09-27 4:42 ` Jean Louis
2020-09-28 3:47 ` Richard Stallman
2020-09-28 4:57 ` Drew Adams
2020-09-30 11:15 ` Jean Louis
2020-09-30 18:50 ` Juri Linkov
2020-10-01 5:08 ` Jean Louis
2020-10-02 3:51 ` Richard Stallman
2020-09-28 6:32 ` Eli Zaretskii
2020-09-30 9:31 ` Jean Louis
2020-09-27 6:27 ` Eli Zaretskii
2020-09-28 3:44 ` Richard Stallman
2020-09-28 6:30 ` Eli Zaretskii
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=20200926203329.GA20474@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=43633@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).