From: Luis Felipe via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 62872@debbugs.gnu.org
Subject: bug#62872: doc: Texinfo Processing: Indicate which version(s) of Texinfo are supported
Date: Sat, 15 Apr 2023 20:55:09 +0000 [thread overview]
Message-ID: <19e4f6b0-7b98-984b-4dd3-67f9bab160a8@zoho.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 716 bytes --]
Hi,
Guile's documentation on Texinfo Processing doesn't seem to mention that
the Texinfo format is *partially supported* or whether a particular
version or versions of the format are supported.
Processing documents written in Texinfo 6.x and 7.x, I found that some
commands lead to parsing errors like the one reported recently in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62374. The following
commands, for example, lead to the error:
+ @abbr
+ @alias
+ @macro
I think the manual should clarify this so that users can more easily
decide whether the current Texinfo modules are enough for their projects.
Cheers,
--
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
reply other threads:[~2023-04-15 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19e4f6b0-7b98-984b-4dd3-67f9bab160a8@zoho.com \
--to=bug-guile@gnu.org \
--cc=62872@debbugs.gnu.org \
--cc=sirgazil@zoho.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.
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).