Carl Sorensen schrieb:
On 1/23/10 3:19 AM, "Marc Hohl" wrote:
Carl Sorensen schrieb:
Marc Hohl has worked on a new G clef that is rotated about 1.5 degrees
clockwise to improve its balance, as suggested by Jan
(see
<http://thread.gmane.org/gmane.comp.gnu.lilypond.deve
Mats Bengtsson schrieb:
Marc Hohl wrote:
Is it ok to do just
cd mf/
make clean
cd ..
make all
since this is faster?
Sure! You may save some typing by doing
make -C mf clean
make
Cool, didn't know about this.
Thanks
Marc
Alexander Kobel schrieb:
[...]
I just noticed that the 'extra-offset won't influence the spacing of
the notes before the bar line. The better property to tweak should be
the right-edge extra space, but this does not work if the line ends
prematurely. (See the attached example.)
Still, like T
HI,
I try to include the varsegno sign (http://codereview.appspot.com/181144)
and Alexander pointed out that moving the compound bar line to the right
works in
nearly every case by
\once \override Staff.BarLine #'space-alist #'right-edge =
#'(extra-space . -1)
but not in combination with \s
Just curious:
In line 205 of scm/output-lib.scm is the definition:
("|s" . (() . "|"))
Is this bar line style used anywhere? I grepped in the sources and
searched in the lsr,
but found nothing...
Marc
___
lilypond-devel mailing list
lilypond-deve
Neil Puttock schrieb:
On 5 February 2010 10:21, Marc Hohl wrote:
Just curious:
In line 205 of scm/output-lib.scm is the definition:
("|s" . (() . "|"))
Is this bar line style used anywhere? I grepped in the sources and searched
in the lsr,
but found nothing...
Alexander Kobel schrieb:
Marc Hohl wrote:
Alexander Kobel schrieb:
I don't really know if I saw the "||-before-break, S-after-break"
combination, but I think it makes sense to offer it since coda parts
are often seperated by double bar lines when the "default" segno
Neil Puttock schrieb:
On 5 February 2010 08:38, Marc Hohl wrote:
Any ideas/hints etc. are highly appreciated!
If you have a spacer rest after \stopStaff, there's no right edge for
the column which the segno's attached to (it's no longer the last
column in the
Hi Alexander,
Alexander Kobel schrieb:
[...]
I just noticed that the 'extra-offset won't influence the spacing of
the notes before the bar line. The better property to tweak should be
the right-edge extra space, but this does not work if the line ends
prematurely. (See the attached exa
Neil Puttock schrieb:
On 9 February 2010 09:20, Marc Hohl wrote:
So \stopStaff does currently not end the line prematurely, but
simply tells lilypond not to draw the staff lines any further, right?
Yes. If it did the former, you'd get an automatic line break, and
you'
Alexander Kobel schrieb:
[...]
So, what do I think is useful? In the optimum, we should have the
following combinations:
Diving into your proposals, I have some comments:
On a line break:
- "|S" ("|" end of line, "S" begin of line)
- "S|" ("S" only end of line)
Ok.
- "||S" ("||" end of
Hello,
I am still working on a proper way to include the varsegno sign (issue
#659).
Displaying the varsegno itself with various combinations (repeat signs etc.)
works already, but for span-bar.cc, I'll have to remove the varsegno
sign itself but
the spacing should be the same, so basically, I
Ian Hulin schrieb:
[...]
Secondly, what I had in mind was this kind of thing:
* \dalsegno and \dacapo - both of these start off a segno/dacapo
section. I know it's a bit weird that the \dacapo command would
have to be at the start of the score, but I think it would be
ben
Marc Hohl schrieb:
[...]
Are you sure about "S:|" and "|:S" ?
Ah, I think I understand - but I'll use ":|S." and ".S|:" for situations
where the segno *and* the repeat sign
should be placed on the same line.
Marc
_
Hello all,
I have uploaded some enhancements due to Alexander Kobel's proposals.
The first attempt to upload broke on my console with some error messages,
so I did it again - now I see that I uploaded two identical versions.
And furthermore, the changes to scm/tablature.scm which Carl had pushed
Ian Hulin schrieb:
Hi Marc,
On 15/02/10 18:32, Marc Hohl wrote:
Ian Hulin schrieb:
[...]
Secondly, what I had in mind was this kind of thing:
* \dalsegno and \dacapo - both of these start off a segno/dacapo
section. I know it's a bit weird that the \dacapo command
Carl Sorensen schrieb:
On 2/15/10 12:33 PM, "Marc Hohl" wrote:
Hello all,
I have uploaded some enhancements due to Alexander Kobel's proposals.
The first attempt to upload broke on my console with some error messages,
so I did it again - now I see that I uploaded two ide
Patrick McCarty schrieb:
Hi Marc,
On 2010-02-15, Marc Hohl wrote:
I have
Stencil segno = Font_interface::get_default_font (me)->find_by_name
("scripts.varsegno");
How can I get the width of the glyph? Or alternatively, can I get
the width of the stencil defined as above?
carl.d.soren...@gmail.com schrieb:
Looks good to me, with the exception of the hardcoded value stuff.
Thanks,
Carl
http://codereview.appspot.com/181144/diff/4008/5018
File lily/bar-line.cc (right):
http://codereview.appspot.com/181144/diff/4008/5018#newcode242
lily/bar-line.cc:242: m.add_at
David Kastrup schrieb:
Marc Hohl writes:
After reading through the other posts, I think that overloading
\repeat would not cover *all* possible
cases. On the other hand, there should be *one* consistent way of
doing any kind of repeats.
David's comparison with goto-like structures
n.putt...@gmail.com schrieb:
Hi Marc,
LGTM, though I still think this is a lot of effort for a very obscure
and little-used symbol.
Perhaps it is little-used because it was missing in lilypond? ;-)
Or do you think this is just too much and we should forget about it all?
(I don't hope so, becau
Hello,
I am currently engraving a piece and wanted to use the 'q' chord
repetition for the first
time. I have standard notation and tablature combined and since all
articulation information
is removed from the content of 'q', the string information has also
gone, so the tablature
is wrong. Is
Patrick Schmidt schrieb:
Hi Marc,
Hello,
I am currently engraving a piece and wanted to use the 'q' chord
repetition for the first
time. I have standard notation and tablature combined and since all
articulation information
is removed from the content of 'q', the string information has also
Hello Nicolas,
Nicolas Sceaux schrieb:
Le 27 févr. 2010 à 11:07, Marc Hohl a écrit :
the 'q' functionality has changed after 2.13.11 was released. Nicolas Sceaux
pushed a patch
to remove multiple fingerings etc., but the string information should be
copied, IMHO.
Precise
Nicolas Sceaux schrieb:
Le 28 févr. 2010 à 10:18, Marc Hohl a écrit :
This solution might be very useful for tablature users, so I propose to store
the
definition for tab-repeat-chord in scm/tablature.scm and provide a
user-friendly shortcut for switching to tab-repeat-chord, perhaps
Hello,
Nicolas Sceaux has provided a function to store the string information
in a repeated chord for better use in tablature. I just put the definition
into the right place and enhanced ly/property-init.ly for switching
more easily to the tab repeat style.
Please have a look at
http://coderevi
nicolas.sce...@gmail.com schrieb:
http://codereview.appspot.com/224082/diff/1/3
File ly/chord-repetition-init.ly (right):
http://codereview.appspot.com/224082/diff/1/3#newcode51
ly/chord-repetition-init.ly:51: #(define-public (tab-repeat-chord
previous-chord location duration articulations)
It
Marc Hohl schrieb:
n.putt...@gmail.com schrieb:
Hi Marc,
LGTM, though I still think this is a lot of effort for a very obscure
and little-used symbol.
[...]
Should the new segno sign be included in the documentation?
If yes, where?
Apart from that, are there any further objections to this
Nicolas Sceaux schrieb:
Le 1 mars 2010 à 10:00, Marc Hohl a écrit :
nicolas.sce...@gmail.com schrieb:
http://codereview.appspot.com/224082/diff/1/3
File ly/chord-repetition-init.ly (right):
http://codereview.appspot.com/224082/diff/1/3#newcode51
ly/chord-repetition-init.ly:51
Marc Hohl schrieb:
Nicolas Sceaux schrieb:
Le 1 mars 2010 à 10:00, Marc Hohl a écrit :
nicolas.sce...@gmail.com schrieb:
http://codereview.appspot.com/224082/diff/1/3
File ly/chord-repetition-init.ly (right):
http://codereview.appspot.com/224082/diff/1/3#newcode51
ly/chord-repetition
Jonathan Kulp schrieb:
[...]
There is a reason for this warning, I'm sure. (I think I'm the one
who put it there). Before deleting it, try using the string number
orientation command and see if it has any effect on the string
number when it's not inside a chord construct.
Nicolas Sceaux schrieb:
Le 1 mars 2010 à 10:00, Marc Hohl a écrit :
nicolas.sce...@gmail.com schrieb:
http://codereview.appspot.com/224082/diff/1/3
File ly/chord-repetition-init.ly (right):
http://codereview.appspot.com/224082/diff/1/3#newcode51
ly/chord-repetition-init.ly:51
Nicolas Sceaux schrieb:
Le 1 mars 2010 à 20:24, Marc Hohl a écrit :
Nicolas Sceaux schrieb:
Shouldn't there be a few words of explantion about using q and
\tabChordRepetition somewhere in 2.4.1 "Common notation for fretted
strings"?
Done. I hope it is
Graham Percival schrieb:
On Mon, Mar 1, 2010 at 9:30 AM, Marc Hohl wrote:
Should the new segno sign be included in the documentation?
If yes, where?
In the feta font (I think that's included/font-table.ly), and in NR
1.2.5 rehearsal marks, in the example wi ththe other segno
Neil Puttock schrieb:
On 2 March 2010 11:25, Marc Hohl wrote:
Thanks. Can you please push it? I am not allowed to...
I'm happy to push, but there seems to be a problem: the default
repetition function is the tablature version; I think this is due to
the parser evaluating the s
Marc Hohl schrieb:
Neil Puttock schrieb:
On 2 March 2010 11:25, Marc Hohl wrote:
Thanks. Can you please push it? I am not allowed to...
I'm happy to push, but there seems to be a problem: the default
repetition function is the tablature version; I think this is due to
the p
Graham Percival schrieb:
On Tue, Mar 02, 2010 at 12:29:09PM +0100, Marc Hohl wrote:
Graham Percival schrieb:
In the feta font (I think that's included/font-table.ly), and in NR
1.2.5 rehearsal marks, in the example wi ththe other segno signs.
I didn't touch inc
Hello all,
it seems that explicit string information has to be used within chord
constructs
for *every* note, otherwise lilypond shows errors.
In the following example the second bar gives an error, because lilypond
uses the
"\2" for the first note within < ... >, this is the g which cannot b
Carl Sorensen schrieb:
On 3/14/10 12:14 PM, "Marc Hohl" wrote:
Hello all,
it seems that explicit string information has to be used within chord
constructs
for *every* note, otherwise lilypond shows errors.
In the following example the second bar gives an error, because lilypon
n.putt...@gmail.com schrieb:
Hi Marc,
Here are a few more comments for you.
Cheers,
Neil
http://codereview.appspot.com/224082/diff/1012/17
File Documentation/notation/fretted-strings.itely (right):
http://codereview.appspot.com/224082/diff/1012/17#newcode256
Documentation/notation/fretted-s
Carl Sorensen schrieb:
[...]
Well, I'm pretty sure I understand you. I think perhaps you misunderstood
my reply. I'm not saying that the samples you made were wrong; they were in
fact correct if we're willing to to accept string-number events following a
chord.
I was not sure about this, t
Marc Hohl schrieb:
[...]
Is the segno patch ready to be applied, or did I miss something?
I don't want to annoy you, but if there is some more work I should
do to improve the patch, let me know ... on the other hand,
if it is ready now, don't hesitate to push it
Hello,
I found a little mistake in the snippets; here is a patch to correct it.
Marc
From 872a719d82e800e958339aa6faceb2baf93735a2 Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: Tue, 30 Mar 2010 21:27:00 +0200
Subject: [PATCH] Correction: no negative fret numbers in snippet
---
.../new
ng directory `/home/marc/git/lilypond/Documentation'
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory `/home/marc/git/lilypond'
make: *** [doc-stage-1] Fehler 2
Any hints are appreciated.
Marc
From 61a8189322260d04426c5fb1bd45e45f38ad0040 Mon Sep 17 00:00:00 2001
From: Marc Ho
While waiting for make doc to settle down, I found issue 1037
and hopefully fixed it.
Marc
From e120a73a45b41cead6acbc381fc1cb547bf8fbea Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: Tue, 30 Mar 2010 22:46:25 +0200
Subject: [PATCH] Issue 1037: Links to old manuals
---
Documentation/web
Graham Percival schrieb:
On Tue, Mar 30, 2010 at 10:45:36PM +0200, Marc Hohl wrote:
/home/marc/git/lilypond/Documentation/out/notation/fretted-strings.texi:32:
I c
an't find file `c6/lily-4f6e19ca-systems.texi'.
@temp ->@input c6/lily-4f6e19ca
3, of course) as a separate
website, I think two separate lists don't make sense ;-)
Marc
Cheers,
- Graham
On Tue, Mar 30, 2010 at 10:49:19PM +0200, Marc Hohl wrote:
While waiting for make doc to settle down, I found issue 1037
and hopefully fixed it.
Graham Percival schrieb:
On Wed, Mar 31, 2010 at 12:01 AM, Marc Hohl wrote:
diff --git a/Documentation/notation/fretted-strings.itely
@@ -1470,13 +1470,33 @@ text markup.
+...@lilypond[quote,ragged-right,verbatim]
+music = \relative c' {
+ < a\3 \deadNote c\2 a'\1 >4
+ <
Graham Percival schrieb:
Thanks, pushed. Wow, that's 2 Critical issues that you've fixed
today. Great job!
:)
Marc
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
looks better IMHO.
Marc
Cheers,
- Graham
>From c494888746b97a2c1a63f1d913635dc9264fbe6e Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: Thu, 1 Apr 2010 08:18:11 +0200
Subject: [PATCH] Issue 1046: better \deadNote example
---
Documentation/notation/fretted-strings.itely |8
Graham Percival schrieb:
On Tue, Mar 30, 2010 at 09:50:49AM +0200, Marc Hohl wrote:
Marc Hohl schrieb:
[...]
Is the segno patch ready to be applied, or did I miss something?
I don't want to annoy you, but if there is some more work I should
do to improve the patch, let me
: Marc Hohl
Date: Thu, 8 Apr 2010 09:09:56 +0200
Subject: [PATCH] Doc: adding palm mute to fretted-strings.itely
---
Documentation/notation/fretted-strings.itely | 27 ++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/Documentation/notation/fretted
ight want to double-check these
things.
Thanks for your remarks!
Marc
>From fa06a8f82993386eca0c5c3b72e11c7c914beb70 Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: Thu, 8 Apr 2010 17:02:16 +0200
Subject: [PATCH] Doc: shortened palm mute example
---
Documentation/notation/fretted-strings
Marc Hohl schrieb:
Graham Percival schrieb:
[...]
Also, we generally try to keep the output down to one line. Does the
second bar really add anything to the example? Could you condense the
example down to 3 bars instead of 4?
I just send the patch once more as a remainder to shorten the
I found some typos and translation errors in the German documentation
of the current development version.
Should I create a patch to correct them, or should I inform the
current translator about my observations - or both?
Marc
___
lilypond-devel mail
David Kastrup schrieb:
[...]
So how about the ultimate tweak: using a separate engraver? We can't
have overlapping slurs with a single engraver, for example. But if we
write something like
and use @1 with the scope of a tweak, and let it use the engraver of
subvoice 1 (a subvoice having it
Carl Sorensen schrieb:
On 5/7/10 12:36 AM, "Marc Hohl" wrote:
I found some typos and translation errors in the German documentation
of the current development version.
Should I create a patch to correct them, or should I inform the
current translator about my observations
Carl Sorensen schrieb:
On 5/7/10 12:36 AM, "Marc Hohl" wrote:
I found some typos and translation errors in the German documentation
of the current development version.
Should I create a patch to correct them, or should I inform the
current translator about my observations
David Kastrup schrieb:
[...]
diff --git a/Documentation/de/notation/fretted-strings.itely
b/Documentation/de/notation/fretted-strings.itely
index ecbf682..b181026 100644
--- a/Documentation/de/notation/fretted-strings.itely
+++ b/Documentation/de/notation/fretted-strings.itely
@@ -19,27 +19,27
David Kastrup schrieb:
[...]
I am not actually all too sure that this distinction is not merely a red
herring: tabulature, just like standard notation, assumes playing in a
12-note room. Whether or not there are explicit frets does not make a
significant difference here. Most certainly a player
David Kastrup schrieb:
[...]
I really now _must_ find some other hairs to split, or I'll get all
excited.
Just to save more hairs from being split, I reworked my patch ;-)
Marc
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.
Till Paala schrieb:
Am 09.05.10 22:32, schrieb Marc Hohl:
Carl Sorensen schrieb:
On 5/7/10 12:36 AM, "Marc Hohl" wrote:
I found some typos and translation errors in the German documentation
of the current development version.
Should I create a patch to correct them, or should I
Marc Hohl schrieb:
Till Paala schrieb:
[...]
Hi,
this looks great, good that somebody with better expertise corrects
my mistakes :-) Should I apply or will you apply this youself?
Hi Till,
I can't push. Here is a reworked version - if there are no further
objections, it would be gre
t out if I had commit access,
just fix it up after it got upstream.
Thanks for the hint - I hope everything is ok now ...
Marc
>From e2d3968a222c9bf85007d9df143c3e611ef96002 Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: Sun, 9 May 2010 21:26:36 +0200
Subject: [PATCH] Doc: [de] Corre
-Eluze schrieb:
after some more reflection and searching for "Bundinstrument" with google (12
results in opera, 32 in firefox, there is even a wikipedia article raising
the question, if a new category "Bundinstrumente" should be created! see:
http://de.wikipedia.org/wiki/Portal_Diskussion:Musik/
ves me the attached grace-start result which resembles the 2.13.17
result presented in the bug tracker.
What should we do about it?
I'd suggest we check with Marc Hohl to see what the intent of that
change was. I suspect that it was an attempt to change how \bar "||" is
al
fine with the segno sign the way it is,
we don't need a narrower double bar in combination with the segno sign.
I hope that I cleaned up the mess I introduced with the segno stuff.
Thanks,
Marc
From 936dd7d3c0794d950a1046e76d5ce273014fcc7b Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: F
Neil Puttock schrieb:
On 16 May 2010 09:35, Marc Hohl wrote:
Now, I have created a patch which
1) restores the former width of the double bar line
2) works properly with the segno sign
\bar ".S|:" is swapped round. Is this what you want?
Of course not - thanks for the
Till Paala schrieb:
Am 11.05.10 21:24, schrieb Marc Hohl:
Thanks for the hint - I hope everything is ok now ...
Marc
Sorry, I pushed an earlier patch already (9th of may) onto the
translation branch which is not yet merged with master (resulting
commitish was
Mark Polesky schrieb:
Marc Hohl wrote:
I did
git remote add -ft lilypond/translation ...
as described here; git complains with
Usage: git remote add [-f] [-t track]* ...
So I replaced "-ft" with "-f -t" ...
Now git complains with
remote origin already exists
What a
John Mandereau schrieb:
Hi Marc,
Il giorno mar, 18/05/2010 alle 18.05 +0200, Marc Hohl ha scritto:
I did
git remote add -ft lilypond/translation -m lilypond/translation origin
git://git.sv.gnu.org/lilypond.git/
as described here; git complains with
Usage: git remote add [-f] [-t track
Hello all,
after some discussions on the frog list I created a patch improving the
use of the 'transparent property. As Neil suggested, an invisible grob
should have no whiteout, and this is what the patch does.
After grepping through the code, I don't think that this will influence the
overall
Carl Sorensen schrieb:
Marc,
The code looks great to me. Please email me a patch (so it will have you as
the author) and I will push it.
Here it is.
Thank you,
Marc
Thanks,
Carl
On 6/19/10 3:11 AM, "Marc Hohl" wrote:
Hello all,
after some discussions on the frog list
n.putt...@gmail.com schrieb:
LGTM.
http://codereview.appspot.com/1681043/diff/1/2
File lily/grob.cc (right):
http://codereview.appspot.com/1681043/diff/1/2#newcode126
lily/grob.cc:126: bool grob_transparent = to_boolean (get_property
("transparent"));
This is a bit fussy. `transparent' will d
n.putt...@gmail.com schrieb:
On 2010/06/21 19:06:52, marc wrote:
Now I *must* overlook the obvious, because the fret numbers still
disappear,
even if they are not tied together.
Remember what I said about 'layer?
Yes, of course, but since the HarmonicParenthesesItem *did* work before
witho
carl.d.soren...@gmail.com schrieb:
Looks pretty good. I have a few comments about things that seem to be
unnecessarily specific to harmonics.
Thanks,
Carl
http://codereview.appspot.com/1669041/diff/26001/27003
File scm/define-grob-interfaces.scm (right):
http://codereview.appspot.com/16690
Carl Sorensen schrieb:
[...]
http://codereview.appspot.com/1669041/diff/26001/27004#newcode130
scm/define-grob-properties.scm:130: (bracket-width ,number? "Width of
the harmonic angle bracket.")
Why do we need bracket-width? Why can't we just use the pre-existing
width property?
Hm, Nei
Carl Sorensen schrieb:
On 6/30/10 1:48 AM, "Marc Hohl" wrote:
Carl Sorensen schrieb:
[...]
http://codereview.appspot.com/1669041/diff/26001/27004#newcode130
scm/define-grob-properties.scm:130: (bracket-width ,number? "Width of
the harmonic angle bracket.&q
n.putt...@gmail.com schrieb:
On 2010/06/30 07:48:12, marc wrote:
So I tried to extend the parenthesize-stencil function in
scm/stencil.scm.
It compiles without error, but the regression file is cluttered up.
I can't test this. Would you mind uploading another version here which
includes al
Hello all,
after about half a year I have to admit that I don't have a) the time
and b) the programming skills to implement bends in lilypond[1]. Sorry.
Bends are important for guitarists, so I offer 75$ for this issue and
I am posting to the tablature list, because perhaps someone else there
is
Dean Radcliffe schrieb:
I added the following to
http://code.google.com/p/lilypond/issues/detail?id=687
I think this is a way to think about - could anyone suggest to a
novice schemer how this might be done ??
Hello Dean,
I thought about this issue some time ago. There is a file articulate.l
Federico Bruni schrieb:
Hi Marc,
Il giorno sab, 24/07/2010 alle 20.19 +0200, Marc Hohl ha scritto:
Hello all,
after about half a year I have to admit that I don't have a) the time
and b) the programming skills to implement bends in lilypond[1]. Sorry.
it's a pity... anywa
, 24/07/2010 alle 20.19 +0200, Marc Hohl ha scritto:
Hello all,
after about half a year I have to admit that I don't have a) the time
and b) the programming skills to implement bends in lilypond[1]. Sorry.
it's a pity... anyway, you did a great job so far!
as a matter
Dmytro O. Redchuk schrieb:
On Mon 26 Jul 2010, 11:25 Marc Hohl wrote:
Graham Percival schrieb:
Bug Squad: two bounty offers in this email; please add to tracker.
Three offers - 2x 75$, 1x 10 €
Added as 1196:
http://code.google.com/p/lilypond/issues/detail?id=1196
Please
.
But then there are two rests showing, and I would love to have only a
whole (time sign. is 3/2)
Any suggestions?
I prepared a patch, see attachment; can somebody push it?
Thanks in advance
Marc
---
Viktor
>From c025613fd91175371591d4242a1a40bdf12cfa4b Mon Sep 17 00:00:00 2001
From: Marc
Neil Puttock schrieb:
On 1 September 2010 16:36, Marc Hohl wrote:
I prepared a patch, see attachment; can somebody push it?
\tabFullNotation ?
Oh yes, of course ...
Done.
Marc
Cheers,
Neil
From 6a9ec63f61dc49a98a906c854331750d253f78e0 Mon Sep 17 00:00:00 2001
From: Marc
Hello all,
lilypond handles tied notes within a TabStaff (almost) correctly, but I
ran into problems
with combinations of tie/slur or tie/glissando combinations.
Consider this example:
\version "2.13.33"
test = { d4 ~ d ( e2 ) | d4 ~ d \glissando e2 | }
\score {
<<
\new Staff { \clef "G
Hello all,
IIUC, \override grob #'foo = #bar
is more or less the same as
(ly:grob-set-property! grob foo bar)
Is there a scheme equivalent for
\once \override Grob #'foo = #bar ?
Thanks in advance!
Marc
___
lilypond-devel mailing list
lilypond-deve
Alexander Kobel schrieb:
On 2010-09-15 10:09, Marc Hohl wrote:
Hello all,
IIUC, \override grob #'foo = #bar
is more or less the same as
(ly:grob-set-property! grob foo bar)
Is there a scheme equivalent for
\once \override Grob #'foo = #bar ?
Hi, Marc,
if _I_ understand corr
Hello,
the following patch should hopefully remove problems in tablature
when a tie is followed by either a slur or a glissando.
http://codereview.appspot.com/2191042
Thanks,
Marc
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.g
carl.d.soren...@gmail.com schrieb:
Looks good to me. Just a comment on the name of the new property to be
added to details.
Thanks,
Carl
Hello Carl,
http://codereview.appspot.com/2191042/diff/1/scm/define-grobs.scm
File scm/define-grobs.scm (right):
http://codereview.appspot.com/219104
n.putt...@gmail.com schrieb:
Hi Marc,
Hello Neil,
In hide-tab-note-head, you end up setting properties on bounds which
aren't noteheads (i.e., for broken bounds, the ties are bound by a
NonMusicalPaperColumn); till now you've got away with it, since the
properties being set were from the grob-
n.putt...@gmail.com schrieb:
On 2010/09/17 07:01:40, marc wrote:
TO be honest, I don't understand what you mean here.
Add
#(ly:set-option 'check-internal-types)
to your snippet below.
Two of the bounds aren't TabNoteHeads; these are the left bounds of the
ties following a break.
Ah, ok,
rc
>From 3d36950e8cadf69f1db169213e4a779519d145be Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: Thu, 23 Sep 2010 07:54:09 +0200
Subject: [PATCH] Doc: mention tablature changes in changes.tely.
---
Documentation/changes.tely |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/c
Graham Percival schrieb:
Here's an update on the release plans. These are not cast in
stone; if you have a thoughtful objection or suggestion, I'm
willing to change things.
1) 2.13.34, "alpha test" has been released.
2) website has been switched over. At first glance, I think I can
close issue
While working with the new spacing settings, I think I found
some typos.
In general, the names of variables should not be translated within
code examples, otherwise cut&paste does not work anymore.
Marc
From eab315b158dc295fd1234eae4966e822e32709af Mon Sep 17 00:00:00 2001
From: Marc Hohl
Graham Percival schrieb:
On Fri, Sep 24, 2010 at 10:59:18AM +0200, Marc Hohl wrote:
Graham Percival schrieb:
2) website has been switched over. At first glance, I think I can
close issue 1244 now, but I want to double-check and wait for
feedback.
The menu bar is misplaced here
Hello all,
here is a small patch that provides proper support for text spanners
in combination with \tabFullNotation.
Greetings,
Marc
From 9ca52bd5be89a5e03b7a4c930154081c1c84f9d5 Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: Fri, 1 Oct 2010 08:36:45 +0200
Subject: [PATCH] tablature
Marc Hohl schrieb:
Hello all,
here is a small patch that provides proper support for text spanners
in combination with \tabFullNotation.
... or is anything wrong with it?
(I know, tablature is not important for most users, but still ... :-)
Marc
Greetings,
Marc
Am 18.10.2010 22:39, schrieb Werner LEMBERG:
Can you open an issue directly on the tracker and post your
attachments there?
Done. It's issue #1335.
Hello Werner,
I did the faulty varsegno sign. I read the tracker and wanted to
reproduce your observations, but I am unable to ru
101 - 200 of 651 matches
Mail list logo
