Celestia --url script.cel doesn't work under Linux

[amoroso]

A week ago I posted this question to Celestia Scripting, but received no reply. I try again with Celestia Users, which probably has a wider audience.

When I start Celestia and run a script from the shell prompt with the command:

Code: Select all

celestia --url myscript.cel

the program starts, but the script doesn't run. And if I add the --once option, a new instance of Celestia is started.

I use Celestia 1.3.2 configured with

Code: Select all

--prefix=/usr/local/celestia --with-gtk --with-lua=/usr/local/lua

under Slackware Linux 10.0. Do I need any specific configuration options or command line arguments?

I read a posting to Celestia Users that seemed to imply that the --url option works only on Windows. Is this correct? If not, how do I run a script from the command line?


Paolo Amoroso

[Christophe]

You can't start a script from the command line with the GTK version of Celestia. The CLI parameters are not the same on all platforms, and --url is only available on Windows. With the KDE version, simply put the script file name or url after 'celestia'.

Code: Select all

$ celestia --help
Usage: celestia [Qt-options] [KDE-options] url

Celestia

Generic options:
  --help                    Show help about options
  --help-qt                 Show Qt specific options
  --help-kde                Show KDE specific options
  --help-all                Show all options
  --author                  Show author information
  -v, --version             Show version information
  --license                 Show license information
  --                        End of options

Arguments:
  url                       Start and go to url


[amoroso]

You can't start a script from the command line with the GTK version of Celestia. The CLI parameters are not the same on all platforms, and --url is only available on Windows. With the KDE version, simply put the script file name or url after 'celestia'.

Thanks for the info, but I can't use the KDE version. I have the same problem described in this Celestia Users post with my Slackware Linux 10.0 box and KDE 3.2.3.


Paolo Amoroso