All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Manuel Ebner <manuelebnerli@mailbox.org>
Cc: Jonathan Corbet <corbet@lwn.net>, Weijie Yuan <wy@wyuan.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Shuah Khan  <skhan@linuxfoundation.org>,
	"open list:DOCUMENTATION PROCESS"  <workflows@vger.kernel.org>,
	"open list:DOCUMENTATION"  <linux-doc@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [Issue] sphinx: incorrect high-lighting
Date: Thu, 3 Sep 2026 17:30:34 +0200	[thread overview]
Message-ID: <20260903173034.46b50b59@localhost> (raw)
In-Reply-To: <f0ccda934d2747f7d39d5c263116ec046c7450e2.camel@mailbox.org>

On Sun, 30 Aug 2026 09:13:31 +0200
Manuel Ebner <manuelebnerli@mailbox.org> wrote:

> On Mon, 2026-08-24 at 07:26 -0600, Jonathan Corbet wrote:
> > Manuel Ebner <manuelebnerli@mailbox.org> writes:
> >   
> > > It would be this list:
> > > Skipidentifiers = [ 'and', 'are', 'as', 'containing', 'element', 'in',
> > >                     'including', 'is', 'name', 'needs', 'of', 'or',  'page',
> > >                     'pages', 'passed', 'randomization', 'request', 'that',
> > >                     'to', 'where', 'which', 'whose', 'will' ]  
> > 
> > So this is an error-prone game of whac-a-mole...as Randy pointed out,
> > "struct page" is a rather important one in the kernel.
> > 
> > I can apply your updated version of this as a short-term fix, I guess,
> > but a better solution is probably to only apply markup to "struct foo"
> > if we have documentation for that type.  I can look into that later.  

There is actually a way to do that. See
Documentation/sphinx/kernel_include.py the code related to this:

    app.connect("missing-reference", check_missing_refs)

One option would be to re-convert such missing references back into
a normal "struct foo" if the reference was not found.

Not sure, however, how much this would affect Sphinx build time.

-- 
Thanks,
Mauro

      reply	other threads:[~2026-09-03 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 15:14 [Issue] sphinx: incorrect high-lighting Manuel Ebner
2026-08-23 15:57 ` Weijie Yuan
2026-08-23 18:08   ` Manuel Ebner
2026-08-23 18:47     ` Randy Dunlap
2026-08-24 13:26     ` Jonathan Corbet
2026-08-30  7:13       ` Manuel Ebner
2026-09-03 15:30         ` Mauro Carvalho Chehab [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260903173034.46b50b59@localhost \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuelebnerli@mailbox.org \
    --cc=mchehab@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@vger.kernel.org \
    --cc=wy@wyuan.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.