Thank you, Werner, for your reply. Werner LEMBERG wrote:
> We can 'lift' the snippet in question > https://wiki.lilypond.community/wiki/Indenting_individual_systems > to make it also part of the 'official' snippets; it would be then available > in the 'Snippets' document. > I think that this is a good idea, at least for now. If you, as a power-user who produces an incredible amount of scores, have > used it only once I would rather say this is something that should *not* > be built into LilyPond. IMHO, this is exactly what a snippet is good for. > I am not sure I deserve the label of “power user”! I think I have published fewer than ten LilyPond editions to date. Most of my work is with a cappella choral music — usually Renaissance polyphony, Anglican chant, or hymns — where indenting individual systems (e.g., to indicate the first entry of an instrument) is something that one very rarely needs to do. If I engraved more instrumental music, I think that I would need the functionality much more often. (The one and only time in recent memory that there was an instrumental line in my score, I did in fact need \pseudoIndent!) Based on quick Google searches just now for “Sibelius how to indent an individual system” and “how to indent an individual system in Dorico,” I gather that it is very simple for the end user of Sibelius or Dorico to adjust the indentations of particular systems in those programs. (Maybe even just click and drag? I am not sure, as I use LilyPond exclusively.) Compare Indenting individual systems - LilyPond wiki <https://wiki.lilypond.community/wiki/Indenting_individual_systems>, where I see approximately 150 lines of code that I need to paste into my LilyPond file in order to get the same effect in my output. Many of us on this list (including, at this point, me) are comfortable with the Wiki and happy to skim over long blocks of code and then paste them into our own work. I love the Wiki! And yet at the same time, given how common it is in music engraving to indent a particular system differently from other systems, I think it’s worth making the functionality native to LilyPond and adding an explanation to LilyPond Notation Reference: 4.5 Horizontal spacing <https://lilypond.org/doc/v2.24/Documentation/notation/horizontal-spacing> (or somewhere else in the documentation). I love LilyPond, and I want more people to use it — including people who, like me, have zero background in coding or computer programming. My 0.02 USD is that this perhaps is the kind of functionality where we lose users to other software programs who might otherwise become (as I want them to become!) the next generation of power users of LilyPond.
