Hello,
I don't know if this could help: the only dependencies problem I had with
the "MIDI part" was that 'aubio' didn't compile with OS X 10.9 (making the
'sudo port upgrade outdated' unusable).
'aubio' is part of the dependencies of 'portmidi', but the outdated version
works (it's only the "upg
A fully indexed PDF portfolio of the Extending, Internals, Learning,
Notation, Snippets, Usage, and Web manuals is available at
https://www.dropbox.com/s/sm35zura3iuptay/lilydoc-2.17.95.pdf (53MB).
Needs Adobe Reader 9.x or later.
Nick
___
lilypond
Hello Davide,
on my system (OSX 10.9) frescobaldi(-devel) fails because portmidi doesn’t
compile - I see lots of C errors in the log.
I completely re-installed MacPorts (and that’s a lot).
Can you make the MIDI stuff optional? Perhaps via a variant +no-midi?
Greetlings, Hraban
---
fiëé visuëll
Davide Liessi-2 wrote
> I'm pleased to announce that Frescobaldi and python-poppler-qt4 have been
> included in MacPorts!
Congrats Davide! This is great news. Thanks for all your work on this. I
successfully completed a frescobaldi-devel install from MacPorts using your
helpful guide.
The onl
Bric wrote
> So, can one throw in conditionals?
>
> (1) Can one, for instance, check/manifest the pitch and duration of
> '#the-music' ? And based on those values are, write something or not?
>
> (2) And how DOES one write something extra? For example, add a note, or
> add a \markup (again,
Bric wrote
> but none of them work. Obviously, I don't know where scheme ends and
> lilypond code begins, in the above, and I don't even know scheme that
> well. (By the way, I think I read the relevant parts of the
> documentation, as much as I could find. I couldn't find stuff on this
> l
On 11/05/2013 07:51 PM, David Kastrup wrote:
Bric writes:
On 11/05/2013 03:08 PM, David Kastrup wrote:
Paul Morris writes:
But I think what you really want is a music function:
\version "2.17.29"
boo =
#(define-music-function
(parser location the-music)
(ly:music?)
#{
2013/11/7 Steve Noland :
> Thanks! Following your recommendation worked fine.
I'm glad it worked. I updated the instructions accordingly.
Best wishes.
Davide
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/li
2013/11/7 Garrett McGilvray :
[...]
> I do have Mac OS 10.9, which apparently was causing problems earlier, but
> that was since reported as fixed.
I understand that you upgraded from a previous version of Mac OS X;
did you follow the instructions at
https://trac.macports.org/wiki/Migration?
[..
Davide,
Thanks! Following your recommendation worked fine.
Regards,
Steve
On Nov 6, 2013, at 4:27 PM, Davide Liessi wrote:
> 2013/11/7 Steve Noland :
>> I have tried to follow the instructions in your new page, and when I attempt
>> to uninstall frescobaldi and/or python-poppler-qt4, I get t
2013/11/7 Steve Noland :
> I have tried to follow the instructions in your new page, and when I attempt
> to uninstall frescobaldi and/or python-poppler-qt4, I get the following
> error message:
>
> Error: port uninstall failed: Registry error: Please specify the full
> version as recorded in the p
Note: Apologies to Davide for the double message. I forgot to Reply All the
first time.
On Nov 6, 2013, at 9:16 AM, Davide Liessi wrote:
> Dear users of Frescobaldi and Mac OS X,
>
> I'm pleased to announce that Frescobaldi and python-poppler-qt4 have
> been included in MacPorts! [1] [2]
> Th
Dear Davide,
Thanks for the inclusion into ports!
I have tried to follow the instructions in your new page, and when I attempt to
uninstall frescobaldi and/or python-poppler-qt4, I get the following error
message:
Error: port uninstall failed: Registry error: Please specify the full version
a
Am 06.11.2013 19:07, schrieb Joseph Rushton Wakeling:
I would imagine it should work well with your own Lilypond examples
project?
Oh my, of course!
Why didn't I think of this myself???
___
lilypond-user mailing list
lilypond-user@gnu.org
https://li
Joseph Rushton Wakeling writes:
> On 06/11/13 17:06, Urs Liska wrote:
>> Really?
>> From my experience publishers don't have/make problems with giving a free
>> licence to use such an excerpt for such a purpose.
>
> IIRC stuff in the LSR is supposed to be dedicated to the public
> domain, and th
On 06/11/13 17:06, Urs Liska wrote:
Really?
From my experience publishers don't have/make problems with giving a free
licence to use such an excerpt for such a purpose.
IIRC stuff in the LSR is supposed to be dedicated to the public domain, and
there's no way I can see to do that.
Anyway, i
On 06/11/13 18:55, David Kastrup wrote:
That would be the case even if Ferneyhough were not British to start
with.
Your other points are fine, but what's Ferneyhough's nationality got to do with
it?
FWIW, he's been resident in the US for 25+ years now, and his publisher is
German ...
_
Tim Roberts writes:
> Urs Liska wrote:
>> Am 06.11.2013 16:39, schrieb Joseph Rushton Wakeling:
>>> > On 05/11/13 07:44, Werner LEMBERG wrote:
>> Please submit this snippet to the LSR!
>>> > He can't, it's the actual beginning of Ferneyhough's score and so
>>> > under copyright.
>> Really?
Tim Roberts schrieb:
>Urs Liska wrote:
>> Am 06.11.2013 16:39, schrieb Joseph Rushton Wakeling:
>>> > On 05/11/13 07:44, Werner LEMBERG wrote:
>> Please submit this snippet to the LSR!
>>> > He can't, it's the actual beginning of Ferneyhough's score and so
>>> > under copyright.
>> Real
Urs Liska wrote:
> Am 06.11.2013 16:39, schrieb Joseph Rushton Wakeling:
>> > On 05/11/13 07:44, Werner LEMBERG wrote:
>>> >> Please submit this snippet to the LSR!
>> > He can't, it's the actual beginning of Ferneyhough's score and so
>> > under copyright.
> Really?
> From my experience publish
Am 06.11.2013 16:39, schrieb Joseph Rushton Wakeling:
On 05/11/13 07:44, Werner LEMBERG wrote:
Please submit this snippet to the LSR!
He can't, it's the actual beginning of Ferneyhough's score and so
under copyright.
Really?
From my experience publishers don't have/make problems with giving
On 05/11/13 07:44, Werner LEMBERG wrote:
Please submit this snippet to the LSR!
He can't, it's the actual beginning of Ferneyhough's score and so under
copyright.
The notation is cool, though, and I'm sure it's easy to come up with a similar
example that is original.
_
Dear users of Frescobaldi and Mac OS X,
I'm pleased to announce that Frescobaldi and python-poppler-qt4 have
been included in MacPorts! [1] [2]
This means that the procedure for installing Frescobaldi is now
greatly simplified.
You can find the new installation instructions at [3] (Italian transl
Scott Miller writes:
> Does the lilypond project accept bitcoin donations?
Ok, this is not "The LilyPond project" as such, but if you want to
support my (full-time) work on LilyPond specifically, you can try so
using the address 1Kw7HZMd8L52BCL9vEjSxdPG4p3phRvtQF but please don't
transfer any la
2013/10/30 Jean-Alexis Montignies :
> Don’t try to do update on Mavericks (MacOS 10.9) as QT is currently not
> compiling.
> If installed before upgrading to 10.9, Frescobaldi continues to work.
The problem is now (apparently) solved:
https://trac.macports.org/ticket/40852
https://trac.macports.o
Urs Liska wrote
> The issue is that the LSR file is written for 2.14, and the syntax has
> changed in the meantime: \markuplines is now \markuplist.
> That's what David is referring to with his advice to use convert-ly.
The only indication that I could find on the LSR site that the snippets are
f
Ralph Palmer writes:
> On Wed, Nov 6, 2013 at 5:34 AM, David Kastrup wrote:
>
>> David Kastrup writes: Did I dream this?
>>
>> Oh good grief. https://codereview.appspot.com/6742057/#msg7>. And
>> that's all.
>
>
> Thank you, David - for this
Well, not for that. I wrote a detailed explanatio
On Wed, Nov 6, 2013 at 5:34 AM, David Kastrup wrote:
> David Kastrup writes: Did I dream this?
>
> Oh good grief. https://codereview.appspot.com/6742057/#msg7>. And
> that's all.
Thank you, David - for this and for all you do. Lilypond would be much
worse off without your help!
Ralph
--
R
Joshua Nichols writes:
> I want to apologize for inciting any frustration... I guess in my small
> mind (with limited understanding of TeX systems and the like) I thought
> when a particular documentation supported using a command that I associate
> with LaTeX, (such as the preverbal \begin and \
David Kastrup writes:
> David Kastrup writes:
>
>> Johan Vromans writes:
>
>>> Unfortunately, the relevant documentation page
>>> http://lilypond.org/doc/v2.17/Documentation/notation/set-versus-override
>>> is a bit, eh, empty...
>>
>> Uh, I'm pretty sure I wrote a rather carefully phrased trea
David Kastrup writes:
> Johan Vromans writes:
>> Unfortunately, the relevant documentation page
>> http://lilypond.org/doc/v2.17/Documentation/notation/set-versus-override
>> is a bit, eh, empty...
>
> Uh, I'm pretty sure I wrote a rather carefully phrased treatise about
> this in general. But
Aha, thank you! I wasn't aware of this before.
Best, Jan-Peter
Am 06.11.2013 10:29, schrieb Urs Liska:
> \override and \revert a property will result in the default value of
> that property
> \temporary\override and \revert will result in the value the property
> had before the override, but not
ah, thank you, now I see. I didn't ran into this before or probably just
wondered, why it doesn't work as I expected and then did something else.
Best, Jan-Peter
Am 06.11.2013 10:33, schrieb David Kastrup:
> If you use \override/\revert as previously, the behavior will be as
> previously: any pre
Jan-Peter Voigt writes:
> Hello all,
>
> I didn't follow the discussions about temporary and push-+-pop. Is there
> a simple explanation for the indroduction of \temporary? Why does
> \override-\revert now has to be \temporary\override-\revert?
Because it can.
If you use \override/\revert as pr
Am 06.11.2013 10:27, schrieb Jan-Peter Voigt:
Hello all,
I didn't follow the discussions about temporary and push-+-pop. Is there
a simple explanation for the indroduction of \temporary?
On a user-level (apart from push and pop) it means:
\override and \revert a property will result in the de
Hello all,
I didn't follow the discussions about temporary and push-+-pop. Is there
a simple explanation for the indroduction of \temporary? Why does
\override-\revert now has to be \temporary\override-\revert?
AFAICS it was introduced sometime in the 2.17 development and it will be
for better lil
Johan Vromans writes:
> David Kastrup writes:
>
>> Correct. In stack terms, \revert is a "pop" while "\override" is "pop,
>> push" (each context has its own stack). In contrast,
>> "\temporary\override" is just "push". So a sequence of
>
> So we have, for context properties:
>
> \set
David Kastrup writes:
> Correct. In stack terms, \revert is a "pop" while "\override" is "pop,
> push" (each context has its own stack). In contrast,
> "\temporary\override" is just "push". So a sequence of
So we have, for context properties:
\setset prop to value
\unset
Am 06.11.2013 07:05, schrieb Joshua Nichols:
I guess in the end I didn't understand anything at all, and my hard
head saw LaTeX and didn't see "preprocessed with lilypond-book."
Maybe this is a good opportunity to hook in.
If there is anybody out there experienced with LaTeX and Lua I'd be glad
39 matches
Mail list logo
