Re: escaped blanks on command line

On Thu, 02 Nov 2006 17:19:00 +0100
Denis Prost <denis.prost@xxxxxxxxxx> wrote:

> I just met one problem with filemanes containing blanks : when I select 
> one of them in one file pane, then press Control+Enter to paste it on 
> the command line, the blanks in the filename appear escaped with "\ ". 
> That should be fine, but unfortunately, it seems that "\ " is not 
> properly handled by the command line. For example :
> oowriter my\ file.odt
> will make oowriter try to open two files "my" and "file.odt".
Un-escaping of command whitespace has now been revised to deal with this.

Do all apps properly handle command parameter(s) with escaped whitespace ?

Regards
Tom


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: