From: Karel Zak <kzak@redhat.com>
To: util-linux@vger.kernel.org
Subject: Re: findmnt: parsing mountpoints with spaces
Date: Tue, 24 Apr 2012 19:52:50 +0200 [thread overview]
Message-ID: <20120424175250.GC17370@x2.net.home> (raw)
In-Reply-To: <20120424144055.GB3813@magazyn-ziarno.zbozowa>
On Tue, Apr 24, 2012 at 04:40:55PM +0200, Marcin Szewczyk wrote:
> Hi,
>
> is there a way to make findmnt print unambiguous output in case of block
> devices/directories/mountpoints whose names contain spaces? I can see
> that --raw makes findmnt print undecorated output, but spaces remain not
> escaped.
>
> May I request a feature of escaping spaces and possibly other
> non-printable characters in a fstab manner (\040 for space)?
Good point, I have already added this to lsblk for LABELs in parsable
output, it seems that we need this for mountpoint and findmnt too.
Added to my TODO. Thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-04-24 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 14:40 findmnt: parsing mountpoints with spaces Marcin Szewczyk
2012-04-24 17:52 ` Karel Zak [this message]
2012-04-24 17:55 ` Marcin Szewczyk
2012-04-26 7:32 ` Karel Zak
2012-04-26 7:48 ` Marcin Szewczyk
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=20120424175250.GC17370@x2.net.home \
--to=kzak@redhat.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