unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Marco Antoniotti <marcoxa@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66680@debbugs.gnu.org
Subject: bug#66680: PDF version of Elisp manual is missing section about 'rx' regexp format
Date: Sun, 22 Oct 2023 15:25:04 +0200	[thread overview]
Message-ID: <CAKmY7cUuLOuycuZs-Oo0S0BfvbhGT=LMLqdo4emTi+zHTfDrJA@mail.gmail.com> (raw)
In-Reply-To: <83il6ypz9d.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 785 bytes --]

Thanks.

A bit confusing though...  Time to re-evaluate this choice?

MA


On Sun, Oct 22, 2023 at 3:23 PM Eli Zaretskii <eliz@gnu.org> wrote:

> tags 66680 notabug
> thanks
>
> > From: Marco Antoniotti <marcoxa@gmail.com>
> > Date: Sun, 22 Oct 2023 14:55:47 +0200
> >
> > 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
>
> This is on purpose: the Rx section is excluded from the printed
> manual, to keep the printed manual's size at bay.  Several other
> sections are also excluded.
>
> This is not a bug.
>


-- 
Marco Antoniotti
Somewhere over the Rainbow

[-- Attachment #2: Type: text/html, Size: 1460 bytes --]

  reply	other threads:[~2023-10-22 13:25 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 [this message]
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

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='CAKmY7cUuLOuycuZs-Oo0S0BfvbhGT=LMLqdo4emTi+zHTfDrJA@mail.gmail.com' \
    --to=marcoxa@gmail.com \
    --cc=66680@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).