hello list,
has anybody written or transcribed music for harmonium (pump organ) ?
Circled numbers/letters show the organ stops, and slashed circles are used
when the organ stop is deactivated (example image from Rossini's Petite
messe solennelle").
So far I've used "nVier = \markup { {\circle 4
Hi David,
> how did you implement those functions?
Below is a snippet that contains the three functions, and an example usage.
Hope this helps!
Kieren.
%% SNIPPET BEGINS
\version "2.19.49"
\language "english"
ignoreH =
#(define-music-function (parser location item) (symbol-list-or-music?)
Karlin High writes:
>>From: Graham Percival
>>Sent: Saturday, December 3, 2016 3:35 PM
>>
>>If there was a single mentor for the new contributor, and if other
>>people didn't make well-intentioned but ultimately misleading
>>suggestions, we could
On Sun, Dec 04, 2016 at 04:06:53AM +, Karlin High wrote:
> >From: Graham Percival
> >Sent: Saturday, December 3, 2016 3:35 PM
> >
> >If there was a single mentor for the new contributor, and if other
> >people didn't make well-intentioned but ultimately misleading
>From: Graham Percival
>Sent: Saturday, December 3, 2016 3:35 PM
>
>If there was a single mentor for the new contributor, and if other
>people didn't make well-intentioned but ultimately misleading
>suggestions, we could have avoided 95% of this mess.
Dunno quite,
Urs Liska wrote
> Am 01.12.2016 um 17:59 schrieb David Kastrup:
>
>> What is up with Frescobaldi? The last commit was 2 months ago. Trivial
>> patches sent to Wilbert don't get applied and no answer comes back.
>>
>
> I can only assume that Wilbert is even more busy than usual (from some
>
Jan-Peter Voigt wrote
> the edition-engraver is not part part of lilypond proper (yet).
>
> For a long time docs for the edition-engraver are on my agenda, but ...
>
> Thanks for poking me to restart action on this matter!
>
> Jan-Peter
>
> Am 02.12.2016 um 01:45 schrieb SoundsFromSound:
>>
On Sat, Dec 03, 2016 at 03:39:58PM -0800, Graham Percival wrote:
> On Sat, Dec 03, 2016 at 11:08:00PM +0100, Simon Albrecht wrote:
> > On 03.12.2016 22:35, Graham Percival wrote:
> > >A wiki is never the right answer.
> >
> > Please elaborate :-) Because it’s too open for everyone to alter?
>
>
On Sat, Dec 03, 2016 at 11:08:00PM +0100, Simon Albrecht wrote:
> On 03.12.2016 22:35, Graham Percival wrote:
> >A wiki is never the right answer.
>
> Please elaborate :-) Because it’s too open for everyone to alter?
Because "somebody else" will fix it. Also, it adds yet one more
place that
On 03.12.2016 22:35, Graham Percival wrote:
On Sat, Dec 03, 2016 at 08:45:30PM +0100, David Kastrup wrote:
Karlin High writes:
I like Urs Liska's idea of having a wiki or contributor guide entry for
web developer work.
Yes, it makes sense.
A wiki is never the right
On Sat, Dec 03, 2016 at 08:45:30PM +0100, David Kastrup wrote:
> Karlin High writes:
>
> > I like Urs Liska's idea of having a wiki or contributor guide entry for
> > web developer work.
>
> Yes, it makes sense.
A wiki is never the right answer.
Karlin's suggestion of
On Fri, Dec 02, 2016 at 07:50:50PM +0100, Jean-Charles Malahieude wrote:
> I've already given it a try, but get stopped by some errors I don't know how
> to resolve (I've no knowledge about perl). Three patches are available for
> anybody willing to help me… I can compile the English version,
On Thu, Dec 01, 2016 at 08:10:17PM -0500, Paul wrote:
> I just wish that working with texinfo (for the website) was more intuitive
> for contributors who know HTML but not texinfo. For example, an HTML
> element with an id and also a number of classes, all used for styling it
> with CSS. I don't
Contributing to LilyPond is not easy; there are a number of
technical and social challenges that make it daunting, especially
for people who have not contributed to mature open-source projects
before.
The best way to address this is by having a mentor. An
experienced developer can help guide you
On Dec 3, 2016, at 8:19 AM, Kieren MacMillan
wrote:
> Right now, I have the syntactic sugar \ignoreH, \ignoreV, and \ignore (both H
> and V) which I put in front of objects when I want to adjust their effect on
> spacing — but it would be nice to have a
Am 03.12.2016 um 11:42 schrieb Federico Bruni:
> At least we would have a concise list of requirements for the next
> person who will offer to renovate the website.
A good suggestion.
___
lilypond-user mailing list
lilypond-user@gnu.org
Karlin High writes:
> On 12/3/2016 4:42 AM, Federico Bruni wrote:
>> John, you resisted more than I would have expected. I wonder if we'll
>> ever see "the best person for _this_ job".
>
> And, I have been admiring John's patience and flexibility. He faced more
> resistance
On 12/3/2016 4:42 AM, Federico Bruni wrote:
> John, you resisted more than I would have expected. I wonder if we'll
> ever see "the best person for _this_ job".
And, I have been admiring John's patience and flexibility. He faced more
resistance than I would have expected. Work on the website
Hear hear!
P
On 12/03/2016 10:19 AM, Kieren MacMillan wrote:
Hi all,
Or perhaps have a distinction between things like { s4 } and { c4\rest } ?
I think we should distinguish between “skips” [which take up no space,
horizontal or vertical], “spacers” [which take up space, but are
Hi all,
> Or perhaps have a distinction between things like { s4 } and { c4\rest } ?
I think we should distinguish between “skips” [which take up no space,
horizontal or vertical], “spacers” [which take up space, but are invisible],
and visible objects (like rests, notes, etc).
My suggestion:
On 12/3/2016 5:06 AM, Simon Albrecht wrote:
> I think it would be a valid request to have s-rests take up the
> respective space with proportional spacing.
Or perhaps have a distinction between things like { s4 } and { c4\rest } ?
--
Karlin High
Missouri, USA
On 12/03/2016 06:26 AM, David Kastrup wrote:
Simon Albrecht writes:
On 03.12.2016 02:36, PMA wrote:
The score setup already calls for proportional
notation.
I think it would be a valid request to have s-rests take up the
respective space with proportional spacing.
> On 3 Dec 2016, at 13:18, Hans Aikema wrote:
>
> Ponders,
>
> Anyone else using coloring in scores, using lilypond unstable and spotting
> coloring-issues when generating scores?
>
> I spotted a horrible output for a score I created for beamer in our church
>
Ponders,
Anyone else using coloring in scores, using lilypond unstable and spotting
coloring-issues when generating scores?
I spotted a horrible output for a score I created for beamer in our church
service and upon futher inspection it appears caused by only partial coloring
of the score
Am 3. Dezember 2016 11:42:35 MEZ, schrieb Federico Bruni :
>Il giorno gio 1 dic 2016 alle 1:48, John Roper
>
>ha scritto:
>> Why specifically do we *need* to use textinfo? If I could make a new
>> system that would auto generate the docs that works
Simon Albrecht writes:
> On 03.12.2016 02:36, PMA wrote:
>> The score setup already calls for proportional
>> notation.
>
> I think it would be a valid request to have s-rests take up the
> respective space with proportional spacing.
I don't think s rests should mess
On 03.12.2016 12:06, Simon Albrecht wrote:
On 03.12.2016 02:36, PMA wrote:
The score setup already calls for proportional
notation.
I think it would be a valid request to have s-rests take up the
respective space with proportional spacing.
P.S. I don’t know any other use cases, though, so
On 03.12.2016 02:36, PMA wrote:
The score setup already calls for proportional
notation.
I think it would be a valid request to have s-rests take up the
respective space with proportional spacing. Would you mind sending a
concise request, with a small example, to bug-lilyp...@gnu.org?
Il giorno gio 1 dic 2016 alle 1:48, John Roper
ha scritto:
Why specifically do we *need* to use textinfo? If I could make a new
system that would auto generate the docs that works with the current
system would you use it?
Good question, if limited to the website (don't
29 matches
Mail list logo