From: TRANS Date: 2005-09-27T01:45:44+09:00 Subject: Re: Finally an answer to my RubyGems question and some small suggestions On 9/26/05, Austin Ziegler wrote: > On 9/26/05, TRANS wrote: > > On 9/26/05, Austin Ziegler wrote: > >> On 9/26/05, TRANS wrote: > >>> On 9/26/05, Austin Ziegler wrote: > >>>> On 9/26/05, TRANS wrote: > >>>>> Do you think, while we're at it, some code can be put in there to > >>>>> deal with non-cross platform punctuation in file names? > >>>> I do not believe that this is a good thing to solve, personally, > >>>> and think that alternative solutions for Nano's problems are > >>>> better. > >>> Well, it NOT just a Nano problem. It IS a cross-platform problem. > >>> This can effect any project that uses a file name with certain > >>> punctuation. > >> Sure. But I don't think that most people would *want* to use such > >> punctuation in their function names. I think it's a Nano problem > >> because you're wanting to allow individual function specification. It > >> makes sense, but I don't think that it's a general-case problem. (It > >> never would have dawned on me to use *, ?, or a couple of other > >> characters in any filename that I would require from Ruby. This may > >> be because I do a *lot* of cross-platform work, but I just wouldn't > >> ever do that. I think it's something that could be discouraged.) > > Well, you are probably right --simply b/c there probably is no really > > good solution from this end. The real solution is to modernize the > > file systems themselves --personally, it boogles my mind that we still > > use .xxx in a filename for file type. > > I'm not boggled by that, actually. While imperfect, it *is* good for the > human eye's pattern matching -- if I see a bunch of files called .jpg in > a direction, I know they're the same. Icons can help with this, but only > to a degree. The interface can still display the type, just as it can display date or permissions if you want. T.