Re: GNUstep "open" tool

[Nicola Pero]

> Mac OS X doesn't have openapp (I tried it the last time I had access to an OS
> X machine), but it does have open. I was rather confused by this, as I'm used
> to openapp. On OS X, open is how you open both files and apps from the command
> line, and it does search for apps (and only apps) in the well-known paths,
> after the current directory (just like my patch does).

Ok - thanks - Stefan also told me the same - he'd simply like to have a
single tool doing the two different things ...

it might become a simple matter of taste then ... but I'd personally
prefer to keep them separate ... `real' users are anyway supposed to use a
GUI interface to open files and run applications ... while `techies'
probably prefer to have more control on what's happening and would prefer
having separate commands for separate operations (at least, I do) ...
openapp for starting system/local/etc applications and gopen for opening
local files.

if they are kept separate, it's still very easy - trivial - to write a
very little shell script which - if the extension is .app or .debug, runs
openapp, and if the extension is not .app, runs gopen ... that script
would behave as on Mac OS X as far as I understand from your explanations.
so I suppose if you want the mac os x behaviour you can still write a tiny
script of this kind and use it on top of the standard ones.


btw, shall we extend openapp so that `openapp Gorm' will work (and not
only `openapp Gorm.app' or `openapp Gorm.debug') ? openapp knows that the
argument is an application so if it has no extension it could try adding
.app or .debug before starting the search ...

(btw, gopen should manage not only Xyz.app but also Xyz.debug).