From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Major and minor modes
Date: Thu, 15 Jun 2017 18:05:36 +0300 [thread overview]
Message-ID: <83bmpp2svz.fsf@gnu.org> (raw)
In-Reply-To: <41AE1409-13B6-404F-BE28-FE43D482360B@gmail.com> (message from Jean-Christophe Helary on Thu, 15 Jun 2017 06:58:07 +0900)
> From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
> Date: Thu, 15 Jun 2017 06:58:07 +0900
>
> PDF Chapter 2 "Characters, Keys and Commands" has:
> [introductory text about the chapter]
> 2.1 Kinds of User Input
> 2.2 Keys
> 2.3 Keys and Commands
>
> but the HTML has:
> • 2 Kinds of User Input
> • 3 Keys
> • 4 Keys and Commands
Ah, that... It's because the manual does this:
@ifnottex
@raisesections
@end ifnottex
So when you later have this:
@node User Input
@section Kinds of User Input
The @section gets rendered as a chapter in on-line formats (Info and
HTML), and as a section in printed formats.
IOW, a book requires somewhat different considerations wrt its
sectioning than an on-line version of the manual.
> So in the HTML, PDF sub-chapters are chapters on their own and the introductory text is not present:
> "This chapter explains the character sets used by Emacs for input commands, and the fundamental concepts of keys and commands, whereby Emacs interprets your keyboard and mouse input."
That introductory text is conditionally included only in the printed
formats:
@iftex
@chapter Characters, Keys and Commands
This chapter explains the character sets used by Emacs for input
commands, and the fundamental concepts of @dfn{keys} and
@dfn{commands}, whereby Emacs interprets your keyboard and mouse
input.
@end iftex
> Then PDF has:
> 32 Emacs Lisp Packages................................. 431
> 33 Customization ...................................... 436
> 34 Dealing with Common Problems ....................... 468
>
> And that chapter 34 corresponds to HTML
> • 52 Quitting and Aborting
> • 53 Dealing with Emacs Trouble
> • 54 Reporting Bugs
> • 55 Contributing to Emacs Development
> • 56 How To Get Help with GNU Emacs
>
> That discrepancy is a bit weird.
Is it still weird?
next prev parent reply other threads:[~2017-06-15 15:05 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 [this message]
2017-06-15 15:16 ` Drew Adams
2017-06-16 2:09 ` Jean-Christophe Helary
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bmpp2svz.fsf@gnu.org \
--to=eliz@gnu.org \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.