On Wed, Jan 30, 2002 at 08:59:33AM +0100, Gabriele wrote: > I think this should be different, anyway. > > Since xmame now understands the command line "xmame > /path/to/zipfile.zip" it should be able to parse "xmame zipfile.zip" as > well. Agreed. Especially since it make it easier to use tab-completion in bash :-)
> > It works if you type "xmame ./zipfile.zip", so I think it's not that > difficult. On the opposite side, it shouldn't work by typing "xmame > /path/to/zipfile" without the .zip extension. Not agreed. well, partially... If it is indeed a zip file then it could more or less be logical to have xmame fail with such a thing. On the other hand if /path/to/something can be read as /path/to/extracted-zip-file-in-a-directory, then it should result into 'xmame -rp /path/to/ extracte-zip-file-in-a-directory-is-gamename' behaviour. However I have the felling that in such case it would be much simpler to also allow /path/to/something to be a zip file without the extension. David -- "Never assume malice when results can be explained through incompetence"? -- Napoleon Bonaparte -- In the case of M$, the distinction can be a difficult one to make _______________________________________________ Xmame mailing list [EMAIL PROTECTED] http://toybox.twisted.org.uk/mailman/listinfo/xmame
