Issue 528: wish: underline markup
http://code.google.com/p/lilypond/issues/detail?id=528
New issue report by wbsoft:
It would be very nice if Lilypond supported underline markup, like:
\markup \underline Piano
Issue attributes:
Status: New
Owner:
Labels: Type-Defec
Issue 527: segfault in bad input
http://code.google.com/p/lilypond/issues/detail?id=527
New issue report by gpermus:
% input is bad, but we still don't want segfaults.
\version "2.11.35"
{ e' \acciaccatura << e'8 \\ cis' >> }
Issue attributes:
Status: Accepted
Owner: gpe
Hans Aberg wrote:
On 7 Dec 2007, at 14:23, Mats Bengtsson wrote:
That's what Graham is trying to do. He voluntarily does a huge job on
both this task
and the document revisions, all on his spare time.
He said that he did not know much about the internals. So the suggestion
is to have somebo
On 7 Dec 2007, at 14:23, Mats Bengtsson wrote:
The problem is that a user which does not know anything about
actual LilyPond debugging is in a rather poor position doing the
actual reduction you want to see unless you tell how. This is
normal in bug reporting. I think you need to have at le
Hans Aberg wrote:
The problem is that a user which does not know anything about actual
LilyPond debugging is in a rather poor position doing the actual
reduction you want to see unless you tell how. This is normal in bug
reporting. I think you need to have at least one developer accessible
t
Hi,
On 7. des. 2007, at 13:44, Mats Bengtsson wrote:
IMHO, this page could (or should) be more visible to users by
providing a link on the front page of lilypond.org. A "How to
submit bugs"-link in the top menu or under "Quick links" could
helpful for bugreporters. Currently you have to dig
On 7 Dec 2007, at 12:20, Valentin Villenave wrote:
The point is: we do *not* have enough people to handle all this (so
this is a very different situation from other places you've been used
to). LilyPond is:
- a huge project
- a large community
- a very small development team, with only volunteer
Erlend Aasland wrote:
Hi Graham et al,
On 7. des. 2007, at 12:19, Graham Percival wrote:
Still, I should have dropped a link to:
http://lilypond.org/web/devel/participating/bugs
IMHO, this page could (or should) be more visible to users by
providing a link on the front page of lilypond.org.
I really don't want to start looking at the website right now. :)
If I'm a complete glutton for punishment, I might start a GWP (grand
website project) after GDP is over. But until then, I'm not even going
to consider thinking about it.
(if anybody else wants to fiddle with the webpages bef
Hi Graham et al,
On 7. des. 2007, at 12:19, Graham Percival wrote:
Still, I should have dropped a link to:
http://lilypond.org/web/devel/participating/bugs
IMHO, this page could (or should) be more visible to users by
providing a link on the front page of lilypond.org. A "How to submit
bug
(oops, I sent it too soon)
2007/12/7, Hans Aberg <[EMAIL PROTECTED]>:
> Sure you have a lot experience with structure of LilyPond bugs, you
> even describe that it several places. If you want to cut down on your
> own time, drop off hints as you did to me first time: "Is this or
> that really nec
Valentin Villenave wrote:
2007/12/7, Hans Aberg <[EMAIL PROTECTED]>:
Sure you have a lot experience with structure of LilyPond bugs, you
even describe that it several places. If you want to cut down on your
own time, drop off hints as you did to me first time: "Is this or
that really necessary?
2007/12/7, Hans Aberg <[EMAIL PROTECTED]>:
> Sure you have a lot experience with structure of LilyPond bugs, you
> even describe that it several places. If you want to cut down on your
> own time, drop off hints as you did to me first time: "Is this or
> that really necessary?" Then people not onl
On 7 Dec 2007, at 02:20, Graham Percival wrote:
Hans Aberg wrote:
When I made the first report, I had no idea what was causing it.
All I knew was that replacing the quadruplet with a rest made it
problem disappear, so it looked to me as though that was the
problem. You, with your broader k
14 matches
Mail list logo
