From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200205301621.g4UGLES02271@zamenhof.cs.utwente.nl>
To: 9fans@cse.psu.edu
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [9fans] spaces in file/dir names? (and acme)?
Date: Thu, 30 May 2002 18:21:14 +0200
Topicbox-Message-UUID: a012e1fc-eaca-11e9-9e20-41e7f4b1d025

Can acme not deal with spaces in file names?

I was trying aplay on a directory of directories of mp3's,
mounted via u9fs.
Both the mp3 files and the directories that contain them contain
spaces in their names. When I open acme in such a directory,
the tag contains the directory name upto the first space,
but the body contains the correct directory listing.
If I start 'aplay playprog .' in such a body,
aplay does not list the songs in the current directory,
but the song-directories of which the current directory is one,
i.e. ..  ; it does single-quote these were needed.
Right-mouse-click on such a quoted subdirectory name does not work.

When I tried creating files (touch) and directories (mkdir)
with names containing spaces on kfs and on fake worm fs,
that was refused with an error message 'bad character in ... name'.

However, intro(5) states

    Plan 9 names may contain any printable character (that is, any
    character outside hexadecimal 00-1F and 80-9F) except slash.)

But /sys/src/fs/port/9p2.c:155 contains

                if((*p & 0xFF) <= 040)
                        return Ename;

and /sys/src/fs/port/sub.c and /sys/src/cmd/disk/kfs/^(9p2.c sub.c)
contain similar checks.

Confused,
Axel.