Re: LSR search not working?

Done. Cheers, Pierre 2016-02-04 23:45 GMT+01:00 Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com>: > OK I'll take a look at it tomorrow. > Cheers, > Pierre > > 2016-02-04 23:12 GMT+01:00 Thomas Morley : > >> 2016-02-04 13:43 GMT+01:00 Pierre Perol-Schneider >> : >> > Hi Nick, >> > >> > T

Re: LilyBin.com wedged?

On Thu, Feb 4, 2016 at 7:52 PM, Simon Albrecht wrote: > On 05.02.2016 02:14, Steve Lacy wrote: > >> It looks like lilybin.com is internally wedged or >> something? The right hand side is just showing a "please wait" spinner for >> me, and the "Preview" button is greyed. >> >

Re: LilyBin.com wedged?

On 05.02.2016 02:14, Steve Lacy wrote: It looks like lilybin.com is internally wedged or something? The right hand side is just showing a "please wait" spinner for me, and the "Preview" button is greyed. No problem here. Just try again :-) Best, Simon _

LilyBin.com wedged?

It looks like lilybin.com is internally wedged or something? The right hand side is just showing a "please wait" spinner for me, and the "Preview" button is greyed. Steve ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman

Tie and slur in opposite directions

Hello, I find the output from the following example quite unpleasant due to the different directions of slur and tie. What do you think? Do the ‘authorities’ say anything on the topic? Curiously, I can’t find a corresponding example for a downward slur and upward tie right now. Slurs have a st

Direction of tie from Completion_heads_engraver

Hello, is there any possibility to tweak direction of a tie generated via the Completion_heads_engraver? The following tweaks both don’t work: %%% \version "2.19.36" \layout { \context { \Voice \remove "Note_heads_engraver" \consists "Completion_heads_engraver" } } {

Re: LSR search not working?

OK I'll take a look at it tomorrow. Cheers, Pierre 2016-02-04 23:12 GMT+01:00 Thomas Morley : > 2016-02-04 13:43 GMT+01:00 Pierre Perol-Schneider > : > > Hi Nick, > > > > This snippet has not been approved yet. Therefor, it is not taken into > > account is the searching algorithm. > > Cheers, > >

Re: LSR search not working?

2016-02-04 13:43 GMT+01:00 Pierre Perol-Schneider : > Hi Nick, > > This snippet has not been approved yet. Therefor, it is not taken into > account is the searching algorithm. > Cheers, > Pierre > > 2016-02-04 12:16 GMT+01:00 Nick Payne : >> >> There is an LSR snippet for Baroque lute tablature at

Re: Re: automatic line-breaking in markup

2016-02-04 8:01 GMT+01:00 Jonathan Scholbach : > Nice! Thank you, Harm! Actually I have (unarguable) reasons to put the title > in a string variable. Am I missing something? In my example title _is_ a string > But since I do not understand anything of the code in > your snippet I cannot manage t

Re: mac web fontconfig slowdown

I seem to have found a fix ... Message: 5 Date: Wed, 3 Feb 2016 19:06:21 -0500 From: Jim Tisdall To: lilypond-user@gnu.org Subject: mac web fontconfig slowdown Message-ID: <56b295fd.5040...@tisdall.net> on mac os x 10.11.2, lilypond 2.18.2, plenty nice mac pro plenty ram Serious slowdown due

Re: LSR search not working?

Hi Nick, This snippet has not been approved yet. Therefor, it is not taken into account is the searching algorithm. Cheers, Pierre 2016-02-04 12:16 GMT+01:00 Nick Payne : > There is an LSR snippet for Baroque lute tablature at > http://lsr.di.unimi.it/LSR/Item?id=920, which contains the phrase >

Re: access font-size of clef G_8

Hi David, > Sorry, but the question is nonsensical. Well, people like me who don't understand it, sometimes don't know how to ask. > Grob properties are inherited through the context hierarchy. An > engraver acting in a particular context will see properties set in this > context. If they aren

Re: access font-size of clef G_8

Noeck writes: > Thanks David for the explanation! The first part is clear now. > >> Also a) changes a single context definition while b) changes all context >> definitions that have an alias of "Score" as well (for "Score" that's >> rather unlikely, but for "Staff" there are a lot more candidates

LSR search not working?

There is an LSR snippet for Baroque lute tablature at http://lsr.di.unimi.it/LSR/Item?id=920, which contains the phrase "baroque lute tablature" in both the title and text. However, it isn't found if I search using any or all of those terms... Nick Payne __

Re: access font-size of clef G_8

Thanks David for the explanation! The first part is clear now. > Also a) changes a single context definition while b) changes all context > definitions that have an alias of "Score" as well (for "Score" that's > rather unlikely, but for "Staff" there are a lot more candidates). That's interesting

Re: Very fast typesetting regardless of beauty?

Am 04.02.2016 um 11:20 schrieb Simon Albrecht: > On 04.02.2016 02:51, Isaac Reilly wrote: >> And since it will always be rendering to a single page wide enough to >> hold it all on one line, I'd like to turn off the line break >> calculations. > > At least there are the ly:one-line-breaking and >

Re: Very fast typesetting regardless of beauty?

On 04.02.2016 02:51, Isaac Reilly wrote: And since it will always be rendering to a single page wide enough to hold it all on one line, I'd like to turn off the line break calculations. At least there are the ly:one-line-breaking and ly:one-line-auto-height-breaking (only from 2.19.36) algorit

Re: Fwd: Re: automatic line-breaking in markup

Noeck writes: > Hi Jonathan, > >> It would be very kind of you if you did even that for me. > > Like this? > > #(define variablename "Your Title") > > \header { > title = #variablename > } > > { a } More LilyPondish: variablename = "Your Title" \header { title = \variablename } [...] --

Re: Fwd: Re: automatic line-breaking in markup

Hi Jonathan, > It would be very kind of you if you did even that for me. Like this? #(define variablename "Your Title") \header { title = #variablename } { a } HTH, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/