Updates:
Owner: ---
Comment #7 on issue 370 by pnorcks: slur #'positions silently does not
place slur at actual position
http://code.google.com/p/lilypond/issues/detail?id=370
(No comment was entered for this change.)
Attachments:
foo.preview.png 4.5 KB
_
It's true that nobody actually wants this feature added -- but
OTOH, I'm reluctant to mark `close' something which isn't actually
resolved.
We have plenty of other postponed feature requests, so I'd rather
leave it as one of those. If we were in the middle of a huge
issue-closing push, then I wou
I prefer to close this issue instead noone actually indicated they
desparately needed it.
2008/2/8, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Issue 370: slur #'positions silently does not place slur at actual position
> http://code.google.com/p/lilypond/issues/detail?id=370
>
--
Han-Wen Nienhuy
Issue 370: slur #'positions silently does not place slur at actual position
http://code.google.com/p/lilypond/issues/detail?id=370
Comment #6 by gpermus:
There seems to be some confusion about this.
FEATURE REQUEST: make
\override Slur #'positions = #'(30 . 30)
actually place slurs in th
Issue 370: slur #'positions silently does not place slur at actual position
http://code.google.com/p/lilypond/issues/detail?id=370
Comment #5 by tdanielsmusic:
The following has been added to the Tweaks section in the LM:
Note, though, that slurs and phrasing slurs cannot be repositioned by
ar
Issue 370: slur #'positions silently does not place slur at actual position
http://code.google.com/p/lilypond/issues/detail?id=370
Comment #4 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Type-Enhancement Type-Documentation
--
You received thi
Issue 370: slur #'positions silently does not place slur at actual position
http://code.google.com/p/lilypond/issues/detail?id=370
Comment #3 by gpermus:
Technically, "something that needs some documentation" is also a bug.
:) Warning
added to git.
--
You received this message because you
