From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] docparse/parse.sh: Fix parsing on dash
Date: Thu, 17 Dec 2020 13:36:15 +0100 [thread overview]
Message-ID: <X9tQv3da2WftcH0z@pevik> (raw)
In-Reply-To: <X9tNEoMlQsCaSZPD@yuki.lan>
> Hi!
> > bash keeps escape sequences (e.g. \t and \n) when using echo:
> > $ a="-v\tverbose output\n"; echo "$a"
> > -v\tverbose output\n
> > $
> > But dash interprets them (behaves like echo -e on bash):
> > $ a="-v\tverbose output\n"; echo -e "$a"
> > -e -v verbose output
> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
Thanks for both reviews!
> Can we remove the \t from the perf_event_open02.c as well please? I
> doubt that it will do any good when we pass the strings into asciidoc
> parser...
Sure, I'll replace it with <tab>.
Kind regards,
Petr
next prev parent reply other threads:[~2020-12-17 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 12:15 [LTP] [PATCH 0/2] Travis build fixes Petr Vorel
2020-12-17 12:15 ` [LTP] [PATCH 1/2] docparse/parse.sh: Fix parsing on dash Petr Vorel
2020-12-17 12:20 ` Cyril Hrubis
2020-12-17 12:36 ` Petr Vorel [this message]
2020-12-17 12:58 ` Petr Vorel
2020-12-17 12:15 ` [LTP] [PATCH 2/2] docparse/parse.sh: Fix running with relative path Petr Vorel
2020-12-17 12:22 ` Cyril Hrubis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X9tQv3da2WftcH0z@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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