Re: Error with -dbackend=null (Lilypond 2.23.10)

[David Wright]

On Sun 10 Jul 2022 at 23:08:19 (+0200), David Kastrup wrote:
> Paolo Prete <paolopr976@gmail.com> writes:
> >> On Sunday, July 10, 2022, David Kastrup <dak@gnu.org> wrote:
> >>> Jean Abou Samra <jean@abou-samra.fr> writes:
> >>> > Le 10/07/2022 à 17:38, Paolo Prete a écrit :
> >>> >> I just used -dno-print-pages as an alternative, and it works.
> >>> >> Will it be removed too in the future?
> >>> >
> >>> > I can't speak for future developers of LilyPond. On
> >>> > the other hand, unlike -dbackend=null, -dno-print-pages
> >>> > is documented with an explanation of its use case (not
> >>> > outputting the "main" PDF when using -dcrop or -dpreview),
> >>> > so it certainly won't be removed as a mere cleanup.
> >>>
> >>> Cough cough.
> >>>
> >>> git show release/2.21.0-1:Documentation/usage/running.itely
> >>>
> >>> [...]
> >>>
> >>>     @item null
> >>>     Do not output a printed score.  This has the same effect as
> >>>     @code{-dno-print-pages}.
> >>>
> >
> > ?
> 
> I was just showing that -dbackend=null had been documented in the
> "Running Lilypond" guide.

Indeed. And the stable Usage (2.22.1-1) mentions five backends:
ps, eps, null, scm and svg, whereas the preview section mentions
six, not including null: pdf, png, ps, eps, svg and scm.

Unstable's (2.23.10) backends are reduced to ps and svg, but the
preview section remains unchanged in Usage.

Cheers,
David.