Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>>>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
| Lars> | BTW it might be nice to have "lyxclient file.lyx" open
| Lars> file.lyx in an | existing LyX instance.
>
| Lars> would it? I am not sure.
>
| We do not have any use for a non-option argument currently, so it does
| not conflict with existing syntax. Moreover, one would be able to bind
| that easily to a filemanager action.
Should it behave as emacsclient? and wait for the lyx to be finished
with the file before exiting?
| Lars> | How do you use -c? I tried something like "lyxclient -c
| Lars> buffer-new", | but it does not work. Am I supposed to give a
| Lars> command with the | lyxclient protocol cruft?
>
| Lars> lyxclient -c "buffer-new file.lyx"
>
| Lars> might work better.
>
| src/client/lyxclient -c "buffer-new file.lyx"
| lyxclient: Connected to /tmp/lyx_tmpdir14791Fyur52/lyxsocket
| ERROR:buffer-new file.lyx:malformed message
>
| However the following works:
>
| fantomas: src/client/lyxclient -c "LYXCMD:buffer-new file.lyx"
| lyxclient: Connected to /tmp/lyx_tmpdir14791Fyur52/lyxsocket
| INFO:buffer-new file.lyx
>
| I do not find it very user friendly...
Which is my I wan lyxclient in there so that we can improve on it.
I'll also continue with my work in making it into a libarary that
other applications can use.
I have a patch ready that redo some of the argument handling.
And move the socket stuff out into a different implementation file.
--
Lgb
