camelcase can confuse - should not whitespace be the border?

[ThurnerRupert]

we use wiki to store ssh publich keys like: ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAIEA6R2yNQF3bKUMZOp8gH/a13PNdoukGG/4sMvHCma3/bqoSogi13JjgGdMHGxM0mhO6jEd7//CBRbr3MdYmR+NaIr/6TwNtCvomxPhlHTllltF1uw3BT2xQwSPJN0TnNh6F9EaA8kBRe3jGs3Ky5Gcgg9Sym99zTuzbwvX+XWC7sE= my key ...

and to tell trac not to put a wiki link in this key is not really intuitive :)

[cboos]

Replying to ThurnerRupert:

...YmR+NaIr/6TwN my key ...

The problematic bit is in the above. We could add "+" to the list of characters that must not precede a WikiPageNames, but this has to be done carefully, only if it doesn't break some common usages (at least, usage that are more common than the problematic one ;) ).

[anonymous]

I would very much like to disable interpretation of CamelCase strings as wiki page names since users continually enter such strings as source code identifiers and whatnot without intending them to be wiki page names. I would like to be able to disable it for the whole trac.

[osimons]

Hmm. In a way I see the reasoning with ignoring '+', but that starts us off on a line of ignoring further characters that may be in certain cases be seen as not wanted. My users are mostly C# developers, and could well be without escaping after '.' when they refer to their classes. Same reasoning that you only escape the first word, but not words followed by a dot: !MyPackage.MyFile.MyClass will only escape the first part. One way would be to say that if it is escaped ('!'), the escape is effective until whitespace is encountered? Again, that may interfere with many other uses cases - not easy to know what people do or want here.

However, there are also the other regular syntax that is commonly used to handle this: Wrap it in {{{SomethingHere}}} blocks (or `SomethingHere` back-quotes).

In projects where this is more annoying than a positive feature, there is always the option of turning off the auto-discovery of wiki names: [wiki] ignore_missing_pages = true (answering the previous comment).

[osimons]

Replying to osimons:

One way would be to say that if it is escaped ('!'), the escape is effective until whitespace is encountered?

Doh. That is obviously the summary of the ticket...