Joao Luis Meloni Assirati wrote:
> I confirm that kdvi does not touch its environment (at least too much). It
Well if it would touch a variable called LYXSOCKET, I'd call that unfair
practice!
> 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.
Seems super.
Regards, Alfredo
