-
If `lyluatex` is to be a drop-in replacement for `lilypond-book` Then the goal should be to support all the [`lilypond-book` music fragment options](http://lilypond.org/doc/v2.19/Documentation/usage/…
-
When a LilyPond compilation fails a Lua stack trace occurs in `write_tex` because it tries to read non-existent files.
This should be handled by at least suppressing the error. Of course the user s…
-
Till now :
- we define a special command to change every global option within the doc ;
- we add special parts to the name of temporary files in `hash_output_filename` ;
- we define options in thr…
-
Currently the file to be included by `\lilypondfile` is searched for
* as a relative path appended to `CURRFILEDIR`
* using `kpse.find_file()`
I'm not sure about the latter, but I assume it fin…
-
Maybe this is a stupid question, but why do we have to use our "private" command/environment names (`\lily`, `ly`, `\inlcudely`) instead of directly using those from `lilypond-book` (`\lilypond`, `lil…
-
There should be a command that inserts a score as a sequence of systems interspersed with some glue space (like lilypond-book does). This will allow multi-system scores to flow over page breaks.
Th…
-
Set indentation of the first music system to zero. This option affects LilyPond, not the text layout. Since no indentation is the default, `noindent` is redundant normally.
-
I suggest considering to change the `line-width` argument to `linewidth`
While `line-width` is the LilyPond name of the paper variable `linewidth` is more in line with LaTeX syntax/expectations and…
-
line-width=size\unit
Set line width to `size`, using `unit` as units. `unit` is one of the following strings: `cm`, `mm`,` in`, or `pt`. This option affects LilyPond output (this is, the staff leng…
-
the lilypond temp directory will grow really fast, with a full set of files for any modification of any score (even size changes). There should be a nice way to purge the temp directory, although it m…