This is basic documented functionality, so I’m sure I’m doing something wrong.
To review what I understand: There are two forms for tagging FoldingText documents.
Tags are quick inline tokens, beginning with
@, with an optional string argument. The expectation is that if present, the string will be brief.
Properties are single tokens, at the beginning of a line, followed by
:(space-colon-space). A free-form string may optionally follow the
There is no semantic difference. The two words are just names for the two ways to create the same thing.
I have a FoldingText document open (it’s empty, I run into it in a populated document, too). I type
@fixme(this is a problem)
It turns gray and responds to clicks by focusing on
@fixme tags. It shows up in search and navigation as I expect.
Next, I try
fixme : this is a problem
Neither the tag nor the content show up in any navigation affordance. It does not change color, nor does it behave as a link. Instead, the tag word is italicized.
Leading whitespace doesn’t matter. (I had hopes for putting
@fixme(etc) into a comment in a Ruby codeblock, but no luck, and it doesn’t matter.)
I’m doing something wrong. What is it?
- FoldingText — 2.0.2 (738); it and the following plugins were installed the evening of 7-Aug-2014 US CDT promptly after download
- Mac OS X Mavericks — 10.9.4 (13E28)
@fontFamily: Input Sans;
and nothing else outside of comments.