Saul Tobin <saul.james.to...@gmail.com> writes:
> Hi all,
>
> I'd like to get folks' thoughts on the future of LilyPond official Emacs
> support.
>
> My project lilypond-ts-mode (https://github.com/shevvek/lilypond-ts-mode)
> is nearing the end of alpha, and is relatively stable and feature complete.
> Features include full support for nested Scheme/LilyPond embeddings,
> modular compilation commands, automatic detection and selection of LilyPond
> installs, dynamic completion and autodoc via the LilyPond runtime, and
> rhythm-aware "vertical" navigation. The package also has decent test
> coverage and resolves multiple open bugs pertaining to lilypond-mode.
>
> It looks to me like except for the recent renaming patch, lilypond-mode has
> been essentially unmaintained for 10-20 years. Initially I had planned to
> merge some aspects of lilypond-mode into lilypond-ts-mode, but after
> looking at the code of lilypond-mode, my impression is that it would be
> simpler to rewrite from scratch whichever features are worth preserving,
> rather than trying to update the existing lilypond-mode code to take
> advantage of modern Emacs and modern LilyPond. I also have to wonder if
> some of lilypond-mode's features either still work properly or are
> genuinely useful to the type of LilyPond user who prefers Emacs over
> Frescobaldi.
>
> In short, my pitch is that it's time to move towards retiring lilypond-mode
> in favor of lilypond-ts-mode.
>
> I believe that quite a few LilyPond devs are Emacs users. If you haven't
> yet, I highly encourage you to give lilypond-ts-mode a try. I think you'll
> be pleased — or if not, please let me know why!
git shortlog -s --after="10 years ago" elisp
1 Dan Eble
2 David Kastrup
2 Han-Wen Nienhuys
3 Jean Abou Samra
3 Jonas Hahnfeld
3 Mark Knoop
2 Martin Joerg
1 Valentin Villenave
7 Werner Lemberg
1 Yiyu Zhou
Did you get Werner's opinion?
At any rate,
git grep lilypond-ts-mode
yields exactly zero hits in the LilyPond repository.
Neither is there anything in either ELPA or MELPA to be found.
If you want to solicit feedback, maybe you should put some info about it
anywhere where it could be found? And/or place the package in MELPA or
some other readily available Emacs package repository?
Particularly putting the package in one of the standard package
repositories would make it simple for people to install, test, deinstall
and/or update the package.
--
David Kastrup
