From: Matthew Wilcox <willy@infradead.org>
To: "Nícolas F. R. A. Prado" <nfraprado@protonmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
lkcamp@lists.libreplanetbr.org, andrealmeid@collabora.com
Subject: Re: [PATCH] docs: Make automarkup ready for Sphinx 3.1+
Date: Thu, 8 Oct 2020 00:40:24 +0100 [thread overview]
Message-ID: <20201007234024.GY20115@casper.infradead.org> (raw)
In-Reply-To: <20201007231214.326456-1-nfraprado@protonmail.com>
On Wed, Oct 07, 2020 at 11:12:25PM +0000, Nícolas F. R. A. Prado wrote:
> While Sphinx 2 used a single c:type role for struct, union, enum and
> typedef, Sphinx 3 uses a specific role for each one.
> To keep backward compatibility, detect the Sphinx version and use the
> correct roles for that version.
>
> Also, Sphinx 3 is more strict with its C domain and generated warnings,
> exposing issues in the parsing.
> To fix the warnings, make the C regexes use ASCII, ensure the
> expressions only match the beginning of words and skip trying to
> cross-reference C reserved words.
Thank you for doing this!
I have a feature request ... could you automarkup NULL as being :c:macro?
Or maybe just anything matching \<[[:upper:]_[:digit:]]*\>
(i may have my regex syntax confused ... a word composed of any
arrangement of upper-case, digits and underscores.)
next prev parent reply other threads:[~2020-10-07 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 23:12 [PATCH] docs: Make automarkup ready for Sphinx 3.1+ Nícolas F. R. A. Prado
2020-10-07 23:40 ` Matthew Wilcox [this message]
2020-10-08 5:27 ` Mauro Carvalho Chehab
2020-10-08 2:15 Nícolas F. R. A. Prado
2020-10-08 2:47 ` Matthew Wilcox
2020-10-08 6:03 ` Mauro Carvalho Chehab
2020-10-08 11:31 ` Matthew Wilcox
2020-10-08 12:25 ` Mauro Carvalho Chehab
2020-10-08 13:54 Nícolas F. R. A. Prado
2020-10-09 5:53 ` Mauro Carvalho Chehab
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=20201007234024.GY20115@casper.infradead.org \
--to=willy@infradead.org \
--cc=andrealmeid@collabora.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=mchehab+huawei@kernel.org \
--cc=nfraprado@protonmail.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 NNTP newsgroup(s).