Hi Federico,
2015-10-10 20:36 GMT+02:00 Federico Bruni :
...
> Instead of "polluting" the lilypond sources with \tag(s), I'd rather set a
> custom field (level) in the \header block and write a script which parses
> the header and process the files accordingly.
>
...
I don't
Am 11.10.2015 um 03:58 schrieb Mark Stephen Mrotek:
Hello,
I recall that instructions were once given to achieve:
p ma ben marcato,
yet my search of the LSP was not successful.
Please direct me to its location.
Thank you for your kind attention.
Mark
If you need these ‘composite’ dynamics
Malte Meyn:
Thank you for the response and the location. Shall bookmark.
Mark
-Original Message-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Malte Meyn
Sent: Sunday, October 11, 2015 6:53 AM
To:
On Sat, 2015-10-10 at 14:40 -0500, David Wright wrote:
> Quoting Richard Shann (rich...@rshann.plus.com):
> > On Fri, 2015-10-09 at 23:37 +0200, Simon Albrecht wrote:
> > > On 09.10.2015 22:25, Richard Shann wrote:
> > > > In the 2.18 it does not seem to mention that the opus and piece fields
> >
Now that my current score has become large, Frescobaldi I am sorry to say the
text editor it provides runs like molasses on Ubuntu 15.04. Hence I am
abandoning it for emacs.
With the emacs lilypond-mode, C-c C-l invokes lilypond on the buffer. But I
need to specify directories to search for
Op Sat, 10 Oct 2015 13:48:39 +0200
Urs Liska schreef:
> The only way out of that would be if LilyPond could learn to take its
> input from stdin. Which might be a nice thing anyway?
I think LilyPond can :-)