From 55ac6f7e56bcd42a6464a35378f02046aee4d2f7 Mon Sep 17 00:00:00 2001 From: Janek Warchol Date: Mon, 4 Jul 2011 21:39:28 +0200 Subject: [PATCH] an example of minimal example for some people it's not clear enough how tiny a tiny example should be. So i used a recently discussed example to illustrate it, and also changed some wording and style. --- Documentation/css/lilypond-website.css | 1 + Documentation/web/community.itexi | 63 ++++++++++++++++++++++++++------ 2 files changed, 52 insertions(+), 12 deletions(-) diff --git a/Documentation/css/lilypond-website.css b/Documentation/css/lilypond-website.css index a6f6f9b..e5bf192 100644 --- a/Documentation/css/lilypond-website.css +++ b/Documentation/css/lilypond-website.css @@ -894,6 +894,7 @@ div.color4 h3 { .example { position: relative; left: -2.5em; + text-align: left; } .h-scroll-auto { diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi index d6918d1..a5d4784 100644 --- a/Documentation/web/community.itexi +++ b/Documentation/web/community.itexi @@ -270,7 +270,7 @@ guidelines for @ref{Bug reports}.} @divClass{column-center-top} @subheading What are @qq{Tiny examples}? -A tiny example is an example from which nothing can be removed. +A tiny example is an example from which @strong{nothing} can be removed. @divEnd @divClass{column-left-bottom} @@ -284,12 +284,12 @@ The simpler the example is, the quicker potential helpers can understand it and help you. @item -A simple example demonstrates that you have put effort towards +A tiny example demonstrates that you have put effort towards solving the problem yourself. When people send huge portions of -input, it looks like they don't care how if we help them or not. +input, it looks like they don't care if we help them or not. @item -Creating a tiny example forces you to understand what is +Creating a tiny example helps you to understand what is happening. Many false problem reports can be avoided by attempting to create a tiny example; if you cannot replicate a @qq{bug} in a tiny example, then the problem was probably an @@ -302,39 +302,78 @@ insufficient understanding of LilyPond, not an actual bug! @divClass{column-right-bottom} address@hidden How do I create them? address@hidden How to create them? @divClass{keep-bullets} @itemize @item -Include the \version number. +Include the @code{\version} number. @item Make it small! Examples about spacing or page layout might require many bars of music, but most issues can be reproduced -using only a single measure. +using less than a single measure. @item When trying to create an example, try commenting out @w{(@code{%} -or @address@hidden @dots{} address@hidden)} sections of your file. If you can -comment something while still demonstrating the main idea, then -remove the commented-material! +or @address@hidden @dots{} address@hidden)} sections of your file. If you +can comment something while still demonstrating the main idea, +then remove the commented-material. @item -Avoid using complicated notes, keys, or time signatures, unless +Avoid using complicated notes, keys or time signatures, unless the bug is about the behavior of those items. @item Do not use @code{\override} or @code{\set} commands unless the bug -is about those particular commands. +is about those specific commands. + address@hidden +Optionally, attach an image showing the desired graphical output. @end itemize @divEnd @divEnd address@hidden address@hidden How tiny should they be? + +Is the code below a minimal example? + address@hidden +\version "2.14.1" +\include "english.ly" + +\score @{ + \new Staff @{ + \key d \major + \numericTimeSignature + \time 2/4 + 16 8. + %% Here: the tie on the D's looks funny + %% Too tall? Left-hand endpoint is not aligned with the B tie? + ~ + 8 [ ] + @} address@hidden address@hidden example +Well, it is not very big, but a truly minimal example is here: + address@hidden +\version "2.14.1" address@hidden + % middle tie looks funny here: + 8. ~ 8 address@hidden address@hidden example + +Very few tiny examples exceed 10 lines of code - +quite often 4 lines are enough to demonstrate the problem! + address@hidden @node Bug reports -- 1.7.0.4