From: Karel Zak <kzak@redhat.com>
To: "Pádraig Brady" <P@draigBrady.com>
Cc: util-linux@vger.kernel.org
Subject: Re: suggestion to avoid erroneous lines in findmnt/lslocks/...
Date: Tue, 7 Aug 2012 10:09:39 +0200 [thread overview]
Message-ID: <20120807080939.GF24621@x2.net.home> (raw)
In-Reply-To: <501FD845.50001@draigBrady.com>
On Mon, Aug 06, 2012 at 03:44:21PM +0100, Pádraig Brady wrote:
> I did a quick test...
Thanks, I'll use it in regression tests ;-) (I was busy yesterday to
write any reg.tests.)
> TARGET SOURCE FSTYPE OPTIONS
> /home/padraig/tst/ascii /dev/loop1 ext2 rw,relatime,seclabel,errors=continue
> /home/padraig/tst/ascii
> TARGET SOURCE FSTYPE OPTIONS
> /home/padraig/tst/co\x0atrol /dev/loop1 ext2 rw,relatime,seclabel,errors=continue
> /home/padraig/tst/co\x0atrol
> TARGET SOURCE FSTYPE OPTIONS
> /home/padraig/tst/back\slash /dev/loop1 ext2 rw,relatime,seclabel,errors=continue
> /home/padraig/tst/back\slash
> TARGET SOURCE FSTYPE OPTIONS
> /home/padraig/tst/es\x63aped /dev/loop1 ext2 rw,relatime,seclabel,errors=continue
> /home/padraig/tst/es\x5cx63aped
> TARGET SOURCE FSTYPE OPTIONS
>
> /dev/loop1 ext2 rw,relatime,seclabel,errors=continue
> /home/padraig/tst/non\xfffffffatf8
> TARGET SOURCE FSTYPE OPTIONS
> /home/padraig/tst/日一二三四五六 /dev/loop1 ext2 rw,relatime,seclabel,errors=continue
> /home/padraig/tst/\xffffffe6\xffffff97...
>
> So two questions.
>
> 1. Should the back\slash case be back\x5cslash in both cases?
back\slash is not \x<xdigit> sequence, so escape is unnecessary
Note that \\server\path is pretty common for cifs and use \x5c
for all '\' will make the findmnt output unreadable in many cases.
IMHO is better to be "smart" and use escape sequences only when it's
really necessary.
> 2. The nonútf8 one produces an errant new line.
> Also in this case could you fall back to using \x escapes for the whole string?
Yeah, nonútf8 output seems strange, I'll fix it.
I'll also update findmnt (and others) man pages to explain when and
how we use \x escapes. Is there any elegant way how to convert \x
sequences back to the native strings in shell? Maybe we can add some
hint to the man pages too.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-08-07 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 15:42 suggestion to avoid erroneous lines in findmnt/lslocks/ Pádraig Brady
2012-08-04 15:57 ` Dave Reisner
2012-08-05 2:02 ` Pádraig Brady
2012-08-06 8:15 ` Karel Zak
2012-08-06 11:10 ` Karel Zak
2012-08-06 14:44 ` Pádraig Brady
2012-08-07 8:09 ` Karel Zak [this message]
2012-08-07 11:35 ` Dave Reisner
2012-08-07 23:36 ` Pádraig Brady
2012-08-13 12:39 ` Karel Zak
2012-08-20 0:31 ` Pádraig Brady
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=20120807080939.GF24621@x2.net.home \
--to=kzak@redhat.com \
--cc=P@draigBrady.com \
--cc=util-linux@vger.kernel.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.
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 NNTP newsgroup(s).