On Jan 26, 2019, at 8:52 PM, David F. wrote:
> I can specify the font for my score to use with #(define fonts … ), but
> calling #(set-global-staff-size) undoes the font definition.
>
> In the snippet below, Times New Roman will be used as the font for the whole
> document. But if line 6
On Sat, Jan 26, 2019 at 11:17:21PM -0500, Hwaen Ch'uqi wrote:
> I'm not sure if this is still on topic, but I have found that LilyPond
> indentation on emacs goes off kilter when brackets (i.e., for beaming)
> and parentheses (i.e., for slurs and phrasing slurs) are used. The
> solution for
I'm not sure if this is still on topic, but I have found that LilyPond
indentation on emacs goes off kilter when brackets (i.e., for beaming)
and parentheses (i.e., for slurs and phrasing slurs) are used. The
solution for brackets is easy enough; putting space around them
alleviates the problem.
I can specify the font for my score to use with #(define fonts … ), but calling
#(set-global-staff-size) undoes the font definition.
In the snippet below, Times New Roman will be used as the font for the whole
document. But if line 6 is uncommented, the font reverts to the default of New
On 2019-01-26 6:56 pm, Gack McShite wrote:
I will stipulate that the version for the file was not necessarily a
match for the syntax. It was 2.14.0, your example was 2.12.0. Not my
generator, so I don't know how that version was chosen other than
current at the time. Obviously had I known
I will stipulate that the version for the file was not necessarily a
match for the syntax. It was 2.14.0, your example was 2.12.0. Not my
generator, so I don't know how that version was chosen other than
current at the time. Obviously had I known that the syntax changed
from 2.12, I wouldn't be
On Sun 27 Jan 2019 at 11:58:30 (+1100), Andrew Bernard wrote:
> Frescobaldi has a great formatting function that indents all the code very
> nicely and nearly flawlessly.
>
> But since an upgrade to Debian 9 and as the complexity of my current score
> increases, F. has slowed down to a molasses
Thanks David!
Interestingly, the following line appears in the lilypond mode elisp:
lilypond-mode.el:;;; Inspired on auctex
Andrew
On Sun, 27 Jan 2019 at 12:11, David Kastrup wrote:
>
>
> You wouldn't want it to try. Really, somebody™ should rewrite Emacs'
> LilyPond support using some of
Andrew Bernard writes:
> Frescobaldi has a great formatting function that indents all the code very
> nicely and nearly flawlessly.
>
> But since an upgrade to Debian 9 and as the complexity of my current score
> increases, F. has slowed down to a molasses like rate and has sadly become
>
Frescobaldi has a great formatting function that indents all the code very
nicely and nearly flawlessly.
But since an upgrade to Debian 9 and as the complexity of my current score
increases, F. has slowed down to a molasses like rate and has sadly become
unusable. [I have never seen that before
Jean-Julien Fleck writes:
> Hello Joe,
>
>
>
> Le sam. 26 janv. 2019 à 21:23, Joseph Srednicki
> a écrit :
>
>> Hello Everyone:
>>
>> See the following example. I am trying to hide the first e the first bea
>> in the upper voice. I successfully hid the note head and stem, but cannot
>> seem to
Thanks. That's exactly what I need.
-Original Message-
From: Jean-Julien Fleck
To: Joseph Srednicki
Cc: lilypond-user Mailinglist
Sent: Sat, Jan 26, 2019 3:32 pm
Subject: Re: Hiding a ledger line
Hello Joe,
Le sam. 26 janv. 2019 à 21:23, Joseph Srednicki a
écrit :
Hello
Hello Joe,
Le sam. 26 janv. 2019 à 21:23, Joseph Srednicki
a écrit :
> Hello Everyone:
>
> See the following example. I am trying to hide the first e the first bea
> in the upper voice. I successfully hid the note head and stem, but cannot
> seem to hide the ledger line.
>
> Can someone
Hello Everyone:
See the following example. I am trying to hide the first e the first bea in
the upper voice. I successfully hid the note head and stem, but cannot seem to
hide the ledger line.
Can someone please give me the appropriate command to do this?
I experimented with
Gack McShite writes:
> convert-ly made no changes, other than the \version. But I had
> forgotten about it so thanks for the reminder!
I just tried. The following
\version "2.12.0"
TrackAVoiceAMusic = #(define-music-function (parser location inTab)
(boolean?)
#{
\tempo 4=106
One more question. I wonder if Lily can do this :)))
Think about this
\new StaffGroup
\relative c'' <<
\set StaffGroup.systemStartDelimiterHierarchy
= #'(SystemStartSquare (SystemStartBrace (SystemStartBracket a
(SystemStartSquare b) ) c ) d)
\new Staff { c1
convert-ly made no changes, other than the \version. But I had
forgotten about it so thanks for the reminder!
Aaron Hill was correct, removing the dollar sign worked, simples.
Glad I gave up and asked for help after 4 hours of banging my head
against the internet!
On 1/26/19, Aaron Hill wrote:
Aaron Hill wrote
> On 2019-01-26 6:08 am, Reggie wrote:
>> Hi. I tried to look here and attempt adding delimiter code but no
>> matter what
>> I do I cannot show a brace or bracket or anything to put my two oboes
>> together for the duration of the 2 staves on a few pages. Then it
>> should go
On 2019-01-26 6:08 am, Reggie wrote:
Hi. I tried to look here and attempt adding delimiter code but no
matter what
I do I cannot show a brace or bracket or anything to put my two oboes
together for the duration of the 2 staves on a few pages. Then it
should go
back to normal grouping in code.
Hi. I tried to look here and attempt adding delimiter code but no matter what
I do I cannot show a brace or bracket or anything to put my two oboes
together for the duration of the 2 staves on a few pages. Then it should go
back to normal grouping in code. Can you please tell me how I am wrong?
Gack McShite writes:
> Trying to clean up errors. I see this pattern a lot, so I assume it
> should work.
>
> TrackAVoiceAMusic = #(define-music-function (parser location inTab) (boolean?)
> #{
>\tempo 4=106
>\clef #(if $inTab "tab" "treble_8")
>
> and then later
>
>\context Voice =
Am Sa., 26. Jan. 2019 um 08:18 Uhr schrieb Gack McShite :
>
> Trying to clean up errors. I see this pattern a lot, so I assume it
> should work.
>
> TrackAVoiceAMusic = #(define-music-function (parser location inTab) (boolean?)
> #{
>\tempo 4=106
>\clef #(if $inTab "tab" "treble_8")
>
>
On 2019-01-26 12:22 am, Aaron Hill wrote:
Unfortunately, I inadvertently broke the hyperlinks in the process, so
while the snippets render properly, you cannot click on links within
the documents. Since I tend to manually search through PDFs, this
hasn't been a big enough issue for me to
On 2019-01-25 7:22 pm, Gack McShite wrote:
Trying to clean up errors. I see this pattern a lot, so I assume it
should work.
TrackAVoiceAMusic = #(define-music-function (parser location inTab)
(boolean?)
#{
\tempo 4=106
\clef #(if $inTab "tab" "treble_8")
What stands out to me is the
On 2019-01-25 6:13 pm, Karlin High wrote:
On Fri, Jan 25, 2019 at 7:10 PM Aaron Hill
wrote:
> In case it helps your friend, I've attached a PDF of the Guile 1.8.7
> docs which can be used as a more technical reference for the specific
> flavor of Scheme used by LilyPond.
>
> The other day I
25 matches
Mail list logo
