From: Tomi Ollila <tomi.ollila@iki.fi>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: [PATCH v3] test: replace notmuch_passwd_sanitize() with _libconfig_sanitize()
Date: Thu, 20 May 2021 10:43:35 +0300 [thread overview]
Message-ID: <m2fsyhono8.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <CAMP44s3-7vh+wTR9NwAf5qNqhjEEgwKprV-DOKSSarvhjx6sXw@mail.gmail.com>
On Wed, May 19 2021, Felipe Contreras wrote:
> On Wed, May 19, 2021 at 12:34 PM Tomi Ollila <tomi.ollila@iki.fi> wrote:
>
>> Haha, as we do _libconfig_sanitize < OUTPUT > OUTPUT.clean
>> reading python script from stdin don't work (perl has __DATA__ ;).
>> (bitten again, I did and tested the change... :D).
>
> That can be fixed with:
>
> python /dev/fd/3 3<<EOF
> EOF
According to
https://unix.stackexchange.com/questions/123602/portability-of-file-descriptor-links
that solution could be portable enough.
Another way still using -c ... I've played to look how it actually looks is
(diff since patch v3)
- sq = chr(39) # single quote
- l = l.replace(sq + name, sq + "USER_FULL_NAME", 1)
+ l = l.replace("'\''" + name, "'\''USER_FULL_NAME", 1)
Tested the above. That python /dev/fd/3 3<<EOF is so neat it at least
have to be tested to see how it looks like and behaves... :D
>
> --
> Felipe Contreras
Tomi
next prev parent reply other threads:[~2021-05-20 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 5:54 [PATCH v3] test: replace notmuch_passwd_sanitize() with _libconfig_sanitize() Tomi Ollila
2021-05-19 7:29 ` Felipe Contreras
2021-05-19 8:44 ` Tomi Ollila
2021-05-19 17:34 ` Tomi Ollila
2021-05-19 19:51 ` Felipe Contreras
2021-05-20 7:43 ` Tomi Ollila [this message]
2021-05-21 9:46 ` Felipe Contreras
2021-05-21 18:22 ` Tomi Ollila
2021-05-24 2:34 ` Felipe Contreras
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2fsyhono8.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=felipe.contreras@gmail.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).