[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Vindaloo - open a PDF from the command line
From: |
Nicola Pero |
Subject: |
Re: Vindaloo - open a PDF from the command line |
Date: |
Thu, 15 Apr 2010 12:51:27 +0100 |
Is there a reason that it's called gopen instead of open?
Avoiding a conflict on Mac OS X?
Why two competing helpers, gopen and openapp, exist eludes me, though.
I can clarify a bit. :-)
"openapp" is not a open-file helper. It's a script that just runs a
specific program. It uses to be
required to execute any GNUstep apps, but it's no more. I recommend
nobody uses it
unless you're working with library combos (which very few people do)!
Just invoke
the program directly instead! :-)
Nowadays instead of typing "openapp Gorm" you can simply type "Gorm"
and the results
should be the same (and the program will start much faster!). :-)
The main use case for "openapp" is if you're using library combos and
developing stuff.
Then openapp allows you to start up an application in a different
library-combo than the one
you are currently living in. That might be useful when developing
with multiple library combos.
But I suspect if we were to remove it, nobody would even notice at
this point. ;-)
I guess typing "gopen -a Gorm.app xxx.gorm" might be almost equally
pointless as typing "openapp Gorm"
on a flattened installation - you'd expect "Gorm xxx.gorm" to do the
same thing and start faster ? ;-)
(unless Gorm doesn't allow you to specify what files to open on the
command line, in that case I suppose yes,
you're bound to have to use gopen)
"gopen" makes lots of sense if you don't know what program you want to
run instead (or don't want to bother
typing it), so "gopen xxx.gorm" would automatically select Gorm for
you and open xxx.gorm using it. That is
handy. :-)
"openapp" does not "choose" any program and only runs whatever you
provide. If you're using "openapp",
mostly likely you shouldn't.
Finally, if
openapp Gorm.app xxx.gorm
doesn't work, it's down to Gorm.app, not openapp, as that command is
entirely equivalent (and
should almost always be replaced with)
Gorm xxx.gorm
So, if Gorm opens files passed as command-line argument, this would
work; if it doesn't, it wouldn't. It's down
to Gorm to decide what to do with the command-line arguments (or
Vindaloo in the case being discussed).
Did that clarify a little bit ?
Thanks
Re: Vindaloo - open a PDF from the command line, Gregory Casamento, 2010/04/14
Re: Vindaloo - open a PDF from the command line, Riccardo Mottola, 2010/04/14