From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.tui/resize-3.exp on ppc64-linux
Date: Fri, 17 Oct 2025 08:14:19 -0600 [thread overview]
Message-ID: <87cy6lr4xw.fsf@tromey.com> (raw)
In-Reply-To: <20251017133957.2464782-1-tdevries@suse.de> (Tom de Vries's message of "Fri, 17 Oct 2025 15:39:57 +0200")
Tom> - "$hex\\s+<foo"
Tom> + [string cat $hex {\s+} "<" ([string_to_regexp .])? "foo"]
Personally I find this a lot less readable than just writing out the
regular expression.
Tom
next prev parent reply other threads:[~2025-10-17 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 13:39 Tom de Vries
2025-10-17 14:14 ` Tom Tromey [this message]
2025-10-18 8:21 ` Tom de Vries
2025-10-18 9:11 ` Tom de Vries
2025-10-18 17:19 ` Tom Tromey
2025-10-20 10:08 ` Tom de Vries
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=87cy6lr4xw.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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