From: Stephen Smith <ishchis2@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: SyntaxWarning for '\S'
Date: Fri, 13 Sep 2024 11:28:39 -0700 [thread overview]
Message-ID: <C7F37713-E65A-4200-A810-C71CFAA55926@gmail.com> (raw)
In-Reply-To: <ZuSDQPssBOujNCrF@tapette.crustytoothpaste.net>
Given that you don’t see it and that Ubuntu release is due a month from now I will see if it is part of the update. If the fix isn’t part of the update I will report it.
Thanks.
SPS
> On Sep 13, 2024, at 11:24 AM, brian m. carlson <sandals@crustytoothpaste.net> wrote:
>
> On 2024-09-10 at 03:49:33, Stephen Smith wrote:
>> When compiling Git from source on my Ubuntu machine I've lately been getting
>> some warnings when the docs are built.
>>
>> An example of is:
>>
>> ASCIIDOC git-sh-i18n--envsubst.html
>> <unknown>:1: SyntaxWarning: invalid escape sequence '\S'
>> <unknown>:1: SyntaxWarning: invalid escape sequence '\S'
>>
>> This syntax warning shows up for nearly every man page or html file.
>>
>> Is there are current documented solution? If there isn't a documented
>> solution, where do I start looking and I will craft a patch and submit it.
>
> I believe this is a warning from Python about the asciidoc program
> itself. I don't see this on my Debian unstable system, so it may be
> that it's fixed upstream (you can check at
> https://gitlab.com/asciidoc3/asciidoc3/) and if so, you can open an
> issue with Ubuntu to get it fixed.
>
> If it bothers you, you could also use Asciidoctor, which is written in
> Ruby, and which won't have that warning.
> --
> brian m. carlson (they/them or he/him)
> Toronto, Ontario, CA
> <signature.asc>
prev parent reply other threads:[~2024-09-13 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 3:49 SyntaxWarning for '\S' Stephen Smith
2024-09-13 18:24 ` brian m. carlson
2024-09-13 18:28 ` Stephen Smith [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=C7F37713-E65A-4200-A810-C71CFAA55926@gmail.com \
--to=ishchis2@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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.
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).