On Thu, Dec 12, 2019 at 10:20 PM Aaron Hill
wrote:
> On 2019-12-12 5:53 pm, Freeman Gilmore wrote:
> > Someday I may write a markup up for some accidentals. This may help
> > me
> > understand what I am doing with markup. For how I just want to know a
> > little about how lexer reads the pitc
On 2019-12-12 5:53 pm, Freeman Gilmore wrote:
Someday I may write a markup up for some accidentals. This may help
me
understand what I am doing with markup. For how I just want to know a
little about how lexer reads the pitch, the octave. accidental and note
size; and I may not be able to do
On Thu, Dec 12, 2019 at 4:40 PM Hans Åberg wrote:
>
> > On 12 Dec 2019, at 22:32, Freeman Gilmore
> wrote:
> >
> >> On Thu, Dec 12, 2019 at 3:01 PM Hans Åberg wrote:
> >>
> >> > On 12 Dec 2019, at 14:01, Freeman Gilmore
> wrote:
> >> >
> >> > I would like to understand how it work, if i can.
>
On Thu, Dec 12, 2019 at 7:13 PM Andrew Bernard
wrote:
> Hi Freeman,
>
> I still don't understand your aim here. Are you just trying to
> understand the lilypond code or do you have some specific purpose or
> application? It would help to know.
>
> Andrew
>
Someday I may write a markup up for som
Hi Freeman,
I still don't understand your aim here. Are you just trying to
understand the lilypond code or do you have some specific purpose or
application? It would help to know.
Andrew
On Fri, 13 Dec 2019 at 08:33, Freeman Gilmore wrote:
>
> 0k that helps. The lexer looks like what i an lo
> On 12 Dec 2019, at 22:32, Freeman Gilmore wrote:
>
>> On Thu, Dec 12, 2019 at 3:01 PM Hans Åberg wrote:
>>
>> > On 12 Dec 2019, at 14:01, Freeman Gilmore
>> > wrote:
>> >
>> > I would like to understand how it work, if i can.
>>
>> There is a lexer generated from a file lexer.ll by Flex
On Thu, Dec 12, 2019 at 3:01 PM Hans Åberg wrote:
>
> > On 12 Dec 2019, at 14:01, Freeman Gilmore
> wrote:
> >
> > I would like to understand how it work, if i can.
>
> There is a lexer generated from a file lexer.ll by Flex, which divides the
> input stream into tokens, which are handed over to
> On 12 Dec 2019, at 14:01, Freeman Gilmore wrote:
>
> I would like to understand how it work, if i can.
There is a lexer generated from a file lexer.ll by Flex, which divides the
input stream into tokens, which are handed over to a parser generated from a
file parser.yy by Bison.
David Kastrup wrote:
Try running LilyPond with -ddebug-parser . The output is related to the
printed LilyPond grammar in the LilyPond Notation Reference appendices.
That grammar appendix is still rather garbled.
Attached is a less confusing version for circa 2.19.80.
Cheers,
Robin
Grammar
Freeman Gilmore writes:
> On Thu, Dec 12, 2019 at 6:08 AM Andrew Bernard
> wrote:
>
>> I think we need to know what the OP wants to actually do first.
>> There's a dozen different possible ideas here.
>>
>
> There are 4 parts to { cis'4 }; i would like to understand how the parts
> are read in
The way to print the first bar number is explained in the first of the
"Selected Snippets" of this section.
http://lilypond.org/doc/v2.19/Documentation/notation/bars#bar-numbers
On 12/12/2019 17:32, Peter Toye wrote:
Re: Bar lines within bars inhibit bar numbering Hi Timothy,
Just done a bit
Hi Timothy,
Just done a bit more poking around. According to Internals,
all-bar-numbers-visible shows all bar numbers including the first one, but it
doesn't seem to as the first bar number isn't printed (not that I want it). I
also tried first-bar-number-invisible but that gave the same effec
Thanks Timothy,
I hadn't realised that you need to put in a dummy bar at the beginning \bar ""
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Thursday, December 12, 2019, 5:38:03 PM, Timothy Lanfear wrote:
The way to print the first bar number is explain
Am Do., 12. Dez. 2019 um 17:05 Uhr schrieb Peter Toye :
>
> The example below shows the issue. The mid-bar line with a \break does not
> show the bar number at the beginning of the next line - I would expect '2'. A
> \break at the end of a bar gives the expected result.
>
> Also, the commented ou
Adding the layout block will number partial bars in brackets.
\version "2.19.83"
\language "english"
\layout {
\context { \Score barNumberVisibility = #all-bar-numbers-visible }
}
\score {
\new Staff {
\clef "treble"
\time 4/4
{
\override BarNumber.break-visibility = ##(
Thursday, December 12, 2019, 4:39:43 PM, Rick Kimpel wrote:
Peter
You need an extra #
\override BarNumber.break-visibility = ##(#t #t #t)
So I do. Thanks. One day I'll get to grips with the tweaking syntax.
But that doesn't do what you're talking about. I had something similar in a
piece with
Thursday, December 12, 2019, 5:10:26 PM, Timothy Lanfear wrote:
Adding the layout block will number partial bars in brackets.
Brilliant. Thanks.
\version "2.19.83"
\language "english"
\layout {
\context { \Score barNumberVisibility = #all-bar-numbers-visible }
}
\score {
\new Staff {
I just created a javascript script to change the slurs of the .svg file
produced by Lilypond using the mouse, as I had announced. The coordinates
of the control points of the associated Bezier curve can be reported in the
corresponding .ly file and this completely avoids the time consuming trial
an
Peter
You need an extra #
\override BarNumber.break-visibility = ##(#t #t #t)
But that doesn't do what you're talking about. I had something similar in a
piece with 4/4 + 3/4 time with a dotted barline. I ended up just manually
renumbering the bars numbers with:
\set Score.currentBarNumber
Proba
The example below shows the issue. The mid-bar line with a \break does not show
the bar number at the beginning of the next line - I would expect '2'. A \break
at the end of a bar gives the expected result.
Also, the commented out line doesn't compile, and I can't see why, so can't see
if it wo
Hello everyone,
Lately I was pointed in Norm Weinberg's direction for a standard drumkit
notation. I noticed there were quite a few differences in Weinberg's drum
key with respect to LilyPond's default (hihat being probably the most
confusing). Other available mappings had differences as well.
So
Good morning!
I am composing a piece that features the harp as a soloist and I had a
question about some notation.
Please see attached.
How would you go about creating this markup so it could easily be used
throughout a piece? Because the note range of the mute symbol will
likely change wit
On Thu, Dec 12, 2019 at 2:36 AM Noeck wrote:
> Hi,
>
> I am not really familiar with the parser, but I think LilyPond uses
> Bison¹ and the input syntax is defined in lilypond/lily/parser.yy
>
> ¹: https://www.gnu.org/software/bison/
Thank you, i will check this.
ƒg
>
>
> Best,
> Joram
>
>
On Thu, Dec 12, 2019 at 2:26 AM Andrew Bernard
wrote:
> \include ?
>
> What do you really want to do?
>
I would like to understand how it work, if i can.
Thank you,
ƒg
>
> Andrew
>
> On Thu, 12 Dec 2019 at 14:38, Freeman Gilmore
> wrote:
> >
> > Where could i find the code that would reads th
On Thu, Dec 12, 2019 at 6:08 AM Andrew Bernard
wrote:
> I think we need to know what the OP wants to actually do first.
> There's a dozen different possible ideas here.
>
There are 4 parts to { cis'4 }; i would like to understand how the parts
are read in to the parser. How is it divided, ans
"Peter Gentry" writes:
> Thanks for that response David. I wonder if the cause is to be found on my
> machine rather than in Lilypond.
The cause is, according to the comparatively sparse and vague
information you provided so far, your input never could have worked in
the form you claim it did.
I think we need to know what the OP wants to actually do first.
There's a dozen different possible ideas here.
Andrew
On Thu, 12 Dec 2019 at 18:35, Noeck wrote:
> I am not really familiar with the parser, but I think LilyPond uses
> Bison¹ and the input syntax is defined in lilypond/lily/parse
Thanks for that response David. I wonder if the cause is to be found on my
machine rather than in Lilypond.
I have recently been looking at Python (to try and stimulate a few aged grey
cells) to which end I have blundered about with Trinket and also installed
Python3.8 (64bit).
These efforts h
28 matches
Mail list logo
