Re: OT - Spaces in file and directory names (was: Alias syntax fo
Jim.Hyslop writes: > > What I object to is the attitude "spaces in file names are evil," the phrase > that kicked off this (as you correctly pointed out) off-topic discussion. > That attitude is outmoded, and reeks of a calcified mentality that refuses > to accept change. Then let me rephrase the attitude: "Funny" characters (like spaces) in file names are nice and work well as long as you never use anything other than point and click applications, but they will cause you no end of grief if you ever use anything else, so they are best avoided. -Larry Jones I can feel my brain beginning to atrophy already. -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: OT - Spaces in file and directory names (was: Alias syntax fo
Rick Genter writes: > > You mean point and click applications like WinCVS? No, I mean real point and click applications. WinCVS is just a point and click wrapper around a traditional application. -Larry Jones I don't see why some people even HAVE cars. -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: OT - Spaces in file and directory names (was: Alias syntax fo r a m odule that has a space in its name)
This whole discussion, OT though it might be, reminds me of a recent discussion of the "proper" way of quoting things (use of backquotes and apostrophes and such). I think that discussion was also on this list, though I thought the outcome was more opposite than parallel to the outcome of this one. FWIW, mostly as an amusing side note. On Fri, Apr 22, 2005 at 11:39:06AM -0400, Jim.Hyslop wrote: Bulgrien, Kevin wrote: > It is easy to tell everyone else what they ought to do in hind-sight. Nobody's doing that. I clearly acknowledged that *when these applications were written*, handling spaces was extremely difficult to do. I'm not denegrating the years of hard work that went into various tools, nor am I saying we should retrofit all applications. What I object to is the attitude "spaces in file names are evil," the phrase that kicked off this (as you correctly pointed out) off-topic discussion. That attitude is outmoded, and reeks of a calcified mentality that refuses to accept change. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs -- Doug Lee [EMAIL PROTECTED]http://www.dlee.org BART Group [EMAIL PROTECTED] http://www.bartsite.com "You must let me try, for a true soldier does not admit defeat before the battle." --Helen Keller (in a letter to the president of Radcliffe College) ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: OT - Spaces in file and directory names (was: Alias syntax fo
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Jones > Sent: Friday, April 22, 2005 11:56 AM > To: Jim.Hyslop > Cc: info-cvs@gnu.org; 'Bulgrien Kevin' > Subject: Re: OT - Spaces in file and directory names (was: Alias syntax fo > > Then let me rephrase the attitude: "Funny" characters (like spaces) in > file names are nice and work well as long as you never use anything > other than point and click applications, but they will cause you no end > of grief if you ever use anything else, so they are best avoided. You mean point and click applications like WinCVS? -- Rick Genter Principal Engineer Silverlink Communications <mailto:[EMAIL PROTECTED]> (781) 272-3080 x242 ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: OT - Spaces in file and directory names (was: Alias syntax fo r a m odule that has a space in its name)
Bulgrien, Kevin wrote: > It is easy to tell everyone else what they ought to do in hind-sight. Nobody's doing that. I clearly acknowledged that *when these applications were written*, handling spaces was extremely difficult to do. I'm not denegrating the years of hard work that went into various tools, nor am I saying we should retrofit all applications. What I object to is the attitude "spaces in file names are evil," the phrase that kicked off this (as you correctly pointed out) off-topic discussion. That attitude is outmoded, and reeks of a calcified mentality that refuses to accept change. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: OT - Spaces in file and directory names (was: Alias syntax fo r a m odule that has a space in its name)
It is easy to tell everyone else what they ought to do in hind-sight. Perhaps the proponents of spaces in file names are primarily users of GUI tools where a heavy front-end takes care of all the details for you? I do not think I should presume to tell everyone who wrote all of the legacy shell tools that their work is all archaic and obsolete just because I want spaces in my file names. When it comes down to it, almost all of life issues are constrained by practicality and cost. Is there a theoretical reason to include spaces? Sure. Does it make sense to rewrite the world of established tools to handle spaces in file names? Not really. Is it really worth losing sleep over? If I really thought so, maybe I would go on a permanent sabbatical and make it my life's work, and would end up contributing almost nothing of real import to society. I do not really anticipate anyone in the "for spaces in file names" camp being willing to put feet to their religion, but, maybe I am just a skeptic? Hey, I space-filename-harden my stuff, but that does not stop me from feeling that life would be a lot easier without spaces in file names. A thread like this will not change that reality. Why are most fire engines red when it has been shown that that other nasty yellowish/green color is actually more visible? ... Because of a strong historical precedent that wreaks havoc with theoretically better implementations. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
