On Thu, Sep 17, 2009 at 12:25:26AM +0200, Patrick Schmidt wrote:
> > Hmm. Maybe it's a problem with 2.13.3. I don't know about this
> > file in particular, but I now see that there definitely *are*
> > some files which require 2.13.4.
>
> I installed 2.13.4 and tried to build documentation. I'm
On 17.09.2009, at 03:08, Ralph Palmer wrote:
Or is there another helpful text editor (with highlighting), other
than jedit (with seems to be slow and resource intensive, in my
experience)?
There's a section that says vim has lilypond support, and nano
supports syntax hilighting. (And, al
Hi Ralph,
To my novice eyes, it seems there is one of two possible issues here:
1. The path indicated in your "init.el" file, which is supposed to
point to the lilypond-mode files in your LilyPond installation
folder is incorrect, or
2. "init.el" points to the place where the lilyp
Hi, I've been here before, but I've still got a problem.
I'm running Ubuntu (Jaunty Jackalope), Lilypond 2.12.2, and emacs 22.2.1.
Whenever I try to open a .ly file in emacs, I get :
File mode specification error: (file-error "Cannot open load file"
"lilypond-mode")
Has anyone else had this prob
Hello,
I did a quick exercise typsetting a Schumann score, and I'm puzzled
because to get the hairpin under the slur I had to turn up
'outside-staff-priority for the slur to be greater than 250. Otherwise,
the snippet below doesn't work correctly.
Reading the NR, it sounds like Lilypo
On 2009-09-16, Tim McNamara wrote:
>
> On Sep 16, 2009, at 9:31 AM, Robin Bannister wrote:
>
> >Tim McNamara wrote:
> >> The first coda glyph should be at the end of bar 28
> >
> >See LSR 432.Before the \break, add
> >\once \override Score.RehearsalMark #'break-visibility =
> >#begin-of-line
On Sep 16, 2009, at 9:31 AM, Robin Bannister wrote:
Tim McNamara wrote:
The first coda glyph should be at the end of bar 28
See LSR 432.Before the \break, add
\once \override Score.RehearsalMark#'break-
visibility = #begin-of-line-invisible
Good grief. But thank you,
And of course I replied only to myself, since the reply-to header is
not set to the mailing list for some reason.
Begin forwarded message:
From: Tim McNamara
Date: September 16, 2009 9:17:03 AM CDT
To: Tim McNamara
Subject: Re: Help with positioning coda glyph
On Sep 16, 2009, at 8:45 AM,
I'm trying to extract some Lilypond snippets to insert into a Word
document, and found a trick in the archives here:
\version "2.13.3"
%{
Austin collection of Mumming Plays
%}
\layout {
clip-regions
= #(list
(cons
(make-rhythmic-lo
Paul Malcolm schrieb:
Can anyone answer the following. I am a string (Viola) player and need
some special markings
in my sheet music. One is the usual semitone marker. This is like a
circumflex between two notes.
For example e f would be written roughly as e^f but with the
circumflex over
The easiest answer was :
\override Score.SpanBar #'break-visibility = #'#( #t #f #t )
Aha! Great -- I knew there'd be a way.
It wasn't _quite_ as simple as that, of course... To recap: I had a
GrandStaff holding a ChoirStaff (of 2 staffs) and a PianoStaff (of 2
Staffs). So I changed th
Mats Bengtsson schrieb:
Neil Thornock wrote:
Sorry about the last one!...
If you don't want stems at all:
\override Stem #'stencil = ##f
In many situations,
\override Stem #'transparent = ##t
may be preferrable, since many other objects need a stem to
attach to.
Yes, but I want the slur co
Neil Thornock wrote:
Sorry about the last one!...
If you don't want stems at all:
\override Stem #'stencil = ##f
In many situations,
\override Stem #'transparent = ##t
may be preferrable, since many other objects need a stem to
attach to.
/Mats
On Wed, Sep 16, 2009 at 10:30 AM, Marc Ho
Neil Thornock schrieb:
Sorry about the last one!...
If you don't want stems at all:
\override Stem #'stencil = ##f
I know, but if I do so, the (invisible) stems still have an influence on the
positioning of the slurs. I thought I could avoid this by setting the
Stem #'length appropriately.
Sorry about the last one!...
If you don't want stems at all:
\override Stem #'stencil = ##f
On Wed, Sep 16, 2009 at 10:30 AM, Marc Hohl wrote:
> Hi,
>
> I tried to manipulate the length of the stems but I got strange results.
> Please compile the following file:
>
>
If you don
On Wed, Sep 16, 2009 at 10:30 AM, Marc Hohl wrote:
> Hi,
>
> I tried to manipulate the length of the stems but I got strange results.
> Please compile the following file:
>
> ---
>
> \version "2.13.3"
>
> test = \relative c {
> << { c4 ( d\5 ) e ( f
Tim McNamara wrote:
The first coda glyph should be at the end of bar 28
See LSR 432.Before the \break, add
\once \override Score.RehearsalMark
#'break-visibility = #begin-of-line-invisible
LilyPond won't put the coda glyph at the beginning of bar 31.
At leas
Hi,
2009/9/14 Andrew Giddings
> Hi all,
>
> Does anyone know whether it's possible to automatically join the barlines at
> the ends of lines across all staffs?
>
> I'm writing a piece for SATB+piano -- a ChoirStaff of two staffs, above a
> PianoStaff of two staffs also, all combined in a GrandS
I am having problems getting LilyPond to properly position coda
glyphs. I've included the code to see if others reproduce it. The
first coda glyph should be at the end of bar 28 but LilyPond insists
on putting it at the end of bar 29. The /break command seems to be
involved (is this a bu
Andrew Giddings wrote:
I've searched the manual, the mailing list archive,
and the web, but I couldn't see anything directly relevant.
Did you see these?
http://lists.gnu.org/archive/html/lilypond-user/2007-07/msg00127.html
http://lsr.dsi.unimi.it/LSR/Search?q=semichoirstaff
Cheers
Hi all,
Does anyone know whether it's possible to automatically join the
barlines at the ends of lines across all staffs?
I'm writing a piece for SATB+piano -- a ChoirStaff of two staffs,
above a PianoStaff of two staffs also, all combined in a GrandStaff.
So normally each barline is spl
21 matches
Mail list logo
