Re: Catch direction operators
Am 29.09.2013 17:04, schrieb David Kastrup:
\new Voice \with { \mapList #colorizeDir Slur.StringNumber.TextScript }
\new Voice \with { \mapList #colorizeDir #(map (lambda (x) (car x))
all-grob-descriptions) }
Adds the option of coloring all grobs with a 'direction property.
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Catch direction operators
Urs Liska writes:
> Am 29.09.2013 17:04, schrieb David Kastrup:
>> \new Voice \with { \mapList #colorizeDir Slur.StringNumber.TextScript }
>
> \new Voice \with { \mapList #colorizeDir #(map (lambda (x) (car x))
> all-grob-descriptions) }
>
> Adds the option of coloring all grobs with a 'direction property.
I cringe whenever I see something like (lambda (x) (car x)). You are
aware that this is just an obfuscated version of car itself?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Catch direction operators
Am 01.10.2013 12:04, schrieb David Kastrup:
Urs Liska writes:
Am 29.09.2013 17:04, schrieb David Kastrup:
\new Voice \with { \mapList #colorizeDir Slur.StringNumber.TextScript }
\new Voice \with { \mapList #colorizeDir #(map (lambda (x) (car x))
all-grob-descriptions) }
Adds the option of coloring all grobs with a 'direction property.
I cringe whenever I see something like (lambda (x) (car x)). You are
aware that this is just an obfuscated version of car itself?
No. But I'm ready to learn.
What I want to achieve here (with the map) is a list of all cars of
all-grob-descriptions.
#(map (lambda (x) (car x)) all-grob-descriptions)
gives me what I want. So what would I have to do to make it cleaner/less
obfuscated?
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Catch direction operators
lambda (x) (car x) is exactly the same as car. You should be able to write
just
#(map car all-grob-descriptions)
instead.
2013/10/1 Urs Liska
> Am 01.10.2013 12:04, schrieb David Kastrup:
>
> Urs Liska writes:
>>
>> Am 29.09.2013 17:04, schrieb David Kastrup:
>>>
\new Voice \with { \mapList #colorizeDir Slur.StringNumber.TextScript }
>>> \new Voice \with { \mapList #colorizeDir #(map (lambda (x) (car x))
>>> all-grob-descriptions) }
>>>
>>> Adds the option of coloring all grobs with a 'direction property.
>>>
>> I cringe whenever I see something like (lambda (x) (car x)). You are
>> aware that this is just an obfuscated version of car itself?
>>
>> No. But I'm ready to learn.
> What I want to achieve here (with the map) is a list of all cars of
> all-grob-descriptions.
>
>
> #(map (lambda (x) (car x)) all-grob-descriptions)
>
> gives me what I want. So what would I have to do to make it cleaner/less
> obfuscated?
>
> Urs
>
>
> __**_
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/**listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Catch direction operators
Am 01.10.2013 12:17, schrieb Franciszek Boehlke: lambda (x) (car x) is exactly the same as car. You should be able to write just #(map car all-grob-descriptions) instead. Thanks. Now I see that it didn't _seem_ to work because I ran the wrong LilyPond version :-[ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Horizontal note spacing
I'm looking for a music writing program that will allow me to precisely control horizontal spacing for use in a psychology sight-reading study. Though I've found information on how to pad accidentals etc I was wondering if someone could help with a few more detailed horizontal spacing questions: (1) I need to be able to choose how wide a bar is (e.g. 3cm, or 1/8 the total page-width), and make each system's spacing the same. I'd need this width to be set regardless of what is in the bar. Is this possible? (2) I additionally need to define the distances between notes (i.e. ratio of 2 for each doubled duration) and I need this to be completely unaffected by accidentals- i.e I want no padding around accidentals. Is this possible? I'd really appreciate someone letting me know whether Lilypond would be an appropriate program to use for my study. Thanks, Lauren -- View this message in context: http://lilypond.1069038.n5.nabble.com/Horizontal-note-spacing-tp151701.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Horizontal note spacing
On 1 oct. 2013, at 13:59, LaurenH wrote: > I'm looking for a music writing program that will allow me to precisely > control horizontal spacing for use in a psychology sight-reading study. > Though I've found information on how to pad accidentals etc I was wondering > if someone could help with a few more detailed horizontal spacing questions: > > (1) I need to be able to choose how wide a bar is (e.g. 3cm, or 1/8 the > total page-width), and make each system's spacing the same. I'd need this > width to be set regardless of what is in the bar. Is this possible? > > (2) I additionally need to define the distances between notes (i.e. ratio of > 2 for each doubled duration) and I need this to be completely unaffected by > accidentals- i.e I want no padding around accidentals. Is this possible? > > I'd really appreciate someone letting me know whether Lilypond would be an > appropriate program to use for my study. Thanks, Lauren > LilyPond can probably do (2) via its proportional notation commands. (1) is possible if you make the line skip at each bar. Otherwise, you'd have to make changes to the C++ code used to compile the LilyPond executable. The changes wouldn't be complicated but would require working knowledge of C++. Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Horizontal note spacing
LaurenH writes: > I'm looking for a music writing program that will allow me to precisely > control horizontal spacing for use in a psychology sight-reading > study. You are probably best off writing your own program then. LilyPond does so many tweaks and finetunes and optical spacing and what else that it will take a lot of work to wrest control of horizontal spacing in its entirety from it. Now you can, like, use LilyPond's markup constructs in order to puzzle things together starting at music glyphs. Whether that is a more convenient path for you than just using any old program (or possibly Urs Liska's project of making LilyPond glyphs accessible to LaTeX) is a different question. It might also be worth looking at MusiXTeX, actually: one of its main nuisances is that you are yourself responsible for every tiny bit of spacing and collision avoidance and whatever. For your task, that might be rather an advantage. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Ties across repeats
How can you program ties across the alternative path of a repeat volta, to avoid untied notes or chords in the last part? Like in the included example. <>___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties across repeats
"Maarten de Keijzer" writes: > How can you ‘program’ ties across the alternative path of a repeat volta, > to avoid untied notes or chords in the last part? > Like in the included example. http://www.lilypond.org/doc/v2.16/Documentation/notation/writing-rhythms#index-repeatTie-1> -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Horizontal note spacing
I'm not completely sure of that, but disabling springs should be quite easy to do (in C++ code), and effect might be what is deserved, i.e. no smart spacing. However, it can result in lots of collisions in some cases. Maybe I'll try it today or tomorrow, I'd like to remind myself spring code a bit. 2013/10/1 David Kastrup > LaurenH writes: > > > I'm looking for a music writing program that will allow me to precisely > > control horizontal spacing for use in a psychology sight-reading > > study. > > You are probably best off writing your own program then. LilyPond does > so many tweaks and finetunes and optical spacing and what else that it > will take a lot of work to wrest control of horizontal spacing in its > entirety from it. > > Now you can, like, use LilyPond's markup constructs in order to puzzle > things together starting at music glyphs. Whether that is a more > convenient path for you than just using any old program (or possibly Urs > Liska's project of making LilyPond glyphs accessible to LaTeX) is a > different question. > > It might also be worth looking at MusiXTeX, actually: one of its main > nuisances is that you are yourself responsible for every tiny bit of > spacing and collision avoidance and whatever. For your task, that might > be rather an advantage. > > -- > David Kastrup > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Catch direction operators
Am 01.10.2013 12:19, schrieb Urs Liska:
Am 01.10.2013 12:17, schrieb Franciszek Boehlke:
lambda (x) (car x) is exactly the same as car. You should be able to
write just
#(map car all-grob-descriptions)
instead.
Thanks. Now I see that it didn't _seem_ to work because I ran the
wrong LilyPond version :-[
Hi again,
sorry to have to insist on perhaps basic questions.
As it is the function now works as I want, but not in 2.16.
From the versions I have available to test it works with 2.17.6 onwards
and not with 2.17.3 and less.
Somehow I suspect the change between 2.17.3 and .4
My best bet is that
#{ $@(map (lambda (s) #{ $colorizeDir $s #}) debug-direction-grob-list) #})
in the mapList function is the offending piece of code.
Is there a way to write this so it compiles both with 2.16.2 and with
current versions?
If that's not possible how would I achieve the same with 2.16.2 (I can
do a conditional include if necessary)?
Please refer to the attached version of the function.
TIA
Urs
\version "2.17.4"
% Define appearance
#(cond ((not (defined? 'debug-direction-up-color))
(define debug-direction-up-color darkgreen)))
#(cond ((not (defined? 'debug-direction-down-color))
(define debug-direction-down-color blue)))
#(cond ((not (defined? 'debug-direction-grob-list))
(define debug-direction-grob-list
(map car all-grob-descriptions
%%%
% Directions set with ^ and _ %
%%%
colorizeDir =
#(define-music-function (parser location item)
(symbol-list-or-music?)
(define (grob-colorize-dir grob)
(let ((ev (event-cause grob)))
(case (and ev (ly:event-property ev 'direction))
((1) debug-direction-up-color)
((-1) debug-direction-down-color)
(else '()
#{ \tweak color #grob-colorize-dir #item #})
mapList =
#(define-music-function (parser location)()
#{ $@(map (lambda (s) #{ $colorizeDir $s #}) debug-direction-grob-list) #})
\layout {
\context {
\Voice
\mapList
}
}
%%%
% Usage example
%%%
{
a4-.( b)
a4^( b)
\stemUp
a''8 g''( b)\noBeam c' \stemNeutral
c''4-3\4-"xy"
c''_3^\4^"xy"
c''^3_\4_"xy"
a'-. a'^.
g'\mf g'^\mf\>
a' b'\!^\< c''
b'\!
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Catch direction operators
Urs Liska writes:
> Am 01.10.2013 12:19, schrieb Urs Liska:
>> Am 01.10.2013 12:17, schrieb Franciszek Boehlke:
>>> lambda (x) (car x) is exactly the same as car. You should be able
>>> to write just
>>> #(map car all-grob-descriptions)
>>> instead.
>>>
>>
>> Thanks. Now I see that it didn't _seem_ to work because I ran the
>> wrong LilyPond version :-[
>>
>
> Hi again,
>
> sorry to have to insist on perhaps basic questions.
> As it is the function now works as I want, but not in 2.16.
> From the versions I have available to test it works with 2.17.6
> onwards and not with 2.17.3 and less.
> Somehow I suspect the change between 2.17.3 and .4
>
> My best bet is that
>
> #{ $@(map (lambda (s) #{ $colorizeDir $s #}) debug-direction-grob-list) #})
>
>
> in the mapList function is the offending piece of code.
No, that one's fine (uses 2.15.41+ functionality). But \tweak is quite
less versatile before 2.17.6.
> Is there a way to write this so it compiles both with 2.16.2 and with
> current versions?
You'll probably need to provide your own symbol-or-music? predicate (or
symbol-list-or-music?) and then split into \override and \tweak
depending on the argument. Or decide whether colorizeDir should do a
tweak or override, and then use it only for one of the two.
> Please refer to the attached version of the function.
Here is a rework based on the "only override" theory. Quite uglier and
less versatile. Also turns out that it barfs under 2.16.0 due to an
unsolved issue 2808, but it would appear that 2.16.1 already contains
the fix.
\version "2.16.1"
% Define appearance
#(cond ((not (defined? 'debug-direction-up-color))
(define debug-direction-up-color darkgreen)))
#(cond ((not (defined? 'debug-direction-down-color))
(define debug-direction-down-color blue)))
#(cond ((not (defined? 'debug-direction-grob-list))
(define debug-direction-grob-list
(map car all-grob-descriptions
%%%
% Directions set with ^ and _ %
%%%
colorizeDir =
#(define-music-function (parser location item)
(symbol?)
(define (grob-colorize-dir grob)
(let ((ev (event-cause grob)))
(case (and ev (ly:event-property ev 'direction))
((1) debug-direction-up-color)
((-1) debug-direction-down-color)
(else '()
#{ \override $(symbol->string item) #'color = #grob-colorize-dir #})
mapList =
#(define-music-function (parser location)()
#{ $@(map (lambda (s) #{ $colorizeDir $s #}) debug-direction-grob-list) #})
\layout {
\context {
\Voice
\mapList
}
}
%%%
% Usage example
%%%
{
a4-.( b)
a4^( b)
\stemUp
a''8 g''( b)\noBeam c' \stemNeutral
c''4-3\4-"xy"
c''_3^\4^"xy"
c''^3_\4_"xy"
a'-. a'^.
g'\mf g'^\mf\>
a' b'\!^\< c''
b'\!
}
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
missing bar numbers after manual line breaks within incomplete measures: bug or feature?
Hey all,
according to the NR "bar numbers are typeset by default at the start of every
line except the first line". In the following example the second line starts
with an incomplete measure which automatically results in a missing bar number.
I would expect a bar number at the beginning of the next complete measure.
What's the common practice here? Gould just generally recommends to "place bar
numbers at the beginning of each system" but she doesn't say anything about
lines starting with an incomplete measure. (I know the commands to make bar
numbers visible.)
\version "2.17.26"
{
\repeat unfold 4 {c'1} c'2 \bar ""
\break
c'2
\repeat unfold 20 {c'1}
}
tia
patrick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: missing bar numbers after manual line breaks within incomplete measures: bug or feature?
On 10/01/2013 04:17 PM, pls wrote: Hey all, according to the NR "bar numbers are typeset by default at the start of every line except the first line". In the following example the second line starts with an incomplete measure which automatically results in a missing bar number. I would expect a bar number at the beginning of the next complete measure. What's the common practice here? Gould just generally recommends to "place bar numbers at the beginning of each system" but she doesn't say anything about lines starting with an incomplete measure. (I know the commands to make bar numbers visible.) Hi Patrick, not an authority argument, but my two pence with the rationale behind: Any integer bar number at the start of the system would be misleading, as you probably figured. In your example, the proper number to place after the break would be 5.5, right? What if you put "5" there and the conductor tells the player to start "at measure 5"? That's beginning of the line, or back in time from the break? More general, there's a good point why the rule is avoid breaks inside a measure: keeping track of bar numbers is fairly easy, keeping track of accidentals can be more involved. Double-check for clarity there; I remember one song where my choir memorized a wrong note, probably for exactly this reason, and I had a really hard time correcting them when I conducted the piece years later. That being said, I also sometimes use in-measure line breaks if (I think) it makes sense. So far that's exclusively for canons with upbeats, where I want the systems to approximately line up, or songs - with several stanzas, - where the chorus comes first, - the stanzas start with a partial, and - ending the chorus system with a lot of first syllables looks terrible. In this case, I give a bar number to the first full measure in the new system, as you suggested; having to place it manually is okay IMHO, since you already enforced the break. Best, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: missing bar numbers after manual line breaks within incomplete measures: bug or feature?
On 01.10.2013, at 16:41, Alexander Kobel wrote: Hi Alexander, > > Any integer bar number at the start of the system would be misleading, as you > probably figured. In your example, the proper number to place after the break > would be 5.5, right? What if you put "5" there and the conductor tells the > player to start "at measure 5"? That's beginning of the line, or back in time > from the break? I certainly didn't want to suggest to have a bar number at the beginning of a line starting with an incomplete measure! That would be misleading, indeed! ;) > More general, there's a good point why the rule is avoid breaks inside a > measure: keeping track of bar numbers is fairly easy, keeping track of > accidentals can be more involved. Double-check for clarity there; I remember > one song where my choir memorized a wrong note, probably for exactly this > reason, and I had a really hard time correcting them when I conducted the > piece years later. > > That being said, I also sometimes use in-measure line breaks if (I think) it > makes sense. So far that's exclusively for canons with upbeats, where I want > the systems to approximately line up, or songs > - with several stanzas, > - where the chorus comes first, > - the stanzas start with a partial, and > - ending the chorus system with a lot of first syllables looks terrible. > In this case, I give a bar number to the first full measure in the new > system, as you suggested; having to place it manually is okay IMHO, since you > already enforced the break. I do a lot of conversions of MusicXML files to LilyPond. So most of the time I don't enforce the breaks manually but try to keep them were they were in the XML file. Some (short) pieces with several partials end up with no bar numbers at all after the conversion / compilation. My gut feeling is telling me that the first full measure in a new system should have a bar number by default. But I might be mistaken... thx patrick > > > Best, > Alexander ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re:Ties across repeats (David Kastrup)
>From: David Kastrup >To: lilypond-user@gnu.org >Subject: Re: Ties across repeats >"Maarten de Keijzer" writes: > How can you ?program? ties across the alternative path of a repeat > volta, to avoid untied notes or chords in the last part? > Like in the included example. http://www.lilypond.org/doc/v2.16/Documentation/notation/writing-rhythm s#index-repeatTie-1> >David Kastrup Great, that's exactly what I needed. As often: it is not that difficult, but hard to find ... Thanks, Maarten ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties across repeats (David Kastrup)
"Maarten de Keijzer" writes: >>From: David Kastrup >>To: lilypond-user@gnu.org >>Subject: Re: Ties across repeats >>"Maarten de Keijzer" writes: > >> How can you ?program? ties across the alternative path of a repeat >> volta, to avoid untied notes or chords in the last part? >> Like in the included example. > > http://www.lilypond.org/doc/v2.16/Documentation/notation/writing-rhythm > s#index-repeatTie-1> > >>David Kastrup > > Great, that's exactly what I needed. > As often: it is not that difficult, but hard to find ... It's in the notation manual in both the sections "Ties" and "Normal repeats", and it is in the index under "ties, repeating" "ties, alternative endings" "ties in repeats" "ties and volta brackets" "repeats, with ties" "repeating ties" and some others. If you are calling this "hard to find", what would you call "easy to find"? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Fedora 19 Lilypond and Vim
Hi, I am new to the group and just starting my Lilypond learning. I am using Fedora 17 and 19. My favorite editor is Vim but I am far from a power user. I am confused about syntax highlighting for Lilypond. The Lilypond website: http://www.lilypond.org/doc/v2.17/Do...editor-support suggests an entry into .vimrc such as: filetype off set runtimepath+=/usr/local/share/lilypond/current/vim/ filetype on My Fedora 19 version of Lilypond is 2.16.2 and has no such vim directory. My Fedora 17 version of Lilypond is 2.16.0 and also no such directory. Fedora 17 appears to use/or has at least, three files in the vim73 syntax directory; lilypond.vim, lilypond-words, and lilypond-words.vim. Vim73's syntax highlighting works although it may not be as developed as Frescobaldi's. My Fedora 19 install has the above three mentioned files installed in vim73's syntax directory but they are the only files as Fedora 19 now uses vim74. I copied them to vim74 but syntax highlighting does not yet work for me in Fedora 19. Helpful persons from the Fedora Forum have told me I should download files from github and put them into my home .vim folder. Are there differences in the quality or completeness of syntax highlighting of Lilypond files by Vim? I tried to contact the maintainer of the lilypond.vim syntax file but the Email is no longer used. Has anyone got vim up and running on Fedora 19 with Lilypond? Is anyone using Vim with Lilypond and found it to be as good or better than Frescobaldi? Namaste, Kevin Tough ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fedora 19 Lilypond and Vim
On 10/01 10:12 PM, Kevin Tough wrote:
> Hi,
>
> I am new to the group and just starting my Lilypond learning. I am using
> Fedora 17 and 19. My favorite editor is Vim but I am far from a power
> user. I am confused about syntax highlighting for Lilypond.
>
> The Lilypond website:
> http://www.lilypond.org/doc/v2.17/Do...editor-support
> suggests an entry into .vimrc such as:
>
> filetype off
> set runtimepath+=/usr/local/share/lilypond/current/vim/
> filetype on
Om Tat Sat, Kevin:
I use vim exclusively for my LilyPond use. I use it along with
Zathura as my pdf viewer. I believe that when I was using Fedora I
had to do the same thing that I have to do with ArchLinux:
create a file in your .vim directory named: filetype.vim
with the following code:
It will be easier if I just attach my filetype.vim.
Here ya go, should work fine.
Let me know if it doesn't though.
Hari Om,
Rachael
" ~/.vim/filetype.vim
if exists("did_load_filetypes")
finish
endif
" LilyPond Syntax highlighting
augroup filetypedetect
au! BufNewFile,BufRead *.ly setf lilypond
augroup END
" Mutt email syntax highlighting
augroup filetypedetect
" mail
autocmd BufRead,BufNewFile *mutt-* setfiletype mail
augroup END
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Flat flags
2013/10/1 Gilberto Agostinho : > Hi Thomas, > > Thank you so much for your help! Indeed this is very close to what I am > looking for, but there is a small catch: your code does not provide a result > identical to the \set stemLeftBeamCount = #0 note[]. The flags' position are > not matching the staff lines (look at the picture attached where all will be > cleared). Hi Gilberto, ofcourse your observations are correct. LilyPond's treating of flagged and beamed stems is different and results in different stem-lengths. Therefore I doubt that a new defined flag ever matches the behaviour of a modified beam. My coding of flat-flags matches exactly the way how old/modern-straight-flags are build. (A little fine-tuning might still be necessary.) You could try to adjust Stem.details-length to equal the behaviour of beamed/flagged stems, though, I doubt you'll find a generalized sollution. Attached you'll find the code again. Including some fine-tuning of flat-flag and a test-routine for some use-cases. (Note the different lengths for flagged and beamed stems in some cases.) For better viewing/comparing I played around with 'color and 'layer. I also added the default-values for Stem.details.lengths and Stem.details.beamed-lengths in case you really want to alter them. HTH, Harm flat-flags-01.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fedora 19 Lilypond and Vim
On Tue, 1 Oct 2013, Kevin Tough wrote: My Fedora 19 install has the above three mentioned files installed in vim73's syntax directory but they are the only files as Fedora 19 now uses vim74. I copied them to vim74 but syntax highlighting does not yet work for me in Fedora 19. I am using Vim and Fedora 19 and syntax highlighting is working. The change from vim73 to vim74 is something that should be reported to the lilypond packagers from Fedora. It's a little problem that keeps popping up from time to time when vim is updated. Copying/moving the files from the old vim73 to the new vim74 directory is the right thing to do. Not only the syntax directory. If you type "rpm -ql lilypond | grep vim" you will see the vim files that are packaged with Lilypond on Fedora. In my personal ~/.vimrc file I have: " LilyPond au BufNewFile,BufRead *.ly setf lilypond set autoindent set smartindent set tabstop=4 set shiftwidth=4 set expandtab filetype plugin indent on Unless you want to use the developers version 2.17.x, I would use the files from the official Fedora RPM version of LilyPond and make them work using the aove method. No need to get files from Git, or put stuff in /local/... directories manually. -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyJAZZ on 2.17
2013/10/1 Thomas Morley > > So I tried creating a symlink in my home: > > ln -s .local/share/fonts ~/.fonts > > > > And now it works! > > Do you think that it should be reported? lilypond binary should look in > > .local/share/fonts (it's the new font directory since Gnome 3) > > Well, not sure. At least it seems worth to notice. So yes. added: https://code.google.com/p/lilypond/issues/detail?id=3589 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Flat flags
Hi Harm, Thank you so much for this code. I realize now that it was not your flat-flag code that wasn't matching the old and modern-straight-flags, but actually it was the notes using \set stemLeftBeamCount x[] that were not matching them! Now I see that by using \set stemLeftBeamCount, the flags behave just like beams that were "cut" in half, and the position of beams are slightly differently than the normal flags. Thus I do not think it is necessary to play around with the stem length values. So thank you once again for all your help. Best regards, Gilberto On Tue, Oct 1, 2013 at 11:37 PM, Thomas Morley wrote: > 2013/10/1 Gilberto Agostinho : > > Hi Thomas, > > > > Thank you so much for your help! Indeed this is very close to what I am > > looking for, but there is a small catch: your code does not provide a > result > > identical to the \set stemLeftBeamCount = #0 note[]. The flags' position > are > > not matching the staff lines (look at the picture attached where all > will be > > cleared). > > Hi Gilberto, > > ofcourse your observations are correct. > > LilyPond's treating of flagged and beamed stems is different and > results in different stem-lengths. > Therefore I doubt that a new defined flag ever matches the behaviour > of a modified beam. > > My coding of flat-flags matches exactly the way how > old/modern-straight-flags are build. > (A little fine-tuning might still be necessary.) > > You could try to adjust Stem.details-length to equal the behaviour of > beamed/flagged stems, though, I doubt you'll find a generalized > sollution. > > Attached you'll find the code again. > Including some fine-tuning of flat-flag and a test-routine for some > use-cases. > (Note the different lengths for flagged and beamed stems in some cases.) > For better viewing/comparing I played around with 'color and 'layer. > I also added the default-values for Stem.details.lengths and > Stem.details.beamed-lengths in case you really want to alter them. > > HTH, > Harm > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Anki and LilyPond
Hi Urs, I've used Anki for a while now and also have thought about adding LilyPond content to flashcards. I suppose it would be a very nice idea, I will get started on them as soon as I am finished with my new batch of video tutorials on LilyPond for Beginners. Anki is solid - great idea Urs! :) Ben Urs Liska wrote > Hi list, > > I'm curious if anybody has some experience using Anki in conjunction > with LilyPond. > I've just discovered Anki and ponder over how useful it could be for me. > > As I've seen this LilyPond add-on: > https://github.com/frostschutz/Anki-LilyPond > I thought this could be terrific for creating musical teaching material. > And I thought whether this could be made useful for tutorial material > about LilyPond itself (maybe a shared deck of Anki cards accompanying > the Learning Manual). > > Any ideas? > Urs > > ___ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user - composer | sound designer -- View this message in context: http://lilypond.1069038.n5.nabble.com/Anki-and-LilyPond-tp150742p151723.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book help need!
Am 30.09.2013 19:56, schrieb Marcos Press: I'm not sure what is happening... LaTeX does not know any lilypond package. That's true, AFAIK. Lilypond-book gives these error always: ~$ lilypond-book --pdf --output=out file.lytex [...] File "/usr/lib/python2.7/re.py", line 242, in _compile raise error, v # invalid expression sre_constants.error: bad character range and nothing else happends. I can submit any info you ask for. Without /any/ hint about the contents of the file you want to process, it is merely impossible to tell you what's wrong. Can you post a minimal example? Reduce your file so that it is a) as small as possible and b) it still shows the error you describe. HTH, Marc ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
