unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Marco Antoniotti <marcoxa@gmail.com>
Cc: 66680-done@debbugs.gnu.org
Subject: bug#66680: PDF version of Elisp manual is missing section about 'rx' regexp format
Date: Sun, 22 Oct 2023 15:28:49 +0200	[thread overview]
Message-ID: <87il6yss4u.fsf@gmx.de> (raw)
In-Reply-To: <CAKmY7cW5F11DmG_jeNd9Zw6Brqd2cR+_bsXi6+JGYf4QH3U0qw@mail.gmail.com> (Marco Antoniotti's message of "Sun, 22 Oct 2023 14:55:47 +0200")

Marco Antoniotti <marcoxa@gmail.com> writes:

> Hi

Hi Marco,

> I noted this glitch since 28.x.  Still there in 29.x.
>
> HTML version has the section on 'rx' regexps coding, but it is missing
> from the PDFs downloadable from the main site
> https://www.gnu.org/software/emacs/manual/emacs.html

The section about "Rx Notation" in doc/lispref/searching.texi is embedded with

--8<---------------cut here---------------start------------->8---
@ifnottex
@node Rx Notation
@subsection The @code{rx} Structured Regexp Notation
...
@end ifnottex
--8<---------------cut here---------------end--------------->8---

The commit message of ac1ad3e49abd, which brought it to the manual,
claims

--8<---------------cut here---------------start------------->8---
    The additions are excluded from the print version to avoid making it
    thicker.
--8<---------------cut here---------------end--------------->8---

So it isn't a bug. Closing.

> All the best

Best regards, Michael.





      parent reply	other threads:[~2023-10-22 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 12:55 bug#66680: PDF version of Elisp manual is missing section about 'rx' regexp format Marco Antoniotti
2023-10-22 13:23 ` Eli Zaretskii
2023-10-22 13:25   ` Marco Antoniotti
2023-10-22 14:05     ` Eli Zaretskii
2023-10-22 16:58       ` Marco Antoniotti
2023-10-22 17:42         ` Eli Zaretskii
2023-10-22 18:34           ` Marco Antoniotti
2023-10-22 13:28 ` Michael Albinus [this message]

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=87il6yss4u.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=66680-done@debbugs.gnu.org \
    --cc=marcoxa@gmail.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).