well, some examples of the LSR <http://lsr.di.unimi.it/LSR/Browse> have "2.18 or higher” so you’d technically miss those if you only search for 2.19 examples. I guess there are also a certain number of core features that remain compatible through all versions, so there is a fair chance that these might work even if the version says 2.16.
best, J > On Mar 18, 2016, at 2:57 PM, Kristin Rollins <kris...@verumsolum.com> wrote: > > Searching with Google tends to be more effective for me in solving my > issues with learning LilyPond and troubleshooting my work, especially > with the ability to simply type the query into the address bar of my > browser. (Though that is after I took the time to go through the > learning manual and at least review what documentation is available to > become familiar with it.) > > The one thing I have learned, after a couple of instances of finding the > wrong version's documentation (or multiple versions of the > documentation): I always start my search with: > > lilypond 2.19 > > and then my search terms. That will usually make the official > documentation for the proper version come to the top of the search > results and lower the risk of finding answers that relate to previous > versions. > > Kristin > > -- > Kristin Rollins > kris...@verumsolum.com > Portsmouth, VA > > On Fri, Mar 18, 2016, at 06:44 AM, David Kastrup wrote: >> That's one reason why it makes sense to look at the accompanying >> documentation of a LilyPond installation rather than search blindly for >> something on the net (which will frequently deliver outdated information >> and infrequently advance information). > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
