Jonas Hahnfeld via bug-lilypond <bug-lilypond@gnu.org> writes: >> Hello, >> >> Thank you for reporting. With >> >> $ ~/lilypond2.23.1/bin/lilypond-invoke-editor >> textedit://input/regression/mozart-hrn-3.ly:3:4:5 >> >> I get emacs running. With >> >> $ ~/lilypond2.23.2/bin/lilypond-invoke-editor >> textedit://input/regression/mozart-hrn-3.ly:3:4:5 >> >> the error is >> >> lilypond-invoke-editor (GNU LilyPond) 2.23.2 >> ERROR: no code for module (lily editor) >> >> This commit between 2.23.1 and 2.23.2 would seem a >> likely candidate: >> >> commit 029532b20243f5aec48178f20f7a5b83840cc92a >> Author: Jonas Hahnfeld <hah...@hahnjo.de> >> Date: Wed Mar 31 21:13:06 2021 +0200 >> >> Move all Scheme modules to a (lily) namespace >> >> This is more logical than (scm) originating from the directory >> layout in the repository. While at it, qualify all loaded files >> with that namespace (primarily through ly:load and one occurrence >> in ly_init_ly_module) so that we only need to add one directory >> to Guile's %load-path. > > Yes, the wrapper from GUB uses the wrong directory in GUILE_LOAD_PATH. > The fix is rather simple (https://github.com/gperciva/gub/pull/87), > maybe it would be a good idea to release 2.23.4 with this. Phil, what > do you think?
Seems a bit wasteful not to include !882 while fixing point-and-click. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
