From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: Re: master 930c578c104: ; Improvements to PEG documentation
Date: Tue, 16 Apr 2024 12:00:08 +0200 [thread overview]
Message-ID: <87le5dmxuf.fsf@gmx.de> (raw)
In-Reply-To: <20240416031700.9D2B1C1FB45@vcs2.savannah.gnu.org> (Eric Abrahamsen's message of "Mon, 15 Apr 2024 23:17:00 -0400 (EDT)")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
Hi Eric,
> doc/lispref/peg.texi | 128 +++++++++++++++++---------------------------------
> lisp/progmodes/peg.el | 7 +--
> 2 files changed, 48 insertions(+), 87 deletions(-)
>
> diff --git a/doc/lispref/peg.texi b/doc/lispref/peg.texi
> index fbf57852ee0..90aa76988db 100644
> --- a/doc/lispref/peg.texi
> +++ b/doc/lispref/peg.texi
> @@ -1,78 +1,31 @@
> -@c -*-texinfo-*-
> -@c This is part of the GNU Emacs Lisp Reference Manual.
> -@c Copyright (C) 1990--1995, 1998--1999, 2001--2023 Free Software
> -@c Foundation, Inc.
> -@c See the file elisp.texi for copying conditions.
> -@node Parsing Expression Grammars
> -@chapter Parsing Expression Grammars
> -@cindex text parsing
> -@cindex parsing expression grammar
> -@cindex PEG
...
It looks, like the beginning of peg.texi has been removed accidently.
Best regards, Michael.
next parent reply other threads:[~2024-04-16 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171323742013.5283.3736155251539337632@vcs2.savannah.gnu.org>
[not found] ` <20240416031700.9D2B1C1FB45@vcs2.savannah.gnu.org>
2024-04-16 10:00 ` Michael Albinus [this message]
2024-04-16 10:05 ` master 930c578c104: ; Improvements to PEG documentation Mattias Engdegård
2024-04-17 0:33 ` Eric Abrahamsen
2024-04-17 2:38 ` Michael Heerdegen via Emacs development discussions.
2024-04-17 3:54 ` Eric Abrahamsen
2024-04-19 23:28 ` Eric Abrahamsen
2024-04-20 23:39 ` Michael Heerdegen via Emacs development discussions.
2024-04-21 0:51 ` Eric Abrahamsen
2024-04-17 12:26 ` 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=87le5dmxuf.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).