Re: Whitespace On The Command Line
"Greg Edwards" <[email protected]>
| Newsgroups | gmane.editors.nedit.user |
|---|---|
| Message-ID | <[email protected]> |
Carlo, Sounds like an issue purely in your shell level, nedit is fine with spaces. See attached pic of nedit junk\ junk -xrm "*.background: red" (This is in bash on MacOS 10.5) What m/c and os and shell are you on ? Can you do other things with filenames incl. spaces ? ls > 'junk junk' ? Ok, world's oldest Unix trivia question, while we're on this sort of thing .. Try ls > -t Then try to rm the file you created. Greg E 2008/5/2 Carlo Graziani <[email protected]>: > Hi Nediters. > > I can't seem to get the nedit command-line to parse arguments with > whitespace properly. For example, a filename like 'foo foo' cannot > be picked up by invocations like > > %> nedit 'foo foo' > %> nedit foo\ foo > %> nedit "foo foo" > %> nedit 'foo\ foo' > > and so on. No combination of quoting and escaping that I've tried > seems to work. The file menu has no trouble with displaying and > selecting the file, but all the above command-line invocations > result in failed stats on files with names like 'foo' or 'foo\'. > > It's not just filenames. I couldn't get the -xrm option to work > with a resource string containing whitespace either, despite the > same flailing about with escaping and quoting. > > So is there a work-around for this? > > Thanks, > > Carlo > > -- > Carlo Graziani (773) 702-7973 (Voice) > Department of Astronomy and Astrophysics (773) 702-6645 (FAX) > University of Chicago > 5640 South Ellis Avenue | If the free market really allocates > resources > Chicago, IL 60637 | efficiently, why does LA have four times as > [email protected] | many plastic surgeons as brain surgeons? > > > -- > NEdit Discuss mailing list - [email protected] > http://www.nedit.org/mailman/listinfo/discuss > -- Greg Edwards mob 0400 102 774 -- NEdit Discuss mailing list - [email protected] http://www.nedit.org/mailman/listinfo/discuss