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 response to patterns. Thanks for picking up on that!
It's like .de rather than just ignoring its content, e.g.
$ nroff | grep .
.nr x 1 10
\n+x
.ig gy
\n+x
.gy
\n+x
^D
11 31
$
> > And why \\fB inside a .de is treated as \fB.
>
> That was actually a conscious exception on my part. Many roff macros need
> heavy escaping, so I made all `\` characters match as one character.
Ah, OK. I think one common error is forgetting to have sufficient \ in
a macro definition. (What do others think?) Having \fB and \\fB appear
different inside a .de scope would help show that. But I also see that
having the fB be recognised is useful too.
> > Why is .PS orange versus .PE's purple?
>
> Hrm, could you show me where you're seeing that, please? =)
After a .ft with no arguments, it seems.
https://github-lightshow.herokuapp.com/?utf8=%E2%9C%93&scope=from-url&grammar_url=https%3A%2F%2Fgithub.com%2FAlhadis%2Flanguage-roff%2Fblob%2Fstatic%2Froff.json&grammar_text=&code_source=from-text&code_url=https%3A%2F%2Fgithub.com%2Frust-lang%2Frust%2Fblob%2Fmaster%2Fman%2Frustdoc.1&code=.de+MO+ed%0D%0A%5C%5CfBerror%5CfP+%5C%5CfIok%5C%5CfP%0D%0A.ed%0D%0A.ig+gy%0D%0A.nothing+special%2C+but+%5Cn%2Br%0D%0A.gy%0D%0A.ft+B%0D%0A.ft%0D%0A.PS%0D%0Abox+box+box%0D%0A.PE
Cheers, Ralph.
