Romain Francoise wrote: > Cameron Horsburgh <[EMAIL PROTECTED]> writes: > > >>Er, don't do that--I'm running LilyPond from upstream, not the Debian >>version. The package structure has changed somewhat, even in the sid >>version. > > > Ah. > Young Grasshopper, writing bug reports at 5:30 in the morning after five hours' sleep is a road leading to folly and ruin. At very least, include all relevant information!
> >>The main thing that concerns me is that the mode worked perfectly well >>under Emacs 21, and has only stopped working since I installed >>-snapshot. > > > I really don't see how that could be possible. > It seems there may be simultaneous bugs going on, all at the LilyPond end, but the working together to just *look* like an emacs-snapshot bug. > >>However, if you suspect it has something to do with my LilyPond >>installation and not emacs-snapshot, I'll try bug-lilypond again. > > > Where exactly did you get those .debs? I can have a look and try to see > where the problem is; in any case it is certainly not a bug in > emacs-snapshot. > On my otherwise pristine sid box I have allowed one impurity--depending on my mood I either compile LilyPond from the upstream tarball, or I cheat and use their 'Grand Unified Binary' which, apart from this issue, works well. LilyPond-mode hasn't really changed much over the last couple of years. An odd thing has happened upstream though--a small patch that was supposed to add 22.0 compatibility didn't work for me, but with slight modification has fixed the problem with 21.4. Given that LilyPond-mode in it's unpatched state used to work, I'm a little confused. I sent a report to bug-lilypond--if you want to have a look, you'll find the thread at http://lists.gnu.org/archive/html/bug-lilypond/2006-02/msg00054.html Anyway, I'm satisfied that it isn't a problem at your end, so I'm happy for this bug to be closed with a 'not-my-problem' tag. Thanks for your time. I promise to have at least one coffee before firing off bug reports in the future! Cameron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
