LGTM
Thanks for this patch!
Marc
Am 28.04.2014 11:35, schrieb thomasmorle...@gmail.com:
Reviewers: ,
Message:
Please review
Description:
corrects typo in bar-line.scm
issue 3908
Missing space in (define-bar-line ":|]" ":|]" #f " |") caused bad
visual output of VoltaBracket.
Changed to (defi
Am 24.05.2014 08:33, schrieb d...@gnu.org:
https://codereview.appspot.com/96570043/diff/1/ly/music-functions-init.ly
File ly/music-functions-init.ly (right):
https://codereview.appspot.com/96570043/diff/1/ly/music-functions-init.ly#newcode646
ly/music-functions-init.ly:646: \override Beam.beam
Am 01.06.2014 08:54, schrieb James:
On 31/05/14 22:44, bobr...@centrum.is wrote:
- Original Message -
From: "James"
To: bobr...@centrum.is
Cc: "lilypond-devel"
Sent: Friday, May 30, 2014 3:16:53 PM
Subject: Re: varC clefs in 2.19
On 30/05/14 14:12, bobr...@centrum.is wrote:
- Or
Am 22.06.2014 14:57, schrieb d...@gnu.org:
On 2014/06/22 12:45:47, janek wrote:
https://codereview.appspot.com/108110044/diff/60001/Documentation/notation/vocal.itely
File Documentation/notation/vocal.itely (right):
https://codereview.appspot.com/108110044/diff/60001/Documentation/notation/
Am 22.06.2014 16:00, schrieb David Kastrup:
Marc Hohl writes:
Am 22.06.2014 14:57, schrieb d...@gnu.org:
Start of the coffee canon?
https://www.youtube.com/watch?v=8PN23MIqoLY> Though somewhat
boring rhythmically.
I was about to propose capital letters like 'A'
Hi list,
in the following example, I want to align the FretBoards to the
bar lines. Now they are centered over the first beat in each measure.
TIA,
Marc
---
\version "2.19.0"
\paper {
indent = 0
ragged-right = ##f
}
frets = {
< d'\3 g'\2 b'\1 >1 | < g\4 cis'\3 e'\2 > | < cis'\3 fis'\2
Am 04.07.2014 09:46, schrieb Marc Hohl:
Hi list,
sorry, wrong list ... I re-posted this question on -user, sorry for the
noise.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 06.07.2014 13:52, schrieb thomasmorle...@gmail.com:
On 2014/07/06 06:46:53, Mark Polesky wrote:
Hi, I'm proposing to get rid of the BarLine.thin-kern property with
this patch,
so if you're opposed, let me know.
You can see my comments/rationale here:
http://code.google.com/p/lilypond/iss
Am 08.07.2014 02:17, schrieb Paul Morris:
Thomas Morley-2 wrote
But *do* we need two different variables which then are used with
exactly the
same value?
Do we need the option to change the distance of the segno double bar
line?
I'd say yes.
I'm always against loosing functionality, and dele
Am 08.07.2014 20:20, schrieb markpole...@gmail.com:
marc wrote:
OK, but 'thin-kern does not seem to be an
appropriate name for this property anymore IMHO.
How about 'segno-kern? (patch updated accordingly)
Much better!
___
lilypond-devel mailin
Am 12.07.2014 14:44, schrieb Janek Warchoł:
Hi all,
[...]
Unfortunately i'm busy on that weekend :(
Is there noone else interested?
Basically, I am interested as well, but I have a concert on August 30th :-(
Marc
Janek
___
lilypond-devel mailing
Am 12.07.2014 19:58, schrieb Mike Solomon:
On Jul 12, 2014, at 3:48 PM, Marc Hohl wrote:
[...]
I’d love to meet up but I am in gig mode as well towards the end of the summer
and we have a newborn in the house.
Hey, congratulations! The nights are quiet, yes? ;-)
All the best for all of
Am 16.07.2014 21:18, schrieb Mark Polesky:
On Wed, Jul 16, 2014 at 12:01 PM, Paul Morris wrote:
The best ideas I've come up with would be either "resize" or "scale".
Since
scale could be confused with the musical meaning of scale, I think resize
is
the better option of these two.
\resizeSta
Am 18.07.2014 01:59, schrieb David Nalesnik:
Hi Mark,
On Thu, Jul 17, 2014 at 2:34 PM, mailto:markpole...@gmail.com>> wrote:
While I have your attention, there was some discussion on the mailing
list about changing \magnifyMusic and \magnifyStaff to \resizeMusic and
\resizeStaff.
Am 30.07.2014 um 17:34 schrieb Phil Holmes:
- Original Message - From:
To:
Cc: ;
Sent: Wednesday, July 30, 2014 3:57 PM
Subject: Re: Phase two of pruning snippets/new (issue 113670043 by
philehol...@googlemail.com)
https://codereview.appspot.com/113670043/diff/20001/Documentation/s
Am 03.11.2014 um 19:26 schrieb Dan Eble:
If the simple-fraction components of a compound time signature respected the
time signature style, would that qualify as useful or as undesirable? For
example,
2 + 32 + 3 4
- + C vs.- + -
4
Am 04.11.2014 um 07:48 schrieb David Kastrup:
Dan Eble writes:
If the simple-fraction components of a compound time signature respected the
time signature style, would that qualify as useful or as undesirable? For
example,
2 + 32 + 3 4
- + C vs.- +
Am 04.11.2014 um 15:18 schrieb Hans Aberg:
On 4 Nov 2014, at 10:49, Marc Hohl wrote:
Am 04.11.2014 um 07:48 schrieb David Kastrup:
Dan Eble writes:
If the simple-fraction components of a compound time signature respected the
time signature style, would that qualify as useful or as
Am 04.11.2014 um 12:55 schrieb Dan Eble:
2 + 32 + 3 4
- + C vs.- + -
44 4
Undesirable in my book.
I overlooked the fact that the denominators are the same, so
either
[…]
I'd rather not use the C symbol in these cases.
Am 07.01.2015 um 22:27 schrieb Ricardo Wurmus:
Hi,
a while ago I wrote a scheme engraver that outputs something close to
StaffTab notation. StaffTab notation is a mix of standard two staff
notation with a few elements of tabulature tailored to the free hands
methods of playing the Chapman Stick
Hi list,
the appearance of cautionary tab note heads differs from parenthesized
ones, see the output of
\version "2.19.0"
\new TabStaff { \parenthesize c4 c~ \bar "" \break c2 }
I think this is a bug. Should I raise an issue for that?
Marc
___
li
Am 19.01.2015 um 14:51 schrieb James:
On 09/01/15 09:25, Marc Hohl wrote:
Hi list,
the appearance of cautionary tab note heads differs from parenthesized
ones, see the output of
\version "2.19.0"
\new TabStaff { \parenthesize c4 c~ \bar "" \break c2 }
I think this is a
Am 19.01.2015 um 19:23 schrieb James:
On 19/01/15 17:43, David Kastrup wrote:
Marc Hohl writes:
Am 19.01.2015 um 14:51 schrieb James:
On 09/01/15 09:25, Marc Hohl wrote:
Hi list,
the appearance of cautionary tab note heads differs from parenthesized
ones, see the output of
\version
Am 29.01.2015 um 19:44 schrieb pkx1...@gmail.com:
Can someone give me the translation in German for:
"PDF files generated will be much larger than normal (due to little or
no font optimization). However, if two or more PDF files are included
within pdftex, xetex or luatex documents they can then
Am 30.01.2015 um 09:57 schrieb Werner LEMBERG:
Die erzeugten PDF-Dateien sind sehr viel größer als normal (aufgrund
der schwachen oder fehlenden Schriftartenoptimierung). Wenn jedoch
zwei oder mehr PDF-Dateien mittels pdftex, xetex oder luatex
eingebunden werden, können sie mit Ghostscript nach
Am 17.03.2015 um 11:24 schrieb Thomas Morley:
2015-03-17 11:00 GMT+01:00 Peter Bjuhr :
Hi,
I just noticed that in the documentation about right-hand fingerings in
the common notation for fretted strings: http://www.lilypond.org/doc/
v2.19/Documentation/notation/common-notation-for-fretted-
str
Am 25.03.2015 um 18:58 schrieb Carl Sorensen:
On 3/25/15 6:54 AM, "u...@openlilylib.org" wrote:
I think the fonts we're looking for should have a similarly classic or
old-fashioned look as Century.
Maybe we should look for fonts that (optionally) ship with texlive.
Hunting around for sans
Am 28.04.2015 um 00:20 schrieb Trevor Daniels:
I'd like to second everything that Carl writes below,
and add my thanks to you, David.
+1
Marc
Trevor
Carl Sorensen wrote Monday, April 27, 2015 11:07 PM
On 4/27/15 3:09 AM, "David Kastrup" wrote:
As things currently stand, I suspect that
Am 19.05.2015 um 09:04 schrieb James Lowe:
[...]
Oh if someone could look at the script that Mark Hohl (I think) created
a while back called 'make-countdown-announcement.sh'
No, it was Mark Polesky who added it.
Cheers,
Marc
___
lilypond-devel m
Am 31.05.2015 um 07:47 schrieb David Kastrup:
[...]
Well, that was actually more what I considered strange: the lack of
comment on the result/merits rather than on the particular
implementation.
I can just speak for myself, but the actual benefit of this patch was
not obviously clear for me, b
o Rietveld?
Cheers,
Marc
From 360d89c13713be692db3a6fc557eda0f7557a288 Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: Sat, 20 Jun 2015 19:19:03 +0200
Subject: [PATCH] Parentheses in ChordNames have the same size as the Chord
symbols.
---
ly/engraver-init.ly | 1 +
1 file changed, 1 insertio
Am 20.06.2015 um 19:47 schrieb David Kastrup:
Marc Hohl writes:
Hi list,
in my latest project, I found out that
\score {
\new ChordNames { \chordmode { \parenthesize c } }
}
yields in way too tiny parentheses. The following patch
resolves that problem.
I recall vaguely that 'g
Am 21.06.2015 um 10:43 schrieb d...@gnu.org:
https://codereview.appspot.com/245430043/diff/1/ly/engraver-init.ly
File ly/engraver-init.ly (right):
https://codereview.appspot.com/245430043/diff/1/ly/engraver-init.ly#newcode517
ly/engraver-init.ly:517: \override ParenthesesItem.font-size = #1.5
Am 23.06.2015 um 10:15 schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-review Patch-needs_work
Comment #3 on issue 4460 by pkx1...@gmail.com: Parentheses in ChordNames
should have the same size as the chord symbols
https://code.google.com/p/lilypond/issues/detail?id=4460
This look
Am 23.06.2015 um 11:03 schrieb James:
Marc
On 23/06/15 09:25, Marc Hohl wrote:
Am 23.06.2015 um 10:15 schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-review Patch-needs_work
Comment #3 on issue 4460 by pkx1...@gmail.com: Parentheses in ChordNames
should have the same size as
Am 23.06.2015 um 11:31 schrieb lilyp...@googlecode.com:
Comment #5 on issue 4460 by thomasmo...@gmail.com: Parentheses in
ChordNames should have the same size as the chord symbols
https://code.google.com/p/lilypond/issues/detail?id=4460
Is this issue a duplicate of
https://code.google.com/p/lil
Am 10.07.2015 um 20:49 schrieb Paul Morris:
On Jul 9, 2015, at 5:39 AM, James wrote:
Perhaps we can tweak the 'website' slightly (i.e. make small changes to
the TexInfo code) to perhaps do something like moving some/all of the
text from here
http://lilypond.org/introduction.html
to the front
LGTM,
Marc
Am 02.09.2015 um 21:26 schrieb simon.albre...@mail.de:
Reviewers: ,
Message:
I came across this rather mishapen wording in NR 4.6.2 – so I changed
it.
Description:
Improve wording for an NR paragraph
The paragraph from "Avoid (or reduce)" in spacing.itely
used 'for example' twice
Am 05.01.2016 um 18:06 schrieb Abraham Lee:
On Tuesday, January 5, 2016, Paul Morris wrote:
Thanks to David Kastrup’s work there’s now much less need to use scheme
syntax in overrides etc. (e.g. the dot syntax instead of #' and no longer
needing # for numbers). This has really simplified thin
Am 05.01.2016 um 21:22 schrieb Thomas Morley:
[...]
To illustrate. Look at the output from the following compiled in a ly-file:
true = ##t
false = ##f
#(define v1 (vector true false true))
#(define v2 #(true false true))
#(newline)
#(write-me "v1 " v1)
#(write-me "v2 " v2)
#(write-me "(vector
Am 01.04.2016 um 23:59 schrieb Simon Albrecht:
Hello,
using Completion_heads_engraver and Completion_rests_engraver means a
lot of typing, and yet it is a pretty stereotypical action. So I thought
about introducing a context modification identifier (like
\RemoveEmptyStaves) for this task. Do you
Hi list,
after a recent "git pull", the call "make -j3" fails with
---
In file included from slur-engraver.cc:32:0:
slur-engraver.cc: In static member function 'static void
Slur_engraver::boot()':
./include/translator.icc:115:40: error:
'&Slur_proto_engraver::listen_slur' is not a valid templ
Am 24.06.2016 um 10:33 schrieb David Kastrup:
[...]
Well, it got through patchy-staging. So obviously something is
different with your setup, and you don't give any information about your
setup. What does g++ --version say?
$ g++ --version
g++ (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
Copyright
Am 25.06.2016 um 10:36 schrieb David Kastrup:
David Kastrup writes:
David Kastrup writes:
autogen.sh --noconfigure
configure --prefix=/home/knut/sources/lilybisect/
make -k -j 1 CPU_COUNT=1 all
Logfile attached.
I see a single error. That's ... curious. Have to go to rehearsal now,
wil
Hi list,
I have written some musicals for children and adolescents in the past
and have two more musicals in the pipeline, to be released at the end of
2016.
The sheets are done with LilyPond and LaTeX and available for free, but
the musicals are only available in German language.
You can
Am 10.07.2016 um 19:11 schrieb Federico Bruni:
Il giorno ven 8 lug 2016 alle 12:36, Marc Hohl ha
scritto:
I have written some musicals for children and adolescents in the past
and have two more musicals in the pipeline, to be released at the end
of 2016.
The sheets are done with LilyPond and
Hi list,
currently, my whole git/patch-workflow environment is not working
properly at the moment.
Nevertheless, it seems to me that in line 616
of Documentation/de/web/introduction.html,
@divClass{column-left-top}
has to be replaced by
@divClass{column-center-top}
see http://lilypond.org/
Am 20.07.2016 um 15:41 schrieb Federico Bruni:
[...]
Who updated the german translation probably overlooked that change.
If we could use gettext, this problem would not occur...
I've pushed the fix directly to translation branch (work on translated
manuals do not need a review process).
Thanks
Am 22.10.2016 um 10:00 schrieb Thomas Morley:
Hi,
I recently mentioned my work to create the very special notation for
Akkordzither.
http://lists.gnu.org/archive/html/lilypond-user/2016-10/msg00349.html
I consider to put it in the source, probably in the same way we
have gregorian.ly.
What do
Am 22.10.2016 um 16:29 schrieb Simon Albrecht:
On 22.10.2016 10:00, Thomas Morley wrote:
Hi,
I recently mentioned my work to create the very special notation for
Akkordzither.
http://lists.gnu.org/archive/html/lilypond-user/2016-10/msg00349.html
I consider to put it in the source, probably in
Am 16.12.2016 um 02:09 schrieb Alexander Kobel:
Hi all.
[...]
What about hide-below-length or hide-if-shorter-than?
minimum-visibility?
Just my 2ct,
Marc
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listin
601 - 651 of 651 matches
Mail list logo