Re: [Groff] GroffHub

Alright, some updates: 1. .ig requests now blank out their contents

Re: [Groff] GroffHub

> > *CSTR 54 has a list of the original ones. :-)* Haha, don't worry, I was actually going through it page-by-page when I wrote this. =) I simply meant that I forgot about how that particular macro should affect highlighting. *After a .ft with no arguments, it seems.* Okay, you've just pointe

Re: [Groff] GroffHub

Hi John, > > That's why .ig doesn't cause subsequent lines to be ignored. > > Uh, actually, I completely forgot about that macro... CSTR 54 has a list of the original ones. :-) > That actually *can* > be handled in a line-based fashion, because TextMate operates by opening > "scopes" in respons

Re: [Groff] GroffHub

> > *That's why .ig doesn't cause subsequent lines to be ignored.* Uh, actually, I completely forgot about that macro... That actually *can* be handled in a line-based fashion, because TextMate operates by opening "scopes" in response to patterns. Thanks for picking up on that! *And why \\fB ins

Re: [Groff] GroffHub

Hi John, Nice work. > Yes, a limitation in highlighting is that each regular expression is > scoped to one line at once, so there's no possibility of knowing > what's on the next line, or what was on the previous line. This is > done by the TextMate-grammar engine for performance reasons, but it

Re: [Groff] GroffHub

> (In other words, I'm insane to have gone this far) :-) Werner

Re: [Groff] GroffHub

Thank you! The hardest part was definitely the repeating-font macros

Re: [Groff] GroffHub

> Over the last four months, I've been working on a > TextMate-compatible grammar > to improve the > highlighting of Roff source on GitHub. I submitted my pull request > earlier today, and > the effect on co