From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <7359f0490810220809n1c7d3493r1b0bbf629986c057@mail.gmail.com> Date: Wed, 22 Oct 2008 08:09:13 -0700 From: "Rob Pike" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <70118626f929a241ac21312138418a94@quintile.net> Subject: Re: [9fans] sam & filenames containing whitespace Topicbox-Message-UUID: 24c23070-ead4-11e9-9d60-3106f5b1d025 Sam cannot handle file names with spaces. There is one way to work around this that I can think of without renaming the file. Make a new buffer with nothing in it. ("B " without the quotes is how you do that.) Then cat > 'a b' Clunky but so be it. Sam comes from a system where spaces in file names made no sense. -rob On Wed, Oct 22, 2008 at 5:55 AM, Rudolf Sykora wrote: > 2008/10/15 Steve Simon : >> Hi, >> >> I am trying to work with files containing whitespace, >> many programs in plan9 are happy with this but sam and B >> don't appear to be (unless I have broken somthing). >> >> I can fix the buglet in B (some string flattening) but >> a cursory look at the sam source and it seems to support >> delimiters in commands (e.g. B "file with spaces in it.txt"). >> >> however I cannot open files with whitespace in their names >> even if it type them in in the sam command windows. >> >> am I missing somthing or is this a real bug? >> >> -Steve >> > > So does anybody know? I don't. :( > Ruda > >