[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (gnu)sed in texinfo
From: |
Mihai Moldovan |
Subject: |
Re: (gnu)sed in texinfo |
Date: |
Sat, 05 Jul 2014 05:33:48 +0200 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
* On 05.07.2014 01:59 am, Mihai Moldovan wrote:
> * On 05.07.2014 01:35 am, Karl Berry wrote:
>> If you comment out the call to run_recode(), does it solve your problem?
>> (Please don't educate me about how this doesn't deal with the "real"
>> issue. :)
> I'll check that. There may be more invocations of sed failing, so I can not
> give
> a clear answer without testing. Will reply later.
Not executing run_recode() seems to work fine with the input file/for the
failure I experienced.
In general, removing run_recode() and friends seems to fix the issue just fine,
other code running sed on input files are, is far as I could see, not parsing
the texi input file but other intermediate files.
Despite of this, I still believe making sed configurable at build time would
help counter such issues in a nice and clean way. I'm just thinking about new
code added in the future.
Mihai
smime.p7s
Description: S/MIME Cryptographic Signature
- Re: (gnu)sed in texinfo, Mihai Moldovan, 2014/07/04
- Re: (gnu)sed in texinfo, Mojca Miklavec, 2014/07/04
- Re: (gnu)sed in texinfo, Mihai Moldovan, 2014/07/04
- Re: (gnu)sed in texinfo, Karl Berry, 2014/07/04
- Re: (gnu)sed in texinfo, Mihai Moldovan, 2014/07/04
- Re: (gnu)sed in texinfo,
Mihai Moldovan <=
- Re: (gnu)sed in texinfo, Karl Berry, 2014/07/07
- Re: (gnu)sed in texinfo, Mihai Moldovan, 2014/07/07
- Re: (gnu)sed in texinfo, Mojca Miklavec, 2014/07/08