João Luis Meloni Assirati <[EMAIL PROTECTED]> writes:
> > * if LyX were able to talk to xdvi through the lyxclient interface, then we
> > wouldn't have to keep creating a new xdvi process in "client" mode each
> > time I click in the LyX window which is what happens now.
>
> No. We don't create a new xdvi process each time we click in the lyx window.
> View -> DVI remains the only way to start a new xdvi process. Forward search
> means that this new xdvi will start at the right page. What occours now is
> that xdvi is called with the option
Sorry to be pedantic, but from LyX's point of view that's "creating a new xdvi"
isn't it? I.e., your "xdvi is called" is my 'system("xdvi option1 option2");'.
Or, eventually, when system() is consigned to the waste bin of history we'll be
using fork() and 'execvp("xdvi", ["xdvi", "option1", "option2", 0]);'
What xdvi itself does with this is a separate matter. (Whether a whole new and
fully-functional instance of xdvi is created or whether the newly created
process just posts the new info to an existing, running xdvi client for it to
update its data.)
Anyway, the whole discussion is just for my academic interest, so don't let my
pedantry bother you :)
> There is also a high level tool to communicate with xdvi, which is xdvi
> itself
> (i.e., there is no xdviclient; instead, xdvi itself can work in client mode).
> It communicates with another running xdvi not through a socket like we do,
> but through something called "X properties", a native xwindow message passing
> protocol (the same way emacsclient and 'mozilla -remote' do
> (http://www.mozilla.org/unix/remote.html)).
Interesting. Thanks. FWIW it appears that Windows apps tend to use a similar
technique to prevent multiple instances of an app from running simultaneously.
> > I think that this is a great piece of work
> > and think it should have gone into the LyX sources a long, long time ago.
> Thanks for the kind words, Angus. I am a theoretical physicist, not a
> programmer, and all I know about C++ comes from hacking parts of the lyx code
> and reading some online references in www.lyx.org/devel/references.php.
That sounds like the same route I took into LyX :)
> For me and some of my colleagues, lyx and a web browser are
> the most important software, so I hack lyx because it is
> important to me, in those parts that I think are important to me.
> Therefore I think it is natural that my contributions are not priority.
Well, it seems to me that we've raised the entry bar too high. LyX survives on
contributers like yourself and we should make it easy for them to feel like
"insiders". I'm guessing that etting your code into the repo in less than two
years would have helped enormously to make you feel like an "insider" :)
> > Very well :) http://www.lyx.org/~leeming/William/
>
> Beautiful. You are a coruja ("owl") like we say in Brazil, meaning a very
> proud and loving dad (applies to a mom, too) :).
Less loving this morning as the wee bugger kept us up all night for no good
reason. Pushing at boundaries already :)
Angus
