Outdated lilypond-mode emacs files in lilypond-data

Bug #219668 reported by Emmanuel Charpentier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lilypond (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: lilypond-data

The file header has :

;;;; (c) 1999--2006 Jan Nieuwenhuizen <email address hidden>

Extract from /usr/share/emacs/site-lisp/lilypond-mode.el :

[ ... ]

(defconst LilyPond-version "2.5.20"
  "`LilyPond-mode' version number.")

Since we are well in 2008 and lilypond is now at 2.10.25 (stable branch), this version appears outdated. Indeed, some very common syntax (compiling correctly) is flagded as being errors in emacs.

Note : I did *not* upload the upstream source to check this file, but I doubt that Lilypond maintainers, who teke the trouble to write and maintain convert-ly, would forget *this*, even if hey are currently promoting jedit and its lilypond mode...

The source package is of course lilypond.

charpent@yod:~/Partoches/EssaisLilyPond$ lsb_release -rd
Description: Ubuntu 7.10
Release: 7.10

charpent@yod:~/Partoches/EssaisLilyPond$ apt-cache policy lilypond-data
lilypond-data:
  Installé : 2.10.25-0ubuntu1
  Candidat : 2.10.25-0ubuntu1
 Table de version :
 *** 2.10.25-0ubuntu1 0
        500 ftp://ftp.free.fr gutsy/universe Packages
        100 /var/lib/dpkg/status

Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

I don't see the link between convert-ly and the emacs mode... and the version is still 2.5.20 in the upstream source.
The bug report should go upstream I think.

Revision history for this message
Emmanuel Charpentier (charpent) wrote : Re: [Bug 219668] Re: Outdated lilypond-mode emacs files in lilypond-data

Gauvain Pocentek a écrit :
> I don't see the link between convert-ly and the emacs mode...

OK : I wasn't very clear. What I meant was that since lilypond authors
take the trouble to maintain a (complicated) program to convert sources
 between versions of the syntax, I am quite surprised to see that the
maintainance of the emacs mode (probably a much simpler task) is not done.

> and the version is still 2.5.20 in the upstream source.

That's what I just discovered by tracking it.

> The bug report should go upstream I think.

I'll post a short note on lilypond-users.

Thank you for your prompt answer...

     Emmanuel Charpentier

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 or 9.04?

Changed in lilypond:
status: New → Incomplete
Revision history for this message
etali (etali) wrote :

We'd like to figure out what's causing this bug for you and whether it has been resolved, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Changed in lilypond (Ubuntu):
status: Incomplete → New
Changed in lilypond (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lilypond (Ubuntu) because there has been no activity for 60 days.]

Changed in lilypond (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.