Csound Csound-dev Csound-tekno Search About

Re: [Csnd-dev] manual totally broken

Date2017-01-19 18:50
FromNate Whetsell
SubjectRe: [Csnd-dev] manual totally broken
That’s an issue that will now be resolved when

https://bitbucket.org/birkenfeld/pygments-main/pull-requests/684/update-for-csound-6080

is merged (and Pygments updated). I think the thing to do in the meantime is just not make format specifiers bold.

As for how this came about, to make the tokenization of format specifiers match as closely as possible to what Csound does, I’m looking at the parsing of format specifiers in

https://github.com/csound/csound/blob/develop/Opcodes/fout.c

and

https://github.com/csound/csound/blob/develop/OOps/ugrw1.c

and a search for 'f' comes up empty in both files. I can’t tell w

Date2017-01-19 23:20
FromJohn ff
SubjectRe: [Csnd-dev] manual totally broken
Format specifies are in fprintf... opcodes.

Sent from TypeApp
On 19 Jan 2017, at 18:51, Nate Whetsell <nathan.whetsell@GMAIL.COM> wrote:
That’s an issue that will now be resolved when

https://bitbucket.org/birkenfeld/pygments-main/pull-requests/684/update-for-csound-6080

is merged (and Pygments updated). I think the thing to do in the meantime is just not make format specifiers bold.

As for how this came about, to make the tokenization of format specifiers match as closely as possible to what Csound does, I’m looking at the parsing of format specifiers in

https://github.com/csound/csound/blob/develop/Opcodes/fout.c

and

https://github.com/csound/csound/blob/develop/OOps/ugrw1.c

and a search for 'f' comes up empty in both files. I can’t tell where the f specifier is coming from.