On Sat, Nov 29, 2008 at 01:50:35AM +0100, Francisco Vila wrote: > are cleared (not immediately but after a variable wait), and then > (again after a variable wait sometimes rather long) finally shows the > output. The feel is otherwise quick, I usually work with gedit+evince > under Linux+Gnome and the response for small files is absolutely > instantaneous, less than 1 second. Only jpedal seems not to finish > thinking for ages.
I'm using a little home-brewed script that does the following things automatically: 1. If I start the script with a lilypond file as argument, lilypond processes the file with --ps option (postscript only). No time is waisted to convert the ps to pdf. 2. Two windows are opened: One window with gv shows the postscript picture, one xterm window running vim to edit the lilypond source. Both windows are automatically placed and correctly dimensioned to fit next to each other on my screen. gv is called with the "-watch" option and automatically sets the zoom to 50% ( -scale=-2 ) to show more of my page. 3. If I edit the source, everytime I save this is detected by an endless loop in my script, lilypond is called and a new postscript is created. This is detected by gv thanks to the -watch option. Et voila, the score can be seen almost instantaneously! 4. And all this can be done without ever touching the mouse :-) I did take a short look at kdelily (or was it lilykde ?) and jedit/lilypondtool. I was impressed at first sight, but in the end I liked my own fast and lightweight approach better. If anyone is interested I can make it publically available. But I have to polish it a little bit first to make it more configurable to different needs (screensizes, file locations, etc.) _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
