Hello,
Just compiled 1.3.0 from source. Played around with the lyx-server. IIRC
lyx should kill .lyxpipe.{in,ou} on exit. Apperantly that is not the case.
I do remember a thread about reverting some changes to the lyx-server
just before releasing 1.3.0 since usage shut up to 100% when using it.
Did same fix get lost in the shuffle since I remember this bug getting
fixed
in some 1.2 or eralier.
By the way: the sample in section 4.3 of Customization doesn't work
in 1.3.0 any more. Should I provide a better example?
Additionally the Perl-code in LyX-Client (under /development/lyxserver/..)
makes assumptions that are no longer true. Is the code unmaintained?
It seems rather old.
I am interested in writing a "torture-test" for lyx to trigger bugs and
crashes
(the whole undo-redo thing comes to mind). The obviuos way for me is to
use lyx-server and perl.
I thing that I will have an alpha ready in about 10 days. Are you guys
interested?
Michael
--
Michael Abshoff - MRB - Universität Dortmund - Telefon 755-3463 (intern)
Where do you want to RTFM today?
- Re: BUG?: .lyxpip.{in,out} not deleted on exit Michael Abshoff
- Re: BUG?: .lyxpip.{in,out} not deleted on e... Joao Luis Meloni Assirati
- Re: BUG?: .lyxpip.{in,out} not deleted ... Michael Abshoff
- Re: BUG?: .lyxpip.{in,out} not deleted on e... John Levon
- Re: BUG?: .lyxpip.{in,out} not deleted ... Michael Abshoff