Nicolas, The ~ I have in mind appears only as the first character since it replaces /home/userName, so it might not be a problem. Am I missing something?
I realize I mentioned /~/andSoOn, but that was only in the context of Pharo's having introduced the leading /, turning ~/andSoOn into garbage and then getting confused by it, or something like that. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Nicolas Cellier Sent: Sunday, October 04, 2009 4:05 PM To: [email protected] Subject: Re: [Pharo-project] Dumb question: ~ vs. /home/user If you follow that path, don't forget we might require a way to escape '\~' Nicolas 2009/10/4 Schwab,Wilhelm K <[email protected]>: > Nicolas, > > It is OS-specific, but there is no reason to avoid doing things that > are expected on the local host - mac menus come to mind. An > OS-neutral approach gets the least-common denominator. Another more > fundamental example: the windows guys should get ready to part with > drive letters :) > > I think Randall nailed it with wildcards; that's where it fits. I suppose > one could provide a Windows version of it (/home/user could map to the > documents and settings craziness), though I learned the hard way to steer > clear of such things on Windows - if I have to use Windows, give me my own > directory on c: any day. > > This cropped up in porting one of my tools that I've used for longer than I > care to describe, and have ported a couple of times. Now I need a Linux > version of it, and ~ would be a nice solution to some problems that quickly > surfaced. > > Bill > > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Nicolas Cellier > Sent: Sunday, October 04, 2009 3:28 PM > To: [email protected] > Subject: Re: [Pharo-project] Dumb question: ~ vs. /home/user > > Isn't this OS-centric ? > > Nicolas > > 2009/10/4 Randal L. Schwartz <[email protected]>: >>>>>>> "Wilhelm" == Schwab,Wilhelm K <[email protected]> writes: >> >> Wilhelm> Understood - the question was (is?) whether or not Pharo >> Wilhelm> should recognize it and act accordingly - I suspect the answer is >> no. >> >> It *should* be understood and interpreted in the same places where '*' >> and '?' and '[]' are used for globbing, since it's effectively a >> globbing character. >> >> So for example, presuming a hypothetical: >> >> '*.st' matchingFiles >> >> to return everything matching in the default directory, then: >> >> '~/foo' matchingFiles >> >> should return something relative to the home directory of the current user. >> >> -- >> Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 >> 777 >> 0095 <[email protected]> <URL:http://www.stonehenge.com/merlyn/> >> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. >> See http://methodsandmessages.vox.com/ for Smalltalk and Seaside >> discussion >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
