On 6 September 2011 11:52, Jason Morrison <[email protected]> wrote: > Thanks, Lex - not sure why I didn't find that before. I am trying to lean > on the docs before turning to the group. > What's the best approach for using this updated filter, going forward? I > could write a filter plugin and share it with my team, and it would override > the built-in filter with the same name, as > per http://www.methods.co.nz/asciidoc/userguide.html#X58 - seems like a > great short-to-medium-term solution. > Would something like this (starting and ending line numbers for source > filtering) be a likely candidate for inclusion into asciidoc proper, or am I > better off maintaining a filter plugin? Are there contribution guidelines > (e.g. "include a testasciidoc exercise")? Should I take the discussion > to http://code.google.com/p/asciidoc/issues/list ? > Thanks very much! >
Hi, Well it seems to me that specifying line numbers is a reasonable extension to the built-in filter, at least for gnu source highlight. Wouldn't work for pygments unless maybe you used sed to select the lines and piped it to pygments. Also how available is sed on Windows? And finally how do you ensure that your line numbers remain in sync with any changes of the source? Perhaps it would be better to mark areas with names using structured comments and include them by name. That probably means a source highlight block macro instead of a source style since there will be no included content to mark with the style. Stuart will make the final decision on additions to the official version. Cheers Lex -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
