"Phil Holmes" <em...@philholmes.net> writes: >> @* >> @file{blah} > > David doesn't like @* so I avoided it. I'll use @*
@* is awful. It cuts the current line _short_ unconditionally which means that we may get abysmally bad breaks when the paragraph content changes. It makes more sense to use @/ which merely permits linebreaks. >> http://codereview.appspot.com/6345088/diff/1/Documentation/notation/fretted-strings.itely#newcode1404 >> Documentation/notation/fretted-strings.itely:1404: >> @file{ly/predefined-guitar-fretboards.ly}, @* >> oh god. Seriously?! there _has_ to be a better way to make tex behave. >> >> hmm, maybe these could be wrapped in an @example? it's icky, though. >> Not a serious suggestion. > > To be honest, it didn't seem worth worrying about too much. It's > basically a list of filenames. Separating them with line break isn't > a big deal, and at least allows the user to read them? Makes for inconsistent formatting of lines. Making an example block or a one-column "table" seems to make for more consistent results. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel