Re: restrainOpenStrings

I just pointed out - I can live with this contradictories. So simply let me annul my question. Thanks On 13.09.2015 12:33, David Kastrup wrote: BB writes: If one interprets the text of the manual the line \set TabStaff.restrainOpenStrings = ##t powers up the not

Re: restrainOpenStrings

BB writes: > If one interprets the text of the manual the line > \set TabStaff.restrainOpenStrings = ##t > powers up the not really perfect working > \set TabStaff.minimumFret = #1 > to work as one would expect by simply interpreting the text implies. Huh? I quote:

restrainOpenStrings

I wonder that \set TabStaff.restrainOpenStrings = ##t is not enough to really avoid open strings? It only works together with \set TabStaff.minimumFret = #1 I can live with this need of this aditional line, but I find the logik is questionable. Is that done by will? Regards

Re: restrainOpenStrings

BB writes: > I wonder that > \set TabStaff.restrainOpenStrings = ##t > is not enough to really avoid open strings? > It only works together with > \set TabStaff.minimumFret = #1 > > I can live with this need of this aditional line, but I find the logik > is

Re: restrainOpenStrings

BB writes: > I just pointed out - I can live with this contradictories. So simply > let me annul my question. LilyPond's behavior and documentation is not supposed to be contradictory. So please point out any actual contradictions in the documentation or LilyPond's

Re: restrainOpenStrings

If one interprets the text of the manual the line \set TabStaff.restrainOpenStrings = ##t powers up the not really perfect working \set TabStaff.minimumFret = #1 to work as one would expect by simply interpreting the text implies. But that does not depreciate the basic question about the logik.

RE: Clef symbol after a barline

On Sat, 2015-09-12 at 14:10 -0700, Mark Stephen Mrotek wrote: > David, > > Here is a snippet. I am not sure where it is located in the manual, V 2.18. > > \once \override Score.BreakAlignment #'break-align-orders = #(make-vector 3 > '( staff-bar > clef > key-cancellation > key-signature >

Re: Unterminated tie

On Sun, 2015-09-13 at 00:46 +0200, Thomas Morley wrote: > 2015-09-13 0:11 GMT+02:00 David Sumbler : > > I have yet another problem related to repeats. The piece I am setting > > has one instrument which is tied from the last note in the > > first-time-bar to the note at the

Re: questions about chord ties to null and Ped. glyph

Thank you!!! -akj > On Sep 13, 2015, at 11:15 AM, David Kastrup wrote: > > \musicglyph #"pedal.Ped" ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: OT: Beauty of programming languages

While we are at it Age 73 - Married - North of England previous life Senior Scientific Oficer - Heat Transfer Mechanical Engineering Degree Struggling clarinet player and general music lover Started producing music scores using NoteWorthy Composer Graduated to LilyPond some years ago - still

Re: restrainOpenStrings

I read the manual. But please answer the question WHY should lilypond statements not do what the statement text straight implies? Obviously you have not read my postings, as I have 1. pointed out that I can handle the "contradictories" 2. quotation: "So simply let me annul my question."

Re: restrainOpenStrings

I try an explanation again: If a user says \set TabStaff.minimumFret = #5 I would expect that LP obeys and just uses no frets closer to the nut tha five. As you wrote, LP is unobedient and uses open strings against that imperative TabStaff.minimumFret = #5 ? On the other extreme if one sets

Re: restrainOpenStrings

I think the issue here is that David K has read the documentation (the NR, section 2.4.1) but BB probably hasn't, and is trying to guess what a lilypond command does from its name. This is always likely to be problematical. -- Phil Holmes - Original Message - From: BB To:

questions about chord ties to null and Ped. glyph

Two questions, I’m trying to write a chord with a tie to null space (see pic below). I tried 1 (<>) and only get one slur then I tried << {e1 (<>)} \\ {g! (<>)} \\ {b (<>)} \\ {e (<>)} >> and the notes are not vertically aligned suggestions? Second question: I’m trying to write a dynamic

Re: restrainOpenStrings

Am 13.09.2015 um 14:07 schrieb BB: I read the manual. But please answer the question WHY should lilypond statements not do what the statement text straight implies? IIRC, we discussed quite a lot about the new restrainOpenStrings functionality and how to name this new property. There were

Re: questions about chord ties to null and Ped. glyph

Alex Jones writes: > Two questions, > > I’m trying to write a chord with a tie to null space (see pic below). I tried > 1 (<>) and only get one slur > > then I tried > << {e1 (<>)} \\ {g! (<>)} \\ {b (<>)} \\ {e (<>)} >> > > and the notes are not vertically aligned > >

RE: Clef symbol after a barline

Welcome! Mark -Original Message- From: David Sumbler [mailto:da...@aeolia.co.uk] Sent: Sunday, September 13, 2015 6:21 AM To: Mark Stephen Mrotek Cc: lilypond-user@gnu.org Subject: RE: Clef symbol after a barline On Sat, 2015-09-12 at 14:10 -0700, Mark Stephen

Re: Fwd: Re: OT: Beauty of programming languages

I'm just about 6 weeks shy of 50, been programming computers for close to 20 years. I have been involved with deep database design, GUI design, and reporting over the years, I'm primarily a SQL jock now. I picked up Lilypond in early 2006, if the modified dates on my files are any indication.

Re: Fwd: Re: OT: Beauty of programming languages

At this point I can't even locate the LP 2.6.5 install package - so I'll be faced with a change when I need a new computer, and that is probably a shockingly small number of days. I figure I can figure something out for opening ly files - they are text after all. The custom editor was fun and

Re: Fwd: Re: OT: Beauty of programming languages

Edward Ardzinski writes: > Lilypond's set up immediately hooked me, I really have never used any > other manuscript programs, so my perspective is probably pretty > limited. And unique - as a programmer I created my own text > editor...now that the source code is

Re: OT: Beauty of programming languages

On Sun, Sep 13, 2015 at 6:47 PM, Flaming Hakama by Elaine < ela...@flaminghakama.com> wrote: > > Started composing in high school in the 1890s, > > Really? Wow! (1980s?) Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___

Re: OT: Beauty of programming languages

44 years old Day job: web development, mostly JavaScript these days, but I've used quite a number of others over the years (including APL). Started composing in high school in the 1890s, primarily Jazz and chamber music, with some larger works. I've been using Lilypond to produce scores for