Re: vim vagaries

J. wrote: I looked at the directions on the lilypond site for setting it up but, because of my noviciate I got confused with all the places and symbols. I found a page here: http://lilypond.org/doc/v2.12/Documentation/user/lilypond-program/Vim-mode It isn't clear which of those things you ha

Re: chord names in piano staff

> "henrik" == henrik pantle writes: henrik> hi, i wonder where to find the solution for my problem. i henrik> guess a lot of others do too. henrik> i want the chord names above the piano staff: You need to add a score block thus: guitarChords = \chordmode { ...} upper = \relative { ... }

Re: Orphaned and widowed lines in \markuplines

Le 10 nov. 2009 à 07:19, David Kastrup a écrit : Nicolas Sceaux writes: Le 9 nov. 2009 à 11:10, Jiri Zurek (Prague) a écrit : It happens to my scores that when using \markuplines for long texts (more than a page), Lilypond leaves a first or a last line orphaned (single, alone) on a pag

Double/Combination Trills

Hi all, I can't find any mention of an implementation of double or combination trill in the docs anywhere. Has anyone found a way to implement these (trills with two or more notes other than the principal note)? many thanks, piaras -- View this message in context: http://old.nabble.com/Do

upgrading

Hi, Perhaps a stupid question - is there any reason NOT to upgrade from 2.12.x to 2.13.7? Thanks, Gerard ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: upgrading

2009/11/11 Gerard McConnell : > Hi, Perhaps a stupid question -  is there any reason NOT to > upgrade from 2.12.x  to 2.13.7? Possibly. 2.13.7 could have changes in syntax, or experimental features. It worths it if you want to help testing it. -- Francisco Vila. Badajoz (Spain) www.paconet.org ww

Re: vim vagaries

Hi Jonathan, It's not to easy to find the right locations indeed, perhaps this might help. First you have to edit a file called filetype.vim, located in /home/yourusername/.vim/ If it isn't there, you can just create it: touch /home/yourusername/.vim/filetype.vim If the .vim directory isn

Re: upgrading

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Mittwoch, 11. November 2009 12:13:49 schrieb Gerard McConnell: > Hi, > Perhaps a stupid question - is there any reason NOT to > upgrade from 2.12.x to 2.13.7? If you are adjusting the vertical layout (staff spacing, padding etc.), then things wi

chordSymbols, arbitrary chord markup

Hi, I use \chordSymbols hack (http://lsr.dsi.unimi.it/LSR/Item?id=608) in my jazz charts and although, it works quite well in normal cases, it has some limitations: you can't write "C phryg" or combination of 6,7,9,11,13 not in the font etc. I read threads on jazz chords on this list as well (http

octave

Hi, a friend send me a score written with encore, I am "porting" it in lilypond. This score has 4 instruments, a sax, a cello and two pianos. Now, the part of the first piano has to be played an octave higher the what is written on the score, so the guy who has written it with encore has placed an

Re: octave

Hi. > Now, the part of the first piano has to be played an octave higher the > what is written on the score, so the guy who has written it with > encore has placed an "8" over the clefs of the piano staves. > > Is this a standard way to specify to play an octave higher? > If yes, how can I do thi

Re: octave

Use \set Staff.clefOctavation = #7 in the octavated staff See http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Displaying-pitches for details. Bert Francesco Petrogalli wrote: Hi, a friend send me a score written with encore, I am "porting" it in lilypond. This score has 4 instrum

Re: Quit

On Wed, 2009-11-11 at 00:44 -0500, lilypond-user-requ...@gnu.org wrote: > Also, the complaint here isn't that there's some inherent defect in > the program or the documentation, rather that you didn't want to > take > the time to learn how to use lilypond when you could do it in > sibelius fa

Re: series of up'n'down bows: /\\//\\/

user28 wrote: > > > is it possible to make they more compact? > with \textLengthOn you can make sure the next note or barline is starting when the text has been written. additionally you can move the starting position of your bows (which i replaced with \dmarcato) to the right if needed. {

Re: chordSymbols, arbitrary chord markup

Václav Šmilauer wrote: other than using \markup{...} in lyrics context for every single chord If your needs are met by (a possibly modifed) ChordNames most of the time, you can use replaceCN to deal with the impossible cases. http://lists.gnu.org/archive/html/lilypond-user/2009-04/msg00558.html

Re: Quit [now definitely O/T]

Hi Craig (et al.), I must say that the "faster" thing is a typical United States behavior. Whether or not it started in the USA, it's a worldwide phenomenon now. =) [Disclosure: I'm Canadian.] Our markets and media constantly barrage us with "time" issues. I think maybe "convenience"

Re: temporary staff for divisi

Dear community, I have a last question. Why is the shortInstrumentName for Violin one solo not shown? Here the snippet: \version "2.12.2" violineA = \context Staff ="ViolineA" { \set Staff.instrumentName = "Violine 1" \set Staff.shortInstrumentName="Vlne.1" c'' 4 d'' e'' f'' g'' a'' b'' c'

Re: quit

On Tue, Nov 10, 2009 at 9:01 PM, Erik Appeldoorn wrote: [...] > > On the plus I found, good looking scores, very flexible > On the minus I found, very tedious, time-consuming and heavily relying on > work-arounds. > > Hope this will give some inside. I won't say I'll never try again, but not > jus

Re: temporary staff for divisi

figured this one out: On 11 Nov 2009, at 14:56, Stefan Thomas wrote: I have a last question. Why is the shortInstrumentName for Violin one solo not shown? because the staff only just started. lily puts the instrumentName at the beginning of the first line of a staff. (naïve explanation, tryi

Re: Quit [now definitely O/T]

Kieren MacMillan writes: > Hi Craig (et al.), > >> I must say that the "faster" thing is a typical United States >> behavior. > > Whether or not it started in the USA, it's a worldwide phenomenon now. > =) > [Disclosure: I'm Canadian.] It is too cheap to put this down to "faster". The problem i

Re: modern accidentals rule

Frédéric Bron wrote: BTW, I have found a strange behaviour of "modern" accidentals rule: LilyPond considers volta alternatives as "previous" measure. Is this correct? (Note the natural sign at the 2nd and 3rd alternatives, not related to the previous _played_ measure.) Yes, this is known behavi

\override VerticalAxisGroup #'remove-empty works only at the beginning of a score

It seems that overriding #'remove-empty for Staff.VerticalAxisGroup has only an effect if it is called prior to the first note of the staff. Any \override VerticalAxisGroup #'remove-empty = ##t (or ##f) after the first note does not have any effect. Now, this is a problem, if the whole score

Re: chordSymbols, arbitrary chord markup

On 11/11/09 4:51 AM, "VáclavŠmilauer" wrote: > Hi, > > I use \chordSymbols hack (http://lsr.dsi.unimi.it/LSR/Item?id=608) in my jazz > charts and although, it works quite well in normal cases, it has some > limitations: you can't write "C phryg" or combination of 6,7,9,11,13 not in > the > fo

Re: \override VerticalAxisGroup #'remove-empty works only at the beginning of a score

Le 11 nov. 2009 à 16:07, Reinhold Kainhofer a écrit : Now, this is a problem, if the whole score consists of several different parts. For example, I have a choral score with fugues and a soprano solo. during the fugues, none of the staves should be removed (if e.g. the Alto sets in 9 measure

A barline half length long

Given that scheme calculations may be passed to the barLine bar-size property, I was attempting to draw a barLine which would be only a half length long vertically. When the size of the score is constant, it is not difficult to hard-code a specific bar-size, but since I use several staff sizes, it

Re: Quit [now definitely O/T]

Hi David, It is too cheap to put this down to "faster". The problem is not that you need longer to do some things with Lilypond initially. The problem is that there is a large number of things for which there is no proper way to do them at all, and you have to take out the crowbar. As is

Re: series of up'n'down bows: /\\//\\/

ok. cool. thanks for the tip. -- View this message in context: http://old.nabble.com/series-of-up%27n%27down-bows%3A---%5C%5C--%5C%5C--tp26295691p26304439.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-use

Re: A barline half length long

"Jiri Zurek (Prague)" writes: > \once \override Staff.BarLine #'bar-size = #(* ly:bar-line::calc-bar-size > 0.5) \bar "|" Try something like \once \override Staff.BarLine #'bar-size = #(lambda(x) (* 0.5 (ly:bar-line::calc-bar-size x))) \bar "|" It is probably possible to fabricate something

Re: Quit [now definitely O/T]

I don't see the "now definitely O/T" you put in the subject line. The subject was that somebody quit, and we are talking about the reasons. Kieren MacMillan writes: >> It is too cheap to put this down to "faster". The problem is not >> that you need longer to do some things with Lilypond init

Re: Quit [now definitely O/T]

Kieren MacMillan writes: [...] I don't see the "now definitely O/T" you put in the subject line. The subject was that somebody quit, and we are talking about the reasons. [...] >> It is too cheap to put this down to "faster". The problem is not >> that you need longer to do some things with

Re: Quit [now definitely O/T]

> I'm not topposting Third attempt because of topposting automoderation -- this _is_ a nuisance. Kieren MacMillan writes: [...] I don't see the "now definitely O/T" you put in the subject line. The subject was that somebody quit, and we are talking about the reasons. [...] >> It is too che

Re: A barline half length long

Jiri Zurek wrote: What is wrong with my syntax, please? ly:bar-line::calc-bar-size needs a parameter. If you get used to writing things like \override Staff.BarLine #'bar-size = #ly:bar-line::calc-bar-size you think that is all you ever need to say. But the functions for grob propertie

Re: Quit [now definitely O/T]

Hi David, I think that sums up very well why somebody would prefer not working with Lilypond. Not only do you have to rely on expert advice, but the main advice is "please do what an expert would do, or shut up". Please show me where I said anything resembling "shut up"...? I'm sorry if you i

Re: Quit [now definitely O/T]

Sorry for the post in triplicate. Gmane's response time confused me. Kieren MacMillan writes: > Hi David, > >> I think that sums up very well why somebody would prefer not working >> with Lilypond. Not only do you have to rely on expert advice, but the >> main advice is "please do what an exp

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 06:11:26PM +0100, David Kastrup wrote: > > Kieren MacMillan writes: > > > I couldn't agree more! [See Steps 1&2, above.] > > I think that sums up very well why somebody would prefer not working > with Lilypond. Not only do you have to rely on expert advice, but the > ma

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 07:12:44PM +, Graham Percival wrote: > Other than kidnap + torture, of course. I might vote for this, > but it strikes me that it might cause long-term problems... Addendum: I don't know the details that you want, so torturing me won't help. I'd *like* to know those d

Re: Quit [now definitely O/T]

Hi David, [By the way, since it's apparently open season on posting style criticism: your consistent lack of salutation and valediction in your posts makes you seem rude, curt, and above all patronizing.] "Reasonable" entails a collective effort not to repeat avoidable work and frustratio

Re: Quit [now definitely O/T]

Graham Percival writes: > On Wed, Nov 11, 2009 at 06:11:26PM +0100, David Kastrup wrote: > >> But if there is roadmap, design and vision, I have not yet been able >> to find it in the obvious places I have been looking for. > > The information for developers is the CG. The manuals don't tell an

Re: Quit [now definitely O/T]

Hi David (and anyone else who makes it here, wondering how to find the "CG"), The manuals don't tell anything about "CG", where it is, what it does. http://lilypond.org/web/devel/participating/> does not tell. There is no directory of that name in the distribution. Step 1: Go to home page.

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 08:47:33PM +0100, David Kastrup wrote: > > Graham Percival writes: > > > The information for developers is the CG. > > The manuals don't tell anything about "CG", where it is, what it does. > http://lilypond.org/web/devel/participating/> does not tell. There > is no dir

Re: Quit

Op woensdag 11-11-2009 om 20:08 uur [tijdzone +0100], schreef David Kastrup: > > As we both (all) know, there IS a "reasonable way to become an expert" > > at Lilypond > > No. A _reasonable_ way to become an expert is by reading into > increasingly more expert-level documentation and working wit

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 03:01:33PM -0500, Kieren MacMillan wrote: > Step 3: Click on "Documentation for LilyPond 2.13 (latest development)" > [since you're going to be helping with development, this is the logical > choice]. > Location: >> Not the

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 2:01 PM, Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi David (and anyone else who makes it here, wondering how to find the > "CG"), > > > The manuals don't tell anything about "CG", where it is, what it does. >> http://lilypond.org/web/devel/participating/>

Re: Quit [now definitely O/T]

Hi Graham, the "more available/obvious" choice would be to make the new website the main one. Currently, that's waiting on: - 2-5 hours of texinfo file editing I just pulled a new origin/master from git. Today, I've got upwards of 3 hours to code: what do you want me to work on? Cheers, K

Re: upgrading

On 11.11.2009, at 12:13, Gerard McConnell wrote: Hi, Perhaps a stupid question - is there any reason NOT to upgrade from 2.12.x to 2.13.7? Thanks, Gerard I tend to work from the "if it ain't broke, don't fix it" principle. So, unless there's something fundamentally broken that you absolu

Re: Quit [now definitely O/T]

Kieren MacMillan writes: > Hi David, > > [By the way, since it's apparently open season on posting style > criticism: your consistent lack of salutation and valediction in your > posts makes you seem rude, curt, and above all patronizing.] Perfectly accurate. >> "Reasonable" entails a collectiv

Re: Quit [now definitely O/T]

On 11/11/09 12:12 PM, "Graham Percival" wrote: > On Wed, Nov 11, 2009 at 06:11:26PM +0100, David Kastrup wrote: > >> But if there is roadmap, design and vision, I have not yet been able to >> find it in the obvious places I have been looking for. > > The information for developers is the CG.

Re: Quit

Jan Nieuwenhuizen writes: > Also seen several times are people sending /lots/ of questions, > be it users or developers, and after everything has been > answered, the user quits or potential developers says she has no > time or does not thing she is up for it after all. If the gist of the releva

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 03:19:37PM -0500, Kieren MacMillan wrote: > Hi Graham, > >> - 2-5 hours of texinfo file editing > > I just pulled a new origin/master from git. > Today, I've got upwards of 3 hours to code: what do you want me to work > on? The first thing that comes to mind is Alternate i

Re: Quit [now definitely O/T]

Hi David, Where does the GDP document the meaning of the acronym "GDP"? Here's one place (of many): It does not say what kind of code to put where for what reason.

Re: Quit [now definitely O/T]

Jonathan Kulp writes: > On Wed, Nov 11, 2009 at 2:01 PM, Kieren MacMillan < > kieren_macmil...@sympatico.ca> wrote: > > Hi David (and anyone else who makes it here, wondering how to find the > "CG"), > > > > The manuals don't tell anything about "CG", where it is, what it does. >

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 03:53:11PM -0500, Kieren MacMillan wrote: >> It does not tell you what language/classes/operations to use to >> implement what kind of task. > > OK, then submit a feature request — rant on -user does not count — and > maybe someone in the know will help out. No, please d

Re: Quit

On Wed, Nov 11, 2009 at 09:49:28PM +0100, David Kastrup wrote: > Jan Nieuwenhuizen writes: > > > Also seen several times are people sending /lots/ of questions, > > be it users or developers, and after everything has been > > answered, the user quits or potential developers says she has no > > ti

Re: Quit [now definitely O/T]

Graham, The first thing that comes to mind is Alternate input. Documentation/general/introduction.texi @node Alternate input I have to mao-ing learn TEXI now? So much for your "2-5 hours" estimate... Still-doing-it-but-thinking-there's-almost-definitely-a-better-way, Kieren. ___

Re: Quit [now definitely O/T]

David, Thanks for your willingness to articulate some concerns. I think that your careful thinking can be of real help to the LilyPond community, expecially if you can help us make things better. On 11/11/09 7:21 AM, "David Kastrup" wrote: > Kieren MacMillan writes: > >> Hi Craig (et al.),

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 04:05:59PM -0500, Kieren MacMillan wrote: >> The first thing that comes to mind is Alternate input. >> Documentation/general/introduction.texi >> @node Alternate input > > I have to mao-ing learn TEXI now? > So much for your "2-5 hours" estimate... I stand by my "2-5 hours

Re: Quit [now definitely O/T]

Carl Sorensen writes: > David, > > Thanks for your willingness to articulate some concerns. I think that > your careful thinking can be of real help to the LilyPond community, > expecially if you can help us make things better. Thanks for putting up with me. > On 11/11/09 7:21 AM, "David Kastr

Re: Quit [now definitely O/T]

>> @node Alternate input > > I have to mao-ing learn TEXI now? What's the problem here? If you don't want to do nifty things it's just a quite simple markup language. And since there has already been written a lot of TEXI documentation for lilypond I'm quite sure that you find examples for almo

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 9:33 PM, David Kastrup wrote: >> \spannerText "rit." >> b1\startTextSpan >> e,\stopTextSpan > > What is wrong with > b1\startSpan "rit." > e,\stopSpan > > ?  Why force meddling with an internal variable in the first place?  You > need the text anyway, why not make it part o

Manually place a clef object?

When a repeated section begins in one clef and ends in another (as in the Basso Continuo part I'm working on), it would be nice to be able to add a "reminder" clef at the end of the repeated section, to alert the player to return to the original clef when the repeat sign is reached. This behavio

Re: Quit [now definitely O/T]

Werner, What's the problem here? The problem is that I come to Lilypond with a skill set — specifically, many years of Java+Javascript+(X)HTML+XSL(T)+CSS+(La) TeX experience — which should be more than adequate for any modern documentation project involving a WWW component. I want to he

documentation formats

On Wed, Nov 11, 2009 at 05:47:28PM -0500, Kieren MacMillan wrote: > Werner, > >> What's the problem here? > > The problem is that I come to Lilypond with a skill set — specifically, > many years of Java+Javascript+(X)HTML+XSL(T)+CSS+(La)TeX experience — > which should be more than adequate for an

Re: Quit [now definitely O/T]

On Wed, 2009-11-11 at 22:33 +0100, David Kastrup wrote: > Carl Sorensen writes: > > The code to establish a ritardando could be easily written, and may (or may > > not) be done as part of the forthcoming GLISS (Grand LilyPond Input Syntax > > Stabilization) project. There's currently some disagre

Re: Quit [now definitely O/T]

On Nov 11, 2009, at 11:29 AM, David Kastrup wrote: For me, this situation is awkward, impeding and dissatisfactory. For others, it is reason to go away. I don't see that anything is gained for chastising me for my impression. That is merely shooting the messenger. Actually, more than the me

Re:Quit [now definitely O/T]

> > > > Things like "ritardando" can't be found in the > notation index and are > > programmed something like > > > >     Some performance indications, > e.g., rallentando or accelerando, are > >     written as text and are > extended over multiple notes with dotted lines. > >     Such objects, c

Re: chordSymbols, arbitrary chord markup

VáclavŠmilauer wrote: > > I use \chordSymbols hack (http://lsr.dsi.unimi.it/LSR/Item?id=608) in my > jazz > charts and although, it works quite well in normal cases, it has some > limitations: you can't write "C phryg" or combination of 6,7,9,11,13 not > in the > font etc. "C phryg" doesn't ex

Re: documentation formats

Hi Graham, If we did stuff in plain html, we'd lose the pdf docs. If we did stuff in plain latex, we'd lose the html docs (without a lot of tweaking). Both would lose the info docs, which IMO wouldn't be terrible, but some people seem to like. I don't even know what the "info docs" are, so I

Re: documentation formats

On Wed, Nov 11, 2009 at 06:39:26PM -0500, Kieren MacMillan wrote: > Hi Graham, > >> If we did stuff in plain html, we'd lose the pdf docs. If we did >> stuff in plain latex, we'd lose the html docs (without a lot of >> tweaking). Both would lose the info docs, which IMO wouldn't be >> terrible, b

Re: Quit [now definitely O/T]

David, I appreciate your persistence in this. I think that you are having part of the difficulty in this conversation because it's on -user, not on -devel. The modifications to anything except input files (which use lilypond code and embedded scheme) really involve knowledge that's primarily dis

Re: documentation formats

Graham Percival writes: > On Wed, Nov 11, 2009 at 05:47:28PM -0500, Kieren MacMillan wrote: >> Werner, >> >>> What's the problem here? >> >> The problem is that I come to Lilypond with a skill set — specifically, >> many years of Java+Javascript+(X)HTML+XSL(T)+CSS+(La)TeX experience — >> which

Re: documentation formats

Kieren MacMillan writes: > Hi Graham, > >> If we did stuff in plain html, we'd lose the pdf docs. If we did >> stuff in plain latex, we'd lose the html docs (without a lot of >> tweaking). Both would lose the info docs, which IMO wouldn't be >> terrible, but some people seem to like. > > I don'

Re: Manually place a clef object?

On 11.11.2009, at 22:37, Peter Kaplan wrote: When a repeated section begins in one clef and ends in another (as in the Basso Continuo part I'm working on), it would be nice to be able to add a "reminder" clef at the end of the repeated section, to alert the player to return to the origina

version 0.0.0-0

Hi, http://lilypond.org/web/install/ is showing version numbers 0.0.0-0 instead of 2.13.7-1 for the development branch. This is not the first time this has happened, so I guess there is someone who will fix this. -- Martin ___ lilypond-user mail

Re: Quit [now definitely O/T]

Carl Sorensen writes: > David, > > I appreciate your persistence in this. I think that you are having part of > the difficulty in this conversation because it's on -user, not on -devel. > > The modifications to anything except input files (which use lilypond code > and embedded scheme) really in