summaryrefslogtreecommitdiff
path: root/Documentation/usage
Commit message (Expand)AuthorAgeFilesLines
* Docs: run convert-ly for 2.14.0....Conflicts: Documentation/snippets/alternative-breve-note.ly input/regression/glissando-consecutive.ly input/regression/glissando-index.ly Graham Percival2011-06-065-5/+5
* Doc: Added new option 'papersize' to Usage...Added note on how to use @lilypond[papersize=xx] as defined in scm/paper.scm James Lowe2011-03-271-0/+22
* Doc: Linebreak edit for last Usage Commit...Hadn't noticed that the linebreak for last change was on a single line. My apologies. Have redone patch with appropriate line breaks as per the CG. James Lowe2011-03-181-1/+4
* Doc: Minor grammar change in Usage Manual...Simplified the explanation for the Variable LILYPOND_GC_YIELD James Lowe2011-03-181-4/+1
* Doc: cleanup @file{}, take 2: remove all @/ escaping sequences....For now, remove all @/ sequences from @file references. New line-breaks will be introduced later with an automatic rulein order to make the syntax more consistent. Valentin Villenave2010-11-265-62/+62
* Doc: clean up @file{} entries...This patch aims to improve syntax consistency in @file entries, by systematically escaping such characters as `.', `/' or `-'. Although this isn't strictly required by texinfo, it does make the docs source code cleaner to have the same policy everywhere. Valentin Villenave2010-11-245-55/+55
* musicxml2ly: dealing with languages...- adapt the -l --language=LANG option to the new \language "LANG" clause - reflect this in the appropriate section of the Usage Manual Jean-Charles Malahieude2010-11-201-2/+1
* Doc: Usage: add xref to lilypond-book options section.Patrick McCarty2010-11-181-1/+4
* Doc: NR 4.4.1 Vertical spacing...: Rewrite.Mark Polesky2010-11-051-1/+1
* Doc: convert-ly on English docs....I left most of the \RemoveEmptyStaff as it came from convert-ly; some of the grammar is a bit weird, but the basic idea is still there. I excluded Documentation/snippets/new/ changing-the-time-signature-without-affecting-the-beaming.ly because convert-ly wasn't smart enough to update it, and neither am I, since I know nothing about the new beaming code. Graham Percival2010-10-215-5/+5
* Doc: sharing ToC from lily to latex (fix 948).Graham Percival2010-09-141-0/+107
* Docs: NR 2.1 Vocal: rearrange sections... * vocal.itely - group all common notation under one section - move two sections to Techniques specific to lyrics * running.itely - fix resulting broken ref Trevor Daniels2010-08-301-1/+1
* Docs: Usage: can't @ruser to a non-nodeTrevor Daniels2010-08-201-1/+2
* Docs: Usage: add warning about 'staff-affinitiesTrevor Daniels2010-08-201-0/+14
* Doc: Usage.itely - more script line breaks...Second script example edited to avoid running off edge of PDF Split script using trailing backslash Also edited comment within script as it too was running of edge of PDF James Lowe2010-08-171-3/+9
* Doc: Usage.itely - script example line breaks...Script example is too long for a single line and causes information to run of edge of PDF. Split up script using trailing backslash onto multiple line James Lowe2010-08-161-1/+4
* lilypond-book.itely: commit a fix for issue 1221David Kastrup2010-08-161-1/+1
* Docs: AU: document shell redirects... - thanks, Eluze, Graham Trevor Daniels2010-08-131-0/+25
* Docs: AU: output can be directed to a folder... - thanks again, Eluze Trevor Daniels2010-08-111-3/+9
* Docs: Usage: explain multiple -I option... - thank, Eluze! Trevor Daniels2010-08-091-2/+6
* Doc: ensure two spaces after end of sentence.Ralf Wildenhues2010-08-014-30/+30
* Fix typos in the English manual.Ralf Wildenhues2010-07-313-3/+3
* Docs: Usage: Simplify Vim usage instructions.Patrick McCarty2010-07-261-28/+10
* DOC: revise Vim support in Usage Text Editors...revised setup of Vim mode in Usage Colin Campbell2010-07-251-16/+16
* Lilypond-book: Document htmly as allowed extension for HTMLReinhold Kainhofer2010-06-111-0/+1
* Doc: remove other copyright potential problem.Graham Percival2010-05-061-1/+1
* Doc: remove potential copyright issue.Graham Percival2010-05-061-1/+1
* Doc: Clarify \relative inside \repeat issue.Mark Polesky2010-04-301-17/+19
* Change lilypond-book's LaTeX environment option placement...This changes the documented option placement for LaTeX "lilypond" environments in lilypond-book mode to have the options after the environment name, like customary with LaTeX environments. lilypond-book is adapted to accept both previous and new order. David A. Kastrup2010-04-253-16/+16
* Doc: Update deprecated \relative syntax....* Replace "\relative { }" with "\relative c' { }". Mark Polesky2010-04-192-2/+2
* Doc: Usage: Add instructions on setting up chroot jailCarl Sorensen2010-04-141-0/+109
* Docs: Usage: update description of -dpreview.Patrick McCarty2010-02-211-0/+4
* Docs: Usage: fix links to alternate editors.Patrick McCarty2010-02-211-2/+2
* Doc: add instructions for articulate.ly; thanks Peter!Graham Percival2010-02-181-1/+22
* Doc: resolve various FIXMEs....Downgrading a FIXME to a TODO is still a "resolution". Of a sort. Graham Percival2010-02-111-4/+7
* Build: move unused templates into Usage.Graham Percival2010-01-241-9/+42
* Docs: Usage: -fsvg is not a valid option.Patrick McCarty2010-01-211-1/+1
* Docs: fix documentation reference of translation committishesJohn Mandereau2010-01-215-5/+10
* Usage: add stub for info about shared \includes....This is aimed at non-lilypond-distributed projects, such as Dr. Chubb's articulate.ly (better MIDI sound). Ideally we'd have nothing in this section (because anything useful would be merged with lilypond, possibly about being cleaned up a bit), but adding info here is a useful stepping stone. Graham Percival2010-01-201-0/+17
* Doc: new chapter "External programs" in Usage....This consists of the old "Converting from other formats" chapter, plus the "Point and click" and "Text editor support" from the Running lilypond chapter; all of these kind-of stuck out awkwardly. No nodes were harmed (renamed) in the making of this patch so far. "Running lilypond-book"'s "Alternate methods..." has been moved into External programs, with the new name of "LilyPond output in other programs". The old name still exists for ease of TOC and whatnot, but anybody referring to it might want to change to the new name to avoid a relatively pointless redirect. Graham Percival2010-01-203-243/+268
* Docs: Usage: use .lytex instead of .pdftex...The latter extension gives an error message saying that lilypond-book does not understand the file extension. Patrick McCarty2010-01-061-1/+1
* Add lilypond-book --use-source-file-names command-line option...This is mainly intended to make regression tests output filenames more stable against changes of their contents and changes in lilypond-book, and could also make generated snippets reuse a little easier (as it makes output filenames controllable and predictable by the user). This doesn't break the hashing system that saves lilypond processing time. See complete discussion at http://lists.gnu.org/archive/html/lilypond-devel/2009-12/msg00636.html John Mandereau2009-12-291-1/+6
* Doc whitespace: process most files....I don't want to touch stuff that people are working on: essay, extending, contributor, and the translations. Graham Percival2009-12-213-37/+37
* DOCS: add Vim runtimepath for Fedora to "usage" manual...The runtimepath to set up LP syntax highlighting in vim on Fedora is very different from what's given in the usage manual. This example shows the proper path on Fedora 12 Jonathan Kulp2009-11-281-0/+6
* Doc build: rename general -> web....Hopefully the last major change until a new build system. :( Graham Percival2009-11-214-6/+6
* Docs: Usage: update point-and-click informationPatrick McCarty2009-10-261-2/+2
* Doc build: fix broken xrefs.Graham Percival2009-10-173-7/+7
* Doc: fix missing pitch for \relative, thanks David!Graham Percival2009-10-041-2/+4
* Doc: rename application to usage.Graham Percival2009-09-268-0/+3398