From owner-freebsd-current Thu Jun 8 11:13: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id E9FED37BC4D; Thu, 8 Jun 2000 11:12:50 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA562572; Thu, 8 Jun 2000 14:11:23 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <2000-06-08-12-51-54+trackit+sam@inf.enst.fr> References: <20000608124605.G82993@lucifer.bart.nl> <2000-06-08-12-51-54+trackit+sam@inf.enst.fr> Date: Thu, 8 Jun 2000 14:11:48 -0400 To: Samuel Tardieu , Jeroen Ruigrok van der Werven From: Garance A Drosihn Subject: Re: mktemp() patch Cc: Kris Kennaway , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:51 PM +0200 6/8/00, Samuel Tardieu wrote: >On 8/06, Jeroen Ruigrok van der Werven wrote: >| -On [20000608 03:12], Kris Kennaway (kris@FreeBSD.ORG) wrote: >| >Instead of using only alphabetic characters, the patch uses the following >| >character set: >| > >| >0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ >| > >| > which is not believed to cause any problems with shells. >| >| Some shells parse # as a deletion character if memory serves me right. >| I think I noticed this behaviour when I started using zsh a few weeks >| ago after ksh. > >Also ^ is used for substitutions in many shells (as in ^faulty^ok). I believe bash requires some kind of whitespace character (blank, tab, newline) in front of the '#' before it will treat it as the comment character. I am not sure about other shells (people who use other shells might want to check). Similarly, I believe '^' is used for substitutions ONLY if it is the first character in the line. Ie, 'echo hello^to^you' does not do any substitution on the previous line. Since we know these characters are only being used in a filename, and NOT as the first character of a filename, then we should not have trouble using them. I must admit I am not as comfortable using '+=,', and I think one of '@' or ':' should go, just in case the file is used in some context that reads blah@blah:blah as userid@hostname:fname I would probably drop the '@', but if there is some other reason to drop ':' then the '@' could probably stay. At the same time, I do like to see the set expanded as much as possible, without causing any problems. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message