From mboxrd@z Thu Jan 1 00:00:00 1970 From: "rob pike, esq." To: 9fans@cse.psu.edu Subject: re: [9fans] blanks in names Message-ID: <1110399.1025797535@GOLD> In-Reply-To: <1b8fddb88743e230927ca086d93d4df2@caldo.demon.co.uk> References: <1b8fddb88743e230927ca086d93d4df2@caldo.demon.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Date: Thu, 4 Jul 2002 15:45:35 -0400 Topicbox-Message-UUID: c1e06728-eaca-11e9-9e20-41e7f4b1d025 I have a simpler solution. If you don't like blanks in file names, prohibit them again. (It's the 'frog' array in /sys/src/9/port/chan.c that determines this.) Servers that give you blanks will get caught (although the failures will often be mysterious). Fix those that do by relabeling as Nemo suggests, although please not with a variant invisible blank. Something visible but rarely used, such as the 0x80 rune. I enabled blanks because they kept appearing, everyone else accepts them, and it seemed a challenge to find a good solution. I still prefer the quoting solution because it leaves the underlying stuff alone, but it's easier to just say no. -rob