Re: Use "simple strings" rather than #"hash-prefixed Scheme strings" (issue 363910043 by v.villen...@gmail.com)

2019-02-10 Thread Joram
> commit 7e39a11c08e6a2a321a2da9c81bd0c62ff6da006 Sorry for the noise and thanks for the change! ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Use "simple strings" rather than #"hash-prefixed Scheme strings" (issue 363910043 by v.villen...@gmail.com)

2019-02-10 Thread David Kastrup
Joram writes: > Hi, > > Am 10.02.19 um 19:41 schrieb carl.d.soren...@gmail.com: >> Simple strings -- don't need # > > Sometimes they do: > > \markup \with-url #"http://lilypond.org; "abc" > works. > > \markup \with-url "http://lilypond.org; "abc" > doesn't. Which version? -- David Kastrup

Re: Use "simple strings" rather than #"hash-prefixed Scheme strings" (issue 363910043 by v.villen...@gmail.com)

2019-02-10 Thread Joram
Hi, Am 10.02.19 um 19:41 schrieb carl.d.soren...@gmail.com: > Simple strings -- don't need # Sometimes they do: \markup \with-url #"http://lilypond.org; "abc" works. \markup \with-url "http://lilypond.org; "abc" doesn't. Cheers, Joram ___

Re: Use "simple strings" rather than #"hash-prefixed Scheme strings" (issue 363910043 by v.villen...@gmail.com)

2019-02-10 Thread David Kastrup
thomasmorle...@gmail.com writes: > On 2019/02/10 18:41:33, Carl wrote: >> Because this represents a change in the documentation policy as listed > in the >> CG, I think it should be discussed. > >> In the past, one could get along by saying "All properties start with > #", even >> though it

Re: Use "simple strings" rather than #"hash-prefixed Scheme strings" (issue 363910043 by v.villen...@gmail.com)

2019-02-10 Thread thomasmorley65
On 2019/02/10 18:41:33, Carl wrote: Because this represents a change in the documentation policy as listed in the CG, I think it should be discussed. In the past, one could get along by saying "All properties start with #", even though it wasn't strictly necessary. With this new change,

Use "simple strings" rather than #"hash-prefixed Scheme strings" (issue 363910043 by v.villen...@gmail.com)

2019-02-10 Thread Carl . D . Sorensen
Because this represents a change in the documentation policy as listed in the CG, I think it should be discussed. While it is easier to not put the hash before the simple string, it is harder to have to understand which elements need the hash and which do not. I think that having the hash is

Segfault when attempting to create an undefined grob. (issue 349840043 by v.villen...@gmail.com)

2019-02-10 Thread nine . fierce . ballads
It's certainly an improvement. A user might appreciate seeing the input location in the error message. https://codereview.appspot.com/349840043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: note-name-engraver: add user-defined note names support (issue 221710044 by v.villen...@gmail.com)

2019-02-10 Thread dak
https://codereview.appspot.com/221710044/diff/60001/lily/general-scheme.cc File lily/general-scheme.cc (right): https://codereview.appspot.com/221710044/diff/60001/lily/general-scheme.cc#newcode150 lily/general-scheme.cc:150: LY_DEFINE (ly_rassoc, "ly:rassoc", I am not sure this is wanted

PATCHES - Countdown for Feb 10th

2019-02-10 Thread James Lowe
Hello, Here is the current patch countdown list. The next countdown will be on February 13th A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ Push: 5464 New feature: automatically invert chords or drop/rise chord