9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Rob Pike" <robpike@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] sam & filenames containing whitespace
Date: Wed, 22 Oct 2008 08:09:13 -0700	[thread overview]
Message-ID: <7359f0490810220809n1c7d3493r1b0bbf629986c057@mail.gmail.com> (raw)
In-Reply-To: <a560a5d00810220555g7301eb5auf34141b4d583f79c@mail.gmail.com>

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'
edit
,>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 <rudolf.sykora@gmail.com> wrote:
> 2008/10/15 Steve Simon <steve@quintile.net>:
>> 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
>
>



  reply	other threads:[~2008-10-22 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 12:25 Steve Simon
2008-10-22 12:53 ` Rudolf Sykora
2008-10-22 12:55 ` Rudolf Sykora
2008-10-22 15:09   ` Rob Pike [this message]
2008-10-22 15:29     ` Gorka Guardiola

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=7359f0490810220809n1c7d3493r1b0bbf629986c057@mail.gmail.com \
    --to=robpike@gmail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).