[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fwd: REVIEW REQUEST - user manual generation
From: |
Gavin Smith |
Subject: |
Re: Fwd: REVIEW REQUEST - user manual generation |
Date: |
Mon, 13 Jun 2016 18:16:53 +0100 |
On 12 June 2016 at 18:09, Vincent Belaïche <address@hidden> wrote:
> Even simpler is the following:
>
> --8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8----
> in_input_funnies=`echo "$in_input" \
> | $SED -e 's![^}#$%&^_{~]!!g' -e 's!\(.\)!\1\''
> !g' | uniq`
> --8<----8<----8<----8<----8<-- end -->8---->8---->8---->8---->8----
>
> The trick is simply to add a tailing '' just before the newline, this
> does not change the content of the argument passed to sed, but prevents
> sh from seeing the sequence \NEWLINE.
Thanks a lot, it looks obvious when you see it.
>
> Anyway, I had to make another fix: you need to have the filename as an
> argument of its own, otherwise MSYS can't do its path name conversion
> ticks. After all, the whole thing about catcoding rather than explicit
> ecaping (ie replacing for instance '~' by '\string~') is to keep the
> filename unchanged.
>
> Attached is a patch with the two changes:
>
> - the passing \NEWLINE to sed stuff
>
> - making input filename an argument of its own.
Committed and uploaded!
- Re: Fwd: REVIEW REQUEST - user manual generation, (continued)
- Re: Fwd: REVIEW REQUEST - user manual generation, Vincent Belaïche, 2016/06/03
- Re: Fwd: REVIEW REQUEST - user manual generation, Vincent Belaïche, 2016/06/04
- Re: Fwd: REVIEW REQUEST - user manual generation, Vincent Belaïche, 2016/06/04
- Re: Fwd: REVIEW REQUEST - user manual generation, Gavin Smith, 2016/06/04
- Re: Fwd: REVIEW REQUEST - user manual generation, Vincent Belaïche, 2016/06/06
- Re: Fwd: REVIEW REQUEST - user manual generation, Vincent Belaïche, 2016/06/12
- Re: Fwd: REVIEW REQUEST - user manual generation,
Gavin Smith <=