> Heikki, I don't think there's any need for those complicated regexps for
> matching strings and comments. If you remove "font-lock-keywords-only",
> the fontification works perfectly well using just the syntax table, and
> it recognises strings within strings, comments within comments...
Hmm. B
I just found an undocumented feature in my accidentals patch,
illustrated by the following ex.
\score {
\context Voice \notes \transpose c'' {
\property Staff.autoAccidentals = #'(Staff (any-octave . 0))
< cis'1 c > < c cis' >
}
\paper {
linewidt
On Tue, Apr 16, 2002 at 10:01:12PM +0200, Rune Zedeler wrote:
> Chris Jackson wrote:
>
> >Because they're recognised by the syntax table, and don't need a
> >multi-line regexp to match them. As they should in lilypond...
>
> How comes that c++ comments are easier to recognise than
> lilypond-c
Chris Jackson wrote:
> Because they're recognised by the syntax table, and don't need a
> multi-line regexp to match them. As they should in lilypond...
How comes that c++ comments are easier to recognise than
lilypond-comments...???
-Rune
___
Lil
Heikki Johannes Junes wrote:
>>Hmmm, then why does C-mode multi line comments work?
> Hmmm. You are right.
> + Set 'font-lock-multiline' true.
What should that do?
I get no difference...
-Rune
___
Lilypond-devel mailing list
[EMAIL PROTECTED
On Tue, Apr 16, 2002 at 08:36:20PM +0200, Rune Zedeler wrote:
> Heikki Johannes Junes wrote:
>
> >>When the mode is invoked (when a file is read or with M-x LilyPond-mode)
> >>then all multi-line schemes and multi-line comments are correctly
> >>parsed. But if you edit any of those - or create
> Hmmm, then why does C-mode multi line comments work?
Hmmm. You are right.
Index: VERSION
===
RCS file: /home/lilypond/lilypond/VERSION,v
retrieving revision 1.385
diff -u -p -r1.385 VERSION
--- VERSION 16 Apr 2002 11:58:57 -
Heikki Johannes Junes wrote:
>>When the mode is invoked (when a file is read or with M-x LilyPond-mode)
>>then all multi-line schemes and multi-line comments are correctly
>>parsed. But if you edit any of those - or create a new one - then the
>>colouring gets wrong.
> Yes. This is problem of
On Tue, 16 Apr 2002, Han-Wen Nienhuys wrote:
> ...
> (But it is possible. Take a whole note for the o, a half note for the
> d, the dynamic p, etc.)
Yes, I had the same thought. But the difficulty lies in the "etc."...
And the symbols somehow should stylistically fit to each other.
Greeting
[EMAIL PROTECTED] writes:
> > > I could try to redo the cello-girl in Metafont, but where'd the
> > > word "lilypond" go?
> >
> > The girl is nice, but I don't think that she'd do so good in a running
> > text. We just need some typography for the word "LilyPond".
>
> Maybe this should be derived
On Tue, 16 Apr 2002, Rune Zedeler wrote:
> Han-Wen Nienhuys wrote:
>
> > I could try to redo the cello-girl in Metafont, but where'd the
> > word "lilypond" go?
>
> The girl is nice, but I don't think that she'd do so good in a running
> text. We just need some typography for the word "LilyPond
Han-Wen Nienhuys wrote:
> I could try to redo the cello-girl in Metafont, but where'd the
> word "lilypond" go?
The girl is nice, but I don't think that she'd do so good in a running
text. We just need some typography for the word "LilyPond".
- It should work in a 10pt text, you know, and I t
On Tue, 16 Apr 2002, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Shouldn't we come up with some sort of typography for mentioning
> > LilyPond in i.e. LaTeX-documents. I mean "This assignment was written in
> > \LaTeX\ with musical examples in LilyPond." just looks a bit - eh - thin
[EMAIL PROTECTED] writes:
> Shouldn't we come up with some sort of typography for mentioning
> LilyPond in i.e. LaTeX-documents. I mean "This assignment was written in
> \LaTeX\ with musical examples in LilyPond." just looks a bit - eh - thin...
I could try to redo the cello-girl in Metafont, b
On Tue, 16 Apr 2002, Rune Zedeler wrote:
> Shouldn't we come up with some sort of typography for mentioning
> LilyPond in i.e. LaTeX-documents. I mean "This assignment was written in
> \LaTeX\ with musical examples in LilyPond." just looks a bit - eh - thin...
>
Just philosophizing:
If you re
Shouldn't we come up with some sort of typography for mentioning
LilyPond in i.e. LaTeX-documents. I mean "This assignment was written in
\LaTeX\ with musical examples in LilyPond." just looks a bit - eh - thin...
-Rune
___
Lilypond-devel mailing l
On Tue, 16 Apr 2002, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Hi!
> >
> > Attached is a patch that introduces ligature brackets (anyone knows a
> > better term for these beasts?). These brackets are used in modern
> > notation when transcribing mensural music; they simply mark a
[EMAIL PROTECTED] writes:
>
> The patch helps to proof-read the source by using colors (for example,
> erronous "a,." now easier to see by an eye). Further comments within.
>
> This patch is against latest CVS. I consider my earlier patch (-hjj2),
> which was sent to HWN, not merged.
I had som
[EMAIL PROTECTED] writes:
> Han-Wen Nienhuys wrote:
>
> > It's because of the internals. Things would get a lot easier, if the
> > paper and midi block were separated, so we could apply different music
> > functions for these situations, i.e.
> >
> > \midi {
> > \notes { .. }
>
[EMAIL PROTECTED] writes:
> Hi!
>
> Attached is a patch that introduces ligature brackets (anyone knows a
> better term for these beasts?). These brackets are used in modern
> notation when transcribing mensural music; they simply mark a series
> of notes that, in the original notation, formed a
This is a suggestion for a new, and IMHO very useful feature of
LilyPond.
Creating repeated sections in lily is currently not flexible enough.
I.e. If one want's
||: c d e f | % | % :|| % | % |.
Then it is currently not possible.
Further more tying big (i.e. 5 note) chords together is he
There was a copy paste-error. Below is the correct patch. Now menus work
the right way.
Index: lilypond-mode.el
===
RCS file: /home/lilypond/lilypond/lilypond-mode.el,v
retrieving revision 1.33
diff -p -u -r1.33 lilypond-mode.el
--
>Well, I hope that the emacs mode will end up being able to fully cope
>with multi line comments and multiline scheme.
>When the mode is invoked (when a file is read or with M-x LilyPond-mode)
>then all multi-line schemes and multi-line comments are correctly
>parsed. But if you edit any of th
23 matches
Mail list logo
