|
| From: | Eric Blake |
| Subject: | Re: How to deal with space in command line? |
| Date: | Mon, 20 Sep 2010 07:56:35 -0600 |
| User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100907 Fedora/3.1.3-1.fc13 Mnenhy/0.8.3 Thunderbird/3.1.3 |
On 09/20/2010 07:14 AM, Greg Wooledge wrote:
... which uses three bash extensions and one BSD/GNU extension. To the best of my knowledge, the task is completely impossible in strict POSIX.
Impossible in strict POSIX 2008. But the Austin Group (the people that develop the POSIX standard) is actively working on proposals to enhance the next revision of POSIX that will make it easier to deal with awkward file names; the proposals on the floor include (among others): mandating support for $'...', requiring that compliant file systems reject \n in newly-created file names, and adding an environment variable to make it easier to detect when you are dealing with existing file systems with \n already in an existing file name. Help in reviewing and contributing to these proposals will be most welcome.
-- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
| [Prev in Thread] | Current Thread | [Next in Thread] |