On Tue, Jul 4, 2017 at 6:53 AM, Federico Bruni wrote:
> Jay,
>
> today I've stumbled upon the same problem you reported here:
> http://lilypond.1069038.n5.nabble.com/Building-issues-lilypo
> nd-and-docs-td198696.html#a198786
>
> Context: I'm building a Fedora container which I'd like to make avai
On Wed, May 17, 2017 at 2:01 AM, Trevor Daniels
wrote:
>
> Did you register git-cl in your account at SourceForge and obtain a bearer
> token?
> See "Authorizing git-cl for the LilyPond issue tracker" as the next step
> in configuring git-cl
> in http://lilypond.org/doc/v2.19/Documentation/contri
https://codereview.appspot.com/321930043/
It was requested sometime last year that I attempt to get this into
lilypond proper this is my attempt. It creates a scheme module for putting
all of the merge rest functionality. I didn't see any precedent for this,
so let me know concerns. If this approa
On Fri, Dec 30, 2016 at 2:28 PM, Phil Holmes wrote:
> Just for clarity. RAM or disk?
In the VM:
- Disk: 14gb (4.2gb used).
- Memory: 4gb (after increasing from 2gb)
I started re-running the doc build about an hour ago. Neither disk nor
memory seem to be in danger of being used up.
-Jay
__
In response to this thread:
https://lists.gnu.org/archive/html/lilypond-user/2016-12/msg00679.html
I'm attempting to build lilypond.
When building locally (an older version of mint linux) it ends with:
make[1]: Entering directory `/home/jay/programming/lilypond/build/mf'
mkdir -p ./out
touch ./ou
On Sun, Jan 31, 2016 at 6:52 AM, Simon Albrecht wrote:
> It definitely looks like a good way to go, except that I wouldn’t know how
> to use multiple features at the same time. Would it be possible to input
> font-features as a symbol list, i.e. (random example)
> { \override TextScript.font-featu
On Mon, Jan 18, 2016 at 10:37 AM, Jay Anderson wrote:
> On Mon, Jan 18, 2016 at 9:59 AM, Jay Anderson wrote:
>> First issue: It appears that lilypond is dependent on pango 1.6
>> (pangoft2 - required 1.6.0, INSTALL.txt says pango 1.12 or newer so
>> I'm not to
On Mon, Jan 18, 2016 at 9:59 AM, Jay Anderson wrote:
> First issue: It appears that lilypond is dependent on pango 1.6
> (pangoft2 - required 1.6.0, INSTALL.txt says pango 1.12 or newer so
> I'm not totally sure what to believe.). OpenType features were added
> in pango 1.18 (ass
I'm interested in seeing what it would take to add OpenType features
-- specifically old style number figures (onum) and small caps (smcp).
First issue: It appears that lilypond is dependent on pango 1.6
(pangoft2 - required 1.6.0, INSTALL.txt says pango 1.12 or newer so
I'm not totally sure what
On Tue, Jun 24, 2014 at 4:06 AM, Werner LEMBERG wrote:
> I fully understand what you say, and similar symbols are used for
> singers, too, however, I think this somehow contradicts what lilypond
> is intended to do: engraving well-formatted music. It's not
> lilypond's job to imitate hand-written
On Mon, Jun 23, 2014 at 10:24 PM, David Kastrup wrote:
> You don't say which frustration. You apparently want to have automatic
> beams across breath marks. To me, that does not make a lot of sense.
Sorry, I took out too much context from the original message. It's
pretty common in horn music (
On Wed, Mar 6, 2013 at 6:00 PM, Thomas Morley
wrote:
> Well, nowadays we have the 'collision-interfaces-property but adding
> breathing-sign-interface to it seems to have no effect.
>
> \version "2.17.12"
>
> respectBS = {
> \override Beam #'collision-interfaces =
> #'(beam-interface
>
On Sat, Sep 22, 2012 at 3:07 PM, Graham Percival
wrote:
> I have no problem with splitting \tempo into a \tempo_bpm and
> \tempoMark command. Or perhaps it would be better to just use
> \mark, and add markup functions which mimic the "text" parts of
> the existing \tempo command (if they don't al
On Thu, Jan 5, 2012 at 12:50 AM, Keith OHara wrote:
> \paper { paper-width= 1\mm }
> { \override Score.NonMusicalPaperColumn #'line-break-permission = ##f
> \repeat unfold 400 { b'4 } }
>
>> Given this message []
>>
>> it seems that previous versions of lilypond don't have this problem.
>
>
>
On Wed, Jan 4, 2012 at 1:41 AM, David Kastrup wrote:
> Can you use git bisect for identifying the commit where things go wrong
> for you?
Git bisect results:
20670d51f8d97fd390210dd239b3b2427f071e7c is the first bad commit
commit 20670d51f8d97fd390210dd239b3b2427f071e7c
Author: Mike Solomon
Date
On Tue, Jan 3, 2012 at 1:12 AM, m...@apollinemike.com
wrote:
> On Jan 3, 2012, at 9:02 AM, David Kastrup wrote:
>> If he hadn't rerun configure since before version 2.15.21, I think that
>> the compilation would likely have failed for other reasons. The problem
>> report is for 2.15.23. It may b
On Mon, Jan 2, 2012 at 6:41 PM, Keith OHara wrote:
> mike apollinemike.com apollinemike.com> writes:
>> Some meh news: I don't get a segfault ...
>> Maybe someone else could give it a look?
>
> I can't produce the segfault, either.
Strange I can consistently reproduce it (just pulled the latest
2011/7/18 Janek Warchoł :
> My friend and I, having some spare time, wanted to fix a bug
> http://code.google.com/p/lilypond/issues/detail?id=1301. It's related
> to planning distribution of music notes and other signs, so we need
> some overview how the whole process works. Comments in the sourc
On Mon, Sep 13, 2010 at 8:03 AM, Jay Anderson wrote:
> On Sun, Sep 12, 2010 at 12:46 PM, Neil Puttock wrote:
>> Add the Tweak_engraver to the Dynamics context.
>
> Works fine. Thanks. This should probably be added to engraver-init.ly.
> Are there any problems with doing this?
&
On Wed, Jun 9, 2010 at 6:34 AM, James Lowe wrote:
> I wondered if anyone can tell me if this is a mistake or what the
> significance of the back-quote is vs the standard singe quote?
It is intentional. Look up scheme's quasiquote and unquote functions.
-Jay
_
On Thu, Apr 29, 2010 at 1:53 PM, Neil Puttock wrote:
> I'm afraid I couldn't resist testing this, so if you're interested,
> try the attached patch.
That's great! You might also want to include simultaneous music
(<<...>>*4). Thanks!
-Jay
___
lil
On Wed, Apr 28, 2010 at 9:40 AM, Xavier Scheuer wrote:
> Current syntax (using colons):
>
> c4:16 d4: e: f: |
> g: a: b: c: | % etc.
>
> with \repeat tremolo:
>
> \repeat tremolo 4 c16 \repeat tremolo 4 d16
> \repeat tremolo 4 e16 \repeat tremolo 4 f16 |
> \repeat tremolo 4 g16 \repeat tre
On Sat, Aug 8, 2009 at 12:57 PM, Dan Eble wrote:
> Doesn't this mix up meaning and appearance? What will you do when people
> come asking for LargeStaff, TinyStaff, LittleGreenStaff (for Martian music),
> and so forth?
On Sat, Aug 8, 2009 at 1:45 PM, Alexander Kobel wrote:
> Oh, and by the way...
> Jay, Mark, anyone: are you interested in submitting a full patch, with
> appropriate documentation, NEWS item etc? If so, we can officially
> submit it for inclusion.
Attached is a patch which adds "SmallStaff" to engraver-init.ly.
Everywhere that \accepts "Staff" was used I just added \accepts
On Wed, Jul 22, 2009 at 9:05 AM, Kieren
MacMillan wrote:
> Hello all,
>
> Like many Lilyponders, I break down my code into variables, e.g. global (for
> time signature changes, etc.), notes, dynamics, etc. The main irritation
> with this (IMO) is that each variable requires a complete set of skips
On Mon, Jun 22, 2009 at 6:03 PM, Mark Polesky wrote:
> I know, I know, I just won't let this die. I rewrote this silly
> function yet again (by now it's more of a programming exercise
> than anything else). But the things I've learned from everyone so
> far have found their way into my other LilyPo
On Thu, Jun 18, 2009 at 9:16 PM, Graham
Percival wrote:
> On Thu, Jun 18, 2009 at 05:33:18PM -0700, Mark Polesky wrote:
>>
>> dynamic-scripts-init.ly
>>
>> why is there p but no f?
>
> IIRC I asked this 3-4 years ago, and the answer was that somebody
> had seen p in the literature (a Tc
On Mon, Jun 15, 2009 at 3:03 AM, Joe Neeman wrote:
>
> On Mon, Jun 8, 2009 at 3:59 AM, Mark Polesky wrote:
>>
>> my version:
>>
>> (define-public (split-at-predicate predicate lst)
>> "Split LST (into 2 lists) at the first element that returns #f for
>> (PREDICATE previous_element element), and
On Sat, Jun 6, 2009 at 4:53 PM, Paul Scott wrote:
> Which is kind of ridiculous if you're writing an ensemble piece with many
> (even more than one) voices/parts. How can a midi of a multi-voice work
> with any repeats be done?
I was working on a large score and originally kept the repeat
structu
On Sat, Jun 6, 2009 at 3:22 AM, Mark Polesky wrote:
>
> I tried to answer a question on -user but hit a brick wall.
> \unfoldRepeats failed to work when the music block was funneled from 2
> separate expressions. Can someone explain this to me? Why does the
> following code work for voiceA but not
Mats Bengtsson ee.kth.se> writes:
>
> We already have the predefined macro \noBeam. Do we really need yet another
> more or less obscure special case of the syntax?
>
> /Mats
>
> Werner LEMBERG wrote:
> > I'm not sure whether this has been discussed before: What do you think
> > of using `c
31 matches
Mail list logo
