Re: another pygment formatting glitch

2022-10-29 Thread Jean Abou Samra
Le 29/10/2022 à 15:02, Werner LEMBERG a écrit : Just curious: Wouldn't be Wilbert's 'parce' library (used for the code highlighter in Frescobaldi) a more sophisticated alternative? Originally, I wanted to have LilyPond support in Pygments because it is used in Sphinx and MkDocs as well as on

Re: another pygment formatting glitch

2022-10-29 Thread Werner LEMBERG
> The problem is that "violin" is also the name of a clef: [...] Ah, yes, thanks. Will fix the example. > [...] in general the Pygments lexer would have to be far smarter in > order to distinguish cases where a particular word is used as a > user-defined name vs. those where it should be highlig

Re: another pygment formatting glitch

2022-10-29 Thread Jean Abou Samra
Le 29/10/2022 à 11:06, Werner LEMBERG a écrit : Please have a look at the attached image, taken from the LM section 3.4.1. As can be seen, the second variable ('cello') is bold, while the first one ('violin') isn't. Can this be fixed? ~/repos/lilypond $ cat test.ly violin = #'foo cello = #'

another pygment formatting glitch

2022-10-29 Thread Werner LEMBERG
Please have a look at the attached image, taken from the LM section 3.4.1. As can be seen, the second variable ('cello') is bold, while the first one ('violin') isn't. Can this be fixed? Werner