On Mon, 21 Jan 2019 at 22:33, David Kastrup wrote:
> Gianmaria Lari writes:
>
> > On Mon, 21 Jan 2019 at 14:57, Gianmaria Lari
> > wrote:
> >
> >>
> >>
> >> On Mon, 21 Jan 2019 at 13:02, Valentin Villenave <
> valen...@villenave.net>
> >> wrote:
> >>
> >>> On 1/21/19, Andrew Bernard wrote:
>
Hello Reggie,
Why can't you just show us an MWE (Minimum Working Example) of your Lily code?
That would make helping you so much easier!
JM
> Le 22 janv. 2019 à 04:57, Aaron Hill a écrit :
>
> On 2019-01-21 6:17 pm, Reggie wrote:
>> For your information, top-system-spacing has zero effect on
On 1/21/19, Aaron Hill wrote:
> That seems like such a useful pattern.
Agreed.
> Why is it only mentioned once
> and buried away in extending.pdf? Also, there is no use of it in the
> entirety of the LSR.
Well, grob-transformer is a relatively new function (it was introduced
after 2.18, which
On Mon, 21 Jan 2019, Ivan Kuznetsov wrote:
I think that is because my lilypond installation
automatically puts the correct files in /usr/share/vim/ and so
lilypond syntax highlighting works immediately for me upon a new
OS installation. But then, I use Fedora. What OS do
you work under?
On 2019-01-21 6:17 pm, Reggie wrote:
For your information, top-system-spacing has zero effect on my Score. I
have
my margins set all to a basic .75\in and this top-system-spacing has no
visible change. Why is this? What causes top-system-spacing to not show
any
change? How should I be a
Hi Reggie,
> top-system-spacing has zero effect on my Score. I have
> my margins set all to a basic .75\in and this top-system-spacing has no
> visible change. Why is this? What causes top-system-spacing to not show any
> change? How should I be a detective and solve this? :))
Compile the
Hi Reggie,
> Is there a way to only adjust the first page top-margin
What I suggested will do that, because top-markup-spacing (essentially, the
"first page" top spacing) is independent of top-system-spacing (essentially,
the "second and subsequent page" top spacing).
Cheers,
Kieren.
Kieren MacMillan wrote
> Hi Reggie,
>
>> Nothing is above my title. I have a normal Piece of music. I
>> would like to have my title move UP vertically only but not move my
>> music
>> at all. The top system and beyond is just fine.
>
> Then you need to decrease top-markup-spacing (to reduce
Aaron Hill wrote
> A side commentary, if you would not mind. You have posted a few times
> asking for features that seem to show a focus on WYSIWYG-style
> activities. You are probably used to using tools that let you click and
> drag items around on a virtual paper, placing things wherever
Mea culpa.
It's built in to 2.19.82.
Apologies for the noise.
Andrew
On Tue, 22 Jan 2019 at 12:52, Andrew Bernard
wrote:
>
> But it's a very large chunk of Scheme for a relatively small matter, yet
> another bit of complex code to look after locally. Is this functionality
> built in to
LSR 745 does a nice job of providing for complex compound meter time
signatures.
But it's a very large chunk of Scheme for a relatively small matter, yet
another bit of complex code to look after locally. Is this functionality
built in to lilypond by now?
Andrew
Hi Reggie,
> Nothing is above my title. I have a normal Piece of music. I
> would like to have my title move UP vertically only but not move my music
> at all. The top system and beyond is just fine.
Then you need to decrease top-markup-spacing (to reduce the gap between the top
margin and
On 2019-01-21 4:35 pm, Aaron Hill wrote:
\version "2.19.82"
#(define-markup-command (faux-raise layout props amount arg) (number?
markup?)
(let* ((sten (interpret-markup layout props arg))
(xex (ly:stencil-extent sten X))
(yex (ly:stencil-extent sten Y)))
Mason Hock writes:
>
> I use vim for everything except large Lilypond projects that consist of
> multiple input files. The ability to click on an object in the score and
> jump to that place in the code, even if the file containing that code is
> not open, outweighs for me vim's advantages as a
On 01/21, Ivan Kuznetsov wrote:
> I have looked at Frescobaldi, but once one is fluent
> with a Unix editor (which means vim or emacs)
> Frescobaldi and other third party tools are
> _not_ a time saver.
I use vim for everything except large Lilypond projects that consist of
multiple input files.
On 2019-01-21 3:30 pm, Reggie wrote:
Karlin High wrote
On 1/21/2019 5:02 PM, Reggie wrote:
I literally want just move up the TITLE and not touch anything
else.
Could you attach an image or PDF showing the form of your current
layout? I'm curious about what is currently above the title.
You
I am a lifelong vim user and I cannot imagine any other way
to enter or manipulate text, be it for web pages,
documents (which I create with Latex) or lilypond.
I have looked at Frescobaldi, but once one is fluent
with a Unix editor (which means vim or emacs)
Frescobaldi and other third party
On 1/21/2019 5:30 PM, Reggie wrote:
Nothing is above my title.
Sorry, communication failure. I was thinking that moving the title up
will quickly reach the top of the page, and there must be something
about the layout I am not understanding.
How about using annotate-spacing to show the
On 2019-01-21 3:02 pm, Reggie wrote:
And actually you are incorrect that command pushes all systems down in
my
Piece so I literally want just move up the TITLE and not touch anything
else. This is not possible I can't see it yet. Sorry but no. Your raise
does
not only move title it bothers my
Karlin High wrote
> On 1/21/2019 5:02 PM, Reggie wrote:
>> I literally want just move up the TITLE and not touch anything
>> else.
>
> Could you attach an image or PDF showing the form of your current
> layout? I'm curious about what is currently above the title.
> --
> Karlin High
> Missouri,
On 1/21/2019 5:02 PM, Reggie wrote:
I literally want just move up the TITLE and not touch anything
else.
Could you attach an image or PDF showing the form of your current
layout? I'm curious about what is currently above the title.
--
Karlin High
Missouri, USA
Kieren MacMillan wrote
> Hi Reggie,
>
>> How is it possible to simply? move a title of a piece vertical up?
>
> %%% SNIPPET BEGINS
> \version "2.19.80"
>
> \bookpart {
> \header {
> title = \markup "My Default Title"
> }
> \score {
> c''1
> }
> }
> \bookpart {
> \header {
>
And actually you are incorrect that command pushes all systems down in my
Piece so I literally want just move up the TITLE and not touch anything
else. This is not possible I can't see it yet. Sorry but no. Your raise does
not only move title it bothers my music.
--
Sent from:
Hi Reggie,
> How is it possible to simply? move a title of a piece vertical up?
%%% SNIPPET BEGINS
\version "2.19.80"
\bookpart {
\header {
title = \markup "My Default Title"
}
\score {
c''1
}
}
\bookpart {
\header {
title = \markup \raise #15 "My Higher Title"
}
How is it possible to simply? move a title of a piece vertical up? Without
moving the systems below first or any systems? I don't want to mess up
markup-system-spacing.minimum-distance or
markup-system-spacing.basic-distance or so on. Just move a title up Y offset
something amount without
On 2019-01-21 1:23 pm, David Kastrup wrote:
Aaron Hill writes:
Using \omit Fingering is supposed to eliminate Fingering grobs until
it is \undone. The problem is that \tweak also modifies the stencil,
cancelling out the effect of the \omit.
I fail to see the problem. You specify a specific
Gianmaria Lari writes:
> On Mon, 21 Jan 2019 at 14:57, Gianmaria Lari
> wrote:
>
>>
>>
>> On Mon, 21 Jan 2019 at 13:02, Valentin Villenave
>> wrote:
>>
>>> On 1/21/19, Andrew Bernard wrote:
>>> > Not sure how to do it with PianoStaff.
>>>
>>> That’s because of the Keep_alive_together
Aaron Hill writes:
> This variation works:
>
>
> \version "2.19.82"
> { \set fingeringOrientations = #'(left)
> \override Fingering.stencil = #(lambda (grob)
> (ly:make-stencil '() '(0 . 0) '(0 . 0)))
That's just #point-stencil .
>}
>
>
> Here we have a valid, albeit empty,
On Mon, 21 Jan 2019 at 14:57, Gianmaria Lari
wrote:
>
>
> On Mon, 21 Jan 2019 at 13:02, Valentin Villenave
> wrote:
>
>> On 1/21/19, Andrew Bernard wrote:
>> > Not sure how to do it with PianoStaff.
>>
>> That’s because of the Keep_alive_together engraver. Your layout block
>> should look
On 2019-01-21 6:04 am, Gianmaria Lari wrote:
Using your old code to draw a circle around finger number on the left
of
the note today I found a problem. When I use "\omit Fingering" the
compilation report me the error:
programming error: Infinity or NaN encountered
\omit Fingering
Here it
Hi Gianmaria,
> Using your old code to draw a circle around finger number on the left of the
> note today I found a problem. When I use "\omit Fingering" the compilation
> report me the error:
>
> programming error: Infinity or NaN encountered
Has nothing to do with my code, you rather
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Taking into account the hints I already gotten, I try to typeset songs
using multiple files and use \lilypondfile to include them into LaTeX
using scrartcl class (Koma).
Now I found out that the margins for the songs are different when
On 1/21/19, Rue wrote:
> I don't actually have this path. What I have is
> "/usr/share/lilypond/2.19.82/", but there's no vim folder though.
If you’ve installed LilyPond through your distribution’s packages,
then the relevant files should have already been put in
/usr/share/vim/, e.g.
"N. Andrew Walsh" writes:
>> The second file has its own paper block as follows:
>>
>> \paper {
>> #(set-paper-size "a3" 'landscape )
>> two-sided = "false"
That is _not_ how you specify a boolean value in LilyPond. You probably
want ##f here.
--
David Kastrup
From: "N. Andrew Walsh"
Date: Monday, January 21, 2019 at 8:30 AM
To: lilypond-user
Subject: Re: setting one book to landscape
There's one other matter here with this score: In the console output, I see
this:
Drawing systems. . .
warning: compressing over-full page by 24.5 staff-spaces
Hi List,
On Sat, Jan 19, 2019 at 12:39 PM N. Andrew Walsh
wrote:
>
> I have an input file with the following structure:
>
> \paper {
> #(set-default-paper-size "a3" )
> }
>
> \include "file 1 - content.ly"
> \include "file 2 - content.ly"
>
> \book {
> \include "file 1 - score.ly"
> }
>
>
I'm somewhat new to Vim and just started learning Lilypond, so I was
wondering if anyone with more experience might be able to share their
experience regarding workflow, plugins you're using, and in general, how
you've set up Vim as a comfortable environment for working with Lilypond.
Whether it's
On Fri, 23 Feb 2018 at 08:43, Gianmaria Lari
wrote:
>
> On 23 February 2018 at 00:53, Thomas Morley
> wrote:
>
>> 2018-02-22 11:03 GMT+01:00 Thomas Morley :
>> > 2018-02-22 10:58 GMT+01:00 Gianmaria Lari :
>> >> Dear Harm,
>> >>
>> >> thank you for your really nice help. Your fix worked well
Hi Valentin,
Great!
Re staff visibility in piano, that was going to be my comment also. But I
always say, give people what they want. At least lilypond lets you do it if
you like.
Andrew
On Mon, 21 Jan 2019 at 23:00, Valentin Villenave
wrote:
>
> That being said, I have never seen a piano
On 1/21/19, Andrew Bernard wrote:
> Not sure how to do it with PianoStaff.
That’s because of the Keep_alive_together engraver. Your layout block
should look like:
\layout {
\context {
\PianoStaff
\RemoveEmptyStaves
\remove "Keep_alive_together_engraver"
\override
Hi Gianmaria,
I know you can do this with GrandStaff and the score context settings shown
here.
Not sure how to do it with PianoStaff.
Andrew
%
\version "2.19.82"
rh = { \clef treble \repeat unfold 3 {a1 b1 c'1 d'1 \break}}
lh = { \clef bass s1*4 a1 1 1 1}
\score
{
\new GrandStaff <<
The following code prints three "lines" of music. The first and second
lines are two staff system (treble and bass) and the third line just one
staff (treble).
\version "2.19.82"
rh = { \clef treble \repeat unfold 3 {a1 b1 c'1 d'1 \break}}
lh = { \clef bass s1*4 a1 1 11}
\score
{
\new
On 1/21/19, Gianmaria Lari wrote:
> Is there any simple way to tie the last note contained in a variable?
> Here it is an example (that doesn't work).
It doesn’t work _yet_, but it will with the upcoming 2.21 release.
(You may already build a pre-release from the source code, but it’s a
bit
Is there any simple way to tie the last note contained in a variable?
Here it is an example (that doesn't work).
\version "2.19.82"
test = {a1}
{\test ~ a4}
Thank you, g.
___
lilypond-user mailing list
lilypond-user@gnu.org
44 matches
Mail list logo