[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63.
|
From: |
Collin Funk |
|
Subject: |
[PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63. |
|
Date: |
Sun, 17 Mar 2024 15:03:17 -0700 |
|
User-agent: |
Mozilla Thunderbird |
This patch is just one added function. Can you double check that I
understood your 'sed' wizardry correctly Bruno?
I read the GNU sed info page a bit, but I could have missed something.
My normal usage of sed is using 's/pattern/replacement/g' and hoping
that it doesn't break too much. :)
I placed the sed command and a modified version of my Python function in
two scripts and compared their output using 'modules/stdio'. They
produced the same output.
The cleansed.append('') call seemed to make them output the same
number of newlines. It looks a bit strange, but that is my reasoning
for it
Collin
0001-gnulib-tool.py-Follow-gnulib-tool-changes-part-63.patch
Description: Text Data
- [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63.,
Collin Funk <=
- Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63., Bruno Haible, 2024/03/17
- Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63., Basil L. Contovounesios, 2024/03/17
- Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63., Collin Funk, 2024/03/17
- Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63., Bruno Haible, 2024/03/17
- Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63., Collin Funk, 2024/03/17
- Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63., Bruno Haible, 2024/03/17
- Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63., Collin Funk, 2024/03/17
- Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63., Bruno Haible, 2024/03/17
- Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 63., Collin Funk, 2024/03/17