From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Major and minor modes
Date: Fri, 16 Jun 2017 11:09:18 +0900 [thread overview]
Message-ID: <C9DE584C-D519-4BAF-BB88-6D6F9F3FD669@gmail.com> (raw)
In-Reply-To: <1750a088-5dfd-4aba-8d45-1e013f587ed7@default>
>> IOW, a book requires somewhat different considerations wrt its
>> sectioning than an on-line version of the manual.
>>
>>> That discrepancy is a bit weird.
>>
>> Is it still weird?
Yes, and I have the exact same opinion as Drew on this one.
There are no logical reasons why a part of the manual would be a chapter on its own in one version and a sub chapter in a different version.
Shall we move this discussion to emacs-devel ?
> But section numbers, like section names, are not just content.
> They are navigational. They are used for reference, including
> as was the case in this thread: someone pointing to a particular
> section by name or number.
>
> [Yes, a _link_ to a section in an online manual is often
> preferable to such a purely textual representation. But that
> is not a reason why the section numbers or names should differ.]
>
> As with everything, there might be exceptions. But what was
> shown here does not seem like a good candidate for being an
> exception.
Jean-Christophe
next prev parent reply other threads:[~2017-06-16 2:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 23:58 Major and minor modes M.R.P.
2017-06-14 0:43 ` Jean-Christophe Helary
2017-06-14 1:49 ` Drew Adams
2017-06-14 3:49 ` Jean-Christophe Helary
2017-06-14 3:59 ` Emanuel Berg
2017-06-15 4:58 ` Marcin Borkowski
2017-06-14 14:23 ` Eli Zaretskii
2017-06-14 21:58 ` Jean-Christophe Helary
2017-06-14 23:10 ` Jean-Christophe Helary
2017-06-15 13:33 ` Emanuel Berg
2017-06-15 15:05 ` Eli Zaretskii
2017-06-15 15:16 ` Drew Adams
2017-06-16 2:09 ` Jean-Christophe Helary [this message]
2017-06-16 3:07 ` Drew Adams
2017-06-16 4:44 ` Emanuel Berg
2017-06-16 5:13 ` Jean-Christophe Helary
2017-06-16 5:26 ` Emanuel Berg
2017-06-16 6:59 ` Eli Zaretskii
2017-06-16 8:02 ` Jean-Christophe Helary
2017-06-16 4:34 ` Emanuel Berg
2017-06-14 4:05 ` Emanuel Berg
2017-06-17 14:08 ` Narendra Joshi
2017-06-19 4:43 ` Krishnakant
2017-06-14 6:21 ` Krishnakant
2017-06-14 7:37 ` Phillip Lord
2017-06-14 1:54 ` Emanuel Berg
2017-06-14 7:40 ` Héctor Lahoz
2017-06-14 8:19 ` Emanuel Berg
2017-06-14 8:51 ` tomas
2017-06-14 9:25 ` Emanuel Berg
2017-06-14 9:36 ` Emanuel Berg
2017-06-14 9:58 ` tomas
2017-06-14 10:43 ` Emanuel Berg
2017-06-14 11:39 ` Emanuel Berg
2017-06-14 11:48 ` Emanuel Berg
2017-06-14 12:19 ` tomas
2017-06-14 14:15 ` Barry Margolin
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=C9DE584C-D519-4BAF-BB88-6D6F9F3FD669@gmail.com \
--to=jean.christophe.helary@gmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).