Currently supported options from lilypond-book about lyluatex HOT 6 CLOSED

Based on my reading of the keycommand package, it is not possible to support a keyword which is both boolean (given or not given) and general (given with a value). That is line-width without a value cannot be supported along side line-width=size\unit (similar for relative and relative=n). I'm not so sure about other ways of defining keyword commands (such as keyval or pfgkeys).

from lyluatex.

@rpspringuel have you ever looked into the (rather new) Github feature of "projects"? Maybe lilypond-book compatibility would be a good candidate for that. The checklist would then become a backlog, with the advantage that each item could become an issue (with assignee, comments etc.).

from lyluatex.

No, I haven't. I'll look into converting this into one of those now, as it seems like as good a time as any to familiarize myself with the new feature.

from lyluatex.

Now Project #1

from lyluatex.

Thank you. I think that's a good way to track this "project". In theory the notes could immediately be changed into issues, but that would unnecessarily clutter the issue tracker. So for now I suggest that in order to comment on notes we edit them but clearly mark the edit as comments.

In general I suggest that we don't try to copy lilypond-book but aim at supporting all of its options. I would discuss the naming of options separately and provide compatibility aliases if necessary.
For example, I find the quote name pretty stupid. It's clear where it's coming from, but an indented music example semantically is in no way a "quote".

from lyluatex.

So for now I suggest that in order to comment on notes we edit them but clearly mark the edit as comments.

The one problem I see here, is that the cards are limited in size. Any issue that really starts to generate discussion will quickly run out of space and require conversion to an Issue anyway in order to continue the discussion.

from lyluatex.