Citat Chris Jackson <[EMAIL PROTECTED]>:
> comments). A similar problem occurs with () meaning either Scheme or
> a
> phrasing-slur, depending on context, and the emacs syntax table
> doesn't understand context.
Well, I don't think it matters whether a paren is a slur or a scheme-paren, does
it?
The problem is that all parens except {} and <> needs to be matched individually
(i.e. ( { ) } is legal)
> I suppose a solution might be to write a lily-specific paren-blinking
> function.
Yes, that is probably what it takes :-(
-Rune
> (meanwhile this patch will take care of [ ] ...)
>
> --- lilypond-font-lock.el~ Fri Mar 15 13:17:12 2002
> +++ lilypond-font-lock.el Mon Mar 18 13:19:38 2002
> @@ -163,7 +163,7 @@
> (lambda (x) (modify-syntax-entry
> (car x) (cdr x) LilyPond-mode-syntax-table)))
> '(( ?\( . "." ) ( ?\) . "." )
> - ( ?\[ . "." ) ( ?\] . "." )
> + ( ?\[ . "(]" ) ( ?\] . ")[" )
> ( ?\{ . "(}2b" )
> ( ?\} . "){4b" )
> ( ?\< . "." )( ?\> . ".")
Tnx.
The colouring of "<" is still buggy, btw.
Try entering
<
>
The result is two black parens. If deleting and reinserting the '<' then the
parens get red.
-Rune
_______________________________________________
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
