Comment 26 for bug 380844

>> I think more common usage will be a link with custom text
>
> I try to omit custom texts for links, because searching for " pad" skips
> links like [[http://launchpad.net/zim|Zim]]. Perhaps this is a bug of
> the Search feature?

I think it's an usual behavior. Or do you know any application that
seeks through the target addresses of the links?

>> Zim syntax is context-sensitive, therefore it's pretty
>> expected that context-insensitive tools (grep) may
>> produce wrong results.
>
> 8-)  grep is not "case-insensitive", "grep -i" is.

I wrote context-insensitive, not case-insensitive.

> My point here is that a syntax is clever if it does not force to look back and forth several lines to know if "#chapter" is an anchor or a sourcecode comment (if it's outside or inside a verbatim block).

I don't agree. When syntax is context sensitive it doesn't mean it is
stupid or bad designed.

> @Jaap: Zims syntax for tags can also be a bit simplistic: @Jaap is not a tag here and @1MHz (common on hardware pages) is not either. Ok, "<SPACE>@" is seldom enough, but "<SPACE>#" is used for various purposes: source comments, colorcodes #F1E2D3, error messages like "inodes count wrong for group #3261", phone service codes #21*, ...

You're right. We should use different syntax for inline anchors if we
decide to implement them.