On Tue, 14 Oct 2003, Joao Luis Meloni Assirati wrote:
> Wait... No need to pass the socket name to kdvi. I got it now :). If kdvi
> doesn't touch an environment variable named LYXSOCKET, the lyxclient
> could read it. Then there is no need to any wrapper.
I confirm that kdvi does not touch its environment (at least too much). It
is easy now:
lyx will set the environment variables:
EDITOR='lyxclient -g %f %l'
LYXSOCKET=<location of the socket>
Xdvi uses EDITOR, kdvi ignores it but we can set the editor in its
apropriated dialog. LYXSOCKET stays in the environment of {x,k}dvi.
When lyxclient starts, it inherits LYXSOCKET from {x,k}dvi.
I will send an updated inverse search patch, together with a patch to
lyxclient to read LYXSOCKET.
Joćo.
