I reported the following bug #641 ----- Lyx communicates with pybliographic via ~/.lyxpipe.in and ~/.lyxpipe.out. These pipes are not erases if the lyx window is closed, lyx crashes or X crashes. Afterwards lyx will never again work together with other programs, the lyxpipe functionality is blocked. This is really bad for alomst all users. lyx should check if the .lyxpipes are still in use and erase them whtn it is started. (Why is this bug grave? Easy: It makes using lyx with citations impossible for normal people where I admin. The lyxpipe is a major loss of functionality.) ----
Now I am being told that it won't be fixed. Ever. WONTFIX. Reasons given: 1) It is hard to fix. 2) It is easy to remove the pipes manually. I think this is a bad attitude towards bugs. Why not stop all development in lyx? You can fix all bugs in latex code(easily) ;-) I think this bug prevents NORMAL users (not latex using GUI users) from using pybliographic or sixpack with lyx. You do not get a sensible error message, communication with lyx just fails after for example a power shortage. You get no clue, no gui option to remove the pipes. Telling people to remove the lyxpipes manually is not a solution but a complicated work-around. Most user don't know and don't care about the pipes, they want a program that just works. If recovering from a crash is so hard to do automatically, just offer a gui for manual deletion if the pipes already exist, when lyx starts. -- Moritz Moeller-Herrmann ICQ #3585990 (wiss. Mitarbeiter, IMGB, Mannheim)
