From: Collin Funk <collin.funk1@gmail.com>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: [PATCH] gnulib-tool.py: Fix configure.ac output.
Date: Tue, 27 Feb 2024 16:04:09 -0800 [thread overview]
Message-ID: <cab55f31-648f-4f7d-8162-65c64b29c816@gmail.com> (raw)
In-Reply-To: <6284451.Sgy9Pd6rRy@nimes>
On 2/27/24 3:39 PM, Bruno Haible wrote:
> $ pycodestyle *.py
> ...
> GLEmiter.py:535:26: W605 invalid escape sequence '\.'
> GLEmiter.py:535:35: W605 invalid escape sequence '\.'
> ...
I discovered it that way too. I like using Eglot from Emacs though. If
you are using Emacs 29+ the `eglot' command should be built-in. In
that case in the following line:
sed_drop_objext='s/\.o$//;s/\.obj$//'
The '\.o$//;s/\.obj$//' part will be crossed out. Not sure if that is
your perfected way of doing things but I find it useful so I figured
I'd mention it. :)
Collin
prev parent reply other threads:[~2024-02-28 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 22:31 [PATCH] gnulib-tool.py: Fix configure.ac output Collin Funk
2024-02-27 22:39 ` Bruno Haible
2024-02-27 23:01 ` Collin Funk
2024-02-27 23:39 ` Bruno Haible
2024-02-28 0:04 ` Collin Funk [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cab55f31-648f-4f7d-8162-65c64b29c816@gmail.com \
--to=collin.funk1@gmail.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).