Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: k4lizen <k4lizen@proton.me>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH]  [gdb/docs] use a clearer example for gdb lexing
Date: Tue, 29 Sep 2026 08:33:28 +0300	[thread overview]
Message-ID: <86qzic1v13.fsf@gnu.org> (raw)
In-Reply-To: <JjReHsyUaIf9SKN2vDhyWrBGwFeVxKsYv9ACUvo7xa2Y5btUQPuB9Gl1VJb-Dln7HJc1pPFNixu7zn0drwF11Dl_CcgG-PPfPcZeIgSUWYE=@proton.me> (message from k4lizen on Mon, 28 Sep 2026 23:21:40 +0000)

> Date: Mon, 28 Sep 2026 23:21:40 +0000
> From: k4lizen <k4lizen@proton.me>
> 
> The old one raised a SyntaxWarning, and this one
> allows the reader to focus on the GDB lexing
> without having to think about what python is
> doing.

Thanks.  Is the new variant you suggest supported by all the versions
of Python we currently support?

Also, I think this should be reviewed by someone who knows Python
better than I do (which is close to nothing), because this is not just
a documentation issue.

The patch is okay Texinfo-wise.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

      reply	other threads:[~2026-09-29  5:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 23:21 k4lizen
2026-09-29  5:33 ` Eli Zaretskii [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=86qzic1v13.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=k4lizen@proton.me \
    /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