Simon Albrecht <simon.albre...@mail.de> writes:

>> Am 21.07.2014 19:12, schrieb:
>>> Hi. Here are two small issues:
>>>
>>> 1. When I repeat a chord with q which contains a reminder accidental,
>>> both notes get the accidental:
>>> \version "2.18.2"
>>> \relative c'' {
>>>     <c bes!>2~ q
>>> }
>>> I think (maybe I am wrong) even the reminder should be printed only once.
>>>
>>> 2. This is a special case so the example explains it better than I can.
>>> \version "2.18.2"
>>> \relative c'' {
>>>     \key g \major
>>>     f1~ \break
>>>     | f2 f2
>>> }
>>> The natural here appears two times in the second bar.
>
> please (re-)read <http://lilypond.org/website/bug-reports.de.html>
> concerning the usage of this mailing list. You may ask every question
> you like on lilypond-u...@gnu.org.

Well, two perfectly suitable minimal examples.  Not much wrong with the
use of this list: it _is_ intended for users reporting bugs after
figuring out as much as they can and boiling them down to the
essentials.

Two improvements are possible: obviously checking the issue tracker (but
if you don't figure out the best keywords and/or have a hunch that this
must be in the tracker already, you might easily overlook an issue).
The second is sort-of marginal and not mentioned in our instructions:
using separate bug reports for separate issues might be preferable.
Usually the bug squad can sort this out by filing separate issues based
on the same posting, but

  a) it becomes easier to overlook one of the issues
  b) if there is a followup discussion, it's harder to figure out what
     issue it belongs to.

-- 
David Kastrup

_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to