Re: Table of Contents in Two Columns?
On Fri, Nov 1, 2019 at 6:05 PM Simon Albrecht wrote: > Unfortunately the latter. LilyPond isn’t equipped for that kind of text > processing; while markuplist can be used for pagebreakable markup, there > is no way of directing it into columns other than hard-coding breaks, > splitting it up and using \line or \table markup (list) commands. > > Your best bet to actually do this would be modifying paper size and/or > line-width for the book-part or book in which you have the TOC and using > external tools to produce the two-column layout. > I actually ended up doing a bit of coding to extract the data from "standard" one-column index in the PDF produced by Lilypond, fed the data into LaTeX to produce a nice-looking two column version, and then splicing in my index in place of the one in the Lilypond PDF. It seems to be working like a charm for me. Thanks for the advice, Sol -- Solomon Foster: colo...@gmail.com HarmonyWare, Inc: http://www.harmonyware.com
Re: scheme-question: matrix-operation
Thomas Morley writes: > Hi, > > lets say I've a list of sublists like '((1 2 3)(4 5 6)) > I want to modify it, the result should be '((1 3 5)(2 4 6)) > > This is a matrix-operation (not sure whether matrix is the correct > english term), on could write it graphically: > 1 2 3 > 4 5 6 > -> > 1 3 5 > 2 4 6 > > What's the best scheme-way to get it? What is it that you are doing? I don't see the principle you apply here. Changing '((1 2 3)(4 5 6)) to '((1 4) (2 5) (3 6)) is an obvious transformation, but your single example does not really give much of an idea of what you do. > All but the last sublist will be of equal lengths, the last may or may > not be shorter. -- David Kastrup
scheme-question: matrix-operation
Hi, lets say I've a list of sublists like '((1 2 3)(4 5 6)) I want to modify it, the result should be '((1 3 5)(2 4 6)) This is a matrix-operation (not sure whether matrix is the correct english term), on could write it graphically: 1 2 3 4 5 6 -> 1 3 5 2 4 6 What's the best scheme-way to get it? All but the last sublist will be of equal lengths, the last may or may not be shorter. Thanks, Harm
Re: Scoped variables
-
Sunday, November 3, 2019, 2:24:10 PM, David Kastrup wrote:
> Peter Toye writes:
>> Is there a case for introducing scoped variables into Lilypond?
>> As I understand it (please correct me if I'm wrong), variables have to be
>> declared at the top of the document, before any music expression. I'm trying
>> to work on a document with many different scores, each if which is in its
>> own file. According to what I gather is best practice I use variables to
>> hold the basic music text: one variable for each staff. When engraving each
>> individual score, I need to put its variable declarations at the head of its
>> file. But when I want to gather them all together into a book or bookpart,
>> this doesn't work, so each score has to be edited to remove the definitions.
>> One way round this would be to allow Lilypond variables to be defined
>> within bookparts and/or scores, and to give them a scope confined to
>> that section. See the following MNWE.
> So what happens with
> bla = c'
> sc = \score { \bla }
> \book {
> bla = f'
> \sc
> }
> There are similar considerations for defining and using bookparts
> outside of books: basically the question is
> what scopes you even want to
> be talking about, lexical or dynamical, and how the two would be
> supposed to interact.
Good question. It would need deciding and documenting. I agree there are two
interpretations of what the writer might want. The simplest (IMO) would be to
use lexical scope: sc is defined outside the \book and would use the global
version of bla, so the output would be c'. If there were a music expression
using bla inside the \book, it would use the local version and output f'. By
allowing one to define sc and bla within the \score one could write each score
independently of others, and name clashes would be avoided.
That's something I failed to do in a multi-movement work before deciding that I
might want it as a book:-(> As it is, six or seven staves over 8 movements is a
lot of variable names to keep organised. I would prefer to keep the variable
name the same for the content of each staff with the same instrument. It also
means that when engraving each movement separately I don't have to keep track
of exactly which variable definitions I need at the very top of the document
(although I suppose the excess definitions don't hurt too much, except in
storage space in the compiler).
Regards,
Peter
Re: Fedora 31, Python3, Frescobaldi
Il giorno ven 1 nov 2019 alle 10:22, Martin Tarenskeen ha scritto: Just upgraded to Fedora 31. Maybe this is not the right place to report this, but I'm seeing this in my terminal when updating my packages: Problem 1: package frescobaldi-3.0.0-10.fc31.noarch requires python3-sip, but none of the providers can be installed - package sip-4.19.19-1.fc31.x86_64 obsoletes python3-sip < 4.19.19-1.fc31 provided by python3-sip-4.19.18-6.fc31.x86_64 - cannot install the best update candidate for package python2-sip-4.19.18-6.fc31.x86_64 - cannot install the best update candidate for package frescobaldi-3.0.0-10.fc31.noarch Problem 2: problem with installed package frescobaldi-3.0.0-10.fc31.noarch - package frescobaldi-3.0.0-10.fc31.noarch requires python3-sip, but none of the providers can be installed - package sip-4.19.19-1.fc31.x86_64 obsoletes python3-sip < 4.19.19-1.fc31 provided by python3-sip-4.19.18-6.fc31.x86_64 - cannot install the best update candidate for package python3-sip-4.19.18-6.fc31.x86_64 -- See https://src.fedoraproject.org/rpms/frescobaldi/c/f7fd91a956649f3015eb7332922fcf2f861a730e?branch=master Those commits are in master but may be merged also in f31 branch? Contact the maintainer if you want to know more.
Re: Scoped variables
On 03/11/2019 12:54, Peter Toye wrote:
Scoped variables Is there a case for introducing scoped variables into
Lilypond?
As I understand it (please correct me if I'm wrong), variables have to
be declared at the top of the document, before any music expression.
I'm trying to work on a document with many different scores, each if
which is in its own file. According to what I gather is best practice
I use variables to hold the basic music text: one variable for each
staff. When engraving each individual score, I need to put its
variable declarations at the head of its file. But when I want to
gather them all together into a book or bookpart, this doesn't work,
so each score has to be edited to remove the definitions.
There are ways to use Lilypond's variable syntax to manage
multi-instrument, multi-movement pieces such as this skeleton for a two
movement string quartet.
\version "2.19.83"
I.Violin.1 = { \clef "treble" b'1 }
I.Violin.2 = { \clef "treble" g' }
I.Viola = { \clef "alto" d' }
I.Cello = { \clef "bass" g1 }
II.Violin.1 = { \clef "treble" c''1 }
II.Violin.2 = { \clef "treble" e' }
II.Viola = { \clef "alto" g' }
II.Cello = { \clef "bass" c1 }
\book {
\bookpart {
\score {
<<
\new Staff { \I.Violin.1 }
\new Staff { \I.Violin.2 }
\new Staff { \I.Viola }
\new Staff { \I.Cello }
>>
}
}
\bookpart {
\score {
<<
\new Staff { \II.Violin.1 }
\new Staff { \II.Violin.2 }
\new Staff { \II.Viola }
\new Staff { \II.Cello }
>>
}
}
}
--
Timothy Lanfear, Bristol, UK.
Re: Frescobaldi LilyPond Log
Problem solved for LilyPond log font size using AutoHotkey. Thanke for the help from Ben (sounds from sound). Thank you all, fg On Sat, Nov 2, 2019 at 11:10 PM Ben wrote: > On 11/2/2019 10:57 PM, Freeman Gilmore wrote: > > > > On Sat, Nov 2, 2019 at 10:51 PM Ben wrote: > >> On 11/2/2019 10:16 PM, Freeman Gilmore wrote: >> >> >> >> On Sat, Nov 2, 2019 at 9:59 PM Ben wrote: >> >>> On 11/2/2019 9:31 PM, Freeman Gilmore wrote: >>> >>> >>> >>> On Sat, Nov 2, 2019 at 9:26 PM Ben wrote: >>> On 11/2/2019 8:16 PM, Freeman Gilmore wrote: Is there a way to make the font larger in the Frescobaldi, LilyPond Log? Thank you, ƒg Yes, you can hover the mouse over the log and use the mouse wheel + control key to change font size. :) >>> Is there a way to simulate the Wheel? I use a touchpad. >>> Thank you, >>> ƒg >>> >>> >>> There can be yes, but it depends. What hardware are you using? Laptop >>> brand/model? What OS? >>> >> I have a Dell that has a Simulated Wheel, touchpad is designed for it >> but i do not use that for Frescobaldi. The touchpad keyboard i am >> using does not know how many fingers i am using on the pad. Just thinking >> there could be so way to set the keys to simulate a wheel. Probably not. >> Thank you, >> ƒg >> >> Hi, >> >> Right. But are you running Windows on that Dell or a Linux flavor? I'm >> just going to guess and assume Windows. >> >> If so, it's pretty easy to setup an AutoHotKey script to simulate a mouse >> scroll wheel up/down so that's what I would do if you don't have/can't get >> access to a mouse. >> > Windows but i would not have a clue. I will try to find how. > Thanks you. > ƒg > > No problem, I got you. :) > > Here's what you do: > > *First, download AutoHotKey.* > > https://www.autohotkey.com/download/ahk-install.exe > > Install it, defaults are fine. > > *Then, download this script to your desktop (it's an .AHK file) - a script > that maps the entire NUMPAD to mouse controls.* > > https://www.autohotkey.com/docs/scripts/NumpadMouse.ahk > > (you only need to worry about the scroll options which is NUM add / NUM > sub ( + -) > > *Then, double click the AHK file to "run it". You should see the icon in > your tray now.* > > That's it! :) > > *Now, if you hold CONTROL + the NUMPAD minus or plus, you can scroll the > font size in Frescobaldi log files.* > > Just tested it, works beautifully. > > Just make sure you have SCROLL LOCK for this to work. > > When you're finished and the log is the right size, you can always close > the script from your tray and go back to whatever you had. > > Hope this helps! > > > > > */* > oo > |Using Keyboard Numpad as a Mouse| > () > | By deguix / A Script file for AutoHotkey 1.0.22+ | > || > || > |This script is an example of use of AutoHotkey. It uses | > | the remapping of numpad keys of a keyboard to transform it | > | into a mouse. Some features are the acceleration which | > | enables you to increase the mouse movement when holding| > | a key for a long time, and the rotation which makes the| > | numpad mouse to "turn". I.e. NumpadDown as NumpadUp| > | and vice-versa. See the list of keys used below: | > || > || > | Keys | Description| > || > | ScrollLock (toggle on)| Activates numpad mouse mode. | > |---|| > | Numpad0 | Left mouse button click. | > | Numpad5 | Middle mouse button click. | > | NumpadDot | Right mouse button click. | > | NumpadDiv/NumpadMult | X1/X2 mouse button click. (Win 2k+)| > | NumpadSub/NumpadAdd | Moves up/down the mouse wheel. | > | || > |---|| > | NumLock (toggled off) | Activates mouse movement mode. | > |---|| > | NumpadEnd/Down/PgDn/ | Mouse movement.| > | /Left/Right/Home/Up/ || > | /PgUp || > | || > |---|| > | NumLock (toggled on) | Activates mouse speed adj. mode. | > |---|| > | Numpad7/Numpad1 | Inc./dec. acceleration
Re: Scoped variables
Peter Toye writes:
> Is there a case for introducing scoped variables into Lilypond?
>
> As I understand it (please correct me if I'm wrong), variables have to be
> declared at the top of the document, before any music expression. I'm trying
> to work on a document with many different scores, each if which is in its own
> file. According to what I gather is best practice I use variables to hold the
> basic music text: one variable for each staff. When engraving each individual
> score, I need to put its variable declarations at the head of its file. But
> when I want to gather them all together into a book or bookpart, this doesn't
> work, so each score has to be edited to remove the definitions.
>
> One way round this would be to allow Lilypond variables to be defined
> within bookparts and/or scores, and to give them a scope confined to
> that section. See the following MNWE.
So what happens with
bla = c'
sc = \score { \bla }
\book {
bla = f'
\sc
}
There are similar considerations for defining and using bookparts
outside of books: basically the question is what scopes you even want to
be talking about, lexical or dynamical, and how the two would be
supposed to interact.
--
David Kastrup
Re: \woodwind-diagram shift problem
Le dim. 3 nov. 2019 à 13:44, Thomas Morley a écrit : > I'd delete all occurrencies of \center-column, makes no sense. > Oops, my mistake, copy/paste typo... Cheers, Pierre
Scoped variables
Is there a case for introducing scoped variables into Lilypond?
As I understand it (please correct me if I'm wrong), variables have to be
declared at the top of the document, before any music expression. I'm trying to
work on a document with many different scores, each if which is in its own
file. According to what I gather is best practice I use variables to hold the
basic music text: one variable for each staff. When engraving each individual
score, I need to put its variable declarations at the head of its file. But
when I want to gather them all together into a book or bookpart, this doesn't
work, so each score has to be edited to remove the definitions.
One way round this would be to allow Lilypond variables to be defined within
bookparts and/or scores, and to give them a scope confined to that section. See
the following MNWE.
\version "2.19.52"
\language "english"
\book {
\bookpart {
music = { f''4 4 4 4 }
\score {
\new Staff
{
\time 4/4
\music
}
}
}
\bookpart {
music = { e''4 4 4 }
\score {
\new Staff
{
\time 3/4
\music
}
}
}
}
I realise that this would probably be a major change, and so I hesitate to
suggest it formally unless there is a consensus of opinion in its favour. It
would however make "bottom-up" document production a lot easier, as local
information would be encapsulated. This, after all, has been best practice in
language design for some time now.
What do the experts think?
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
Re: \woodwind-diagram shift problem
Am So., 3. Nov. 2019 um 11:39 Uhr schrieb Jacques Menu : > > Hello folks, > > In the attached sample, the diagrams in the second measure are shifted right, > and the second one is much above the others. > > Any hint is welcome! > > JM Hi Jacques, I'd delete all occurrencies of \center-column, makes no sense. And apply \textLengthOn \override TextScript.X-align-on-main-noteheads = ##f \override TextScript.parent-alignment-X = 0 At least it works for me. Cheers, Harm
Re: \woodwind-diagram shift problem
Hi Jacques,
I think is due to the narrow chords and the markups layer/extents
conflicts. So, not surprising.
As a workaround:
\version "2.19.82"
#(set-global-staff-size 20)
\header {
% title = "Saxophone fingerings"
title = "Doigtés du saxophone"
instrument = ""
}
\layout {
indent = 0\cm
\context {
\Score
\remove "Bar_number_engraver"
}
}
\paper {
paper-width = 29.7\cm
paper-height = 21.0\cm
ragged-last-bottom = ##f
}
% uncomment to print all key possibilities to the log
%#(print-keys-verbose 'soprano-saxophone (current-error-port))
%#(print-keys-verbose 'saxophone (current-error-port))
{
\clef "treble"
\omit Staff.TimeSignature
\hide TupletBracket
\hide TupletNumber
\tuplet 3/2
{
2-1^\markup {
\raise #2.0
\center-column {
\woodwind-diagram
#'soprano-saxophone
#'(
(cc . (one two three five))
(lh . ())
(rh . ())
)
}
}
-2^\markup {
\raise #2.0
\center-column {
\woodwind-diagram
#'soprano-saxophone
#'(
(cc . (one two three six))
(lh . ())
(rh . ())
)
}
}
-3^\markup {
\raise #2.0
\center-column {
\woodwind-diagram
#'soprano-saxophone
#'(
(cc . (one two three four))
(lh . ())
(rh . (high-fis))
)
}
}
}
\tuplet 3/2
{
2-1
-\tweak X-offset #-2
^\markup\center-align {
\raise #2.0
\center-column {
\woodwind-diagram
#'soprano-saxophone
#'(
(cc . (one two three five))
(lh . (T))
(rh . ())
)
}
}
-2
-\tweak X-offset #-1
^\markup\center-align {
\raise #2.0
\center-column {
\woodwind-diagram
#'soprano-saxophone
#'(
(cc . (one two three six))
(lh . (T))
(rh . ())
)
}
}
-3
^\markup\center-align {
\raise #2.0
\center-column {
\woodwind-diagram
#'soprano-saxophone
#'(
(cc . (one two three four))
(lh . ())
(rh . (high-fis))
)
}
}
}
}
HTH, cheers,
Pierre
Le dim. 3 nov. 2019 à 11:39, Jacques Menu a écrit :
> Hello folks,
>
> In the attached sample, the diagrams in the second measure are shifted
> right, and the second one is much above the others.
>
> Any hint is welcome!
>
> JM
>
>
>
>
>
>
\woodwind-diagram shift problem
Hello folks, In the attached sample, the diagrams in the second measure are shifted right, and the second one is much above the others. Any hint is welcome! JM SaxophoneFingeringsProblem.ly Description: Binary data
