Option to turn off auto CamelCase links

[raindog308]

I know that some people like it...but a lot of us hate it. If I want to create a link, I can use brackets. I would prefer that not every CamelCase word gets made into a link. To me a link implies intention to create, whereas auto CamelCase link generation can pepper docs (depending on what you're writing) with links that lead nowhere.

The Trunk docs themselves have several references to WikiWord that go nowhere

Perhaps there could be an option to ignore auto CamelCase link generation. If set to On, then only manually entered links (with [[ ]] brackets) would be made into links. That way people would have the choice and could set up their personal wikis however they liked. I would like that very much.

Otherwise, brilliant, good show, keep fighting the good fight, rock on, etc.!

[froggyntoady]

I would agree in general. I don't want the appearance of links to pages that don't exist. However, I do like being able to make a WikiWord that is a link without having to put brackets on it. Maybe I can't have it both ways. But maybe there's a way to make words in CamelCase only appear as links (eg, blue and underlined) only if an actual page existed to which they point? Maybe in such a situation, CamelCase words (or perhaps any word, even if not CamelCase) that have no page to which they point could have an option to 'create page' next to the "copy" command that pops up when you select a word in view mode. Same could go for selecting a word in edit mode, although you'd have to confirm saving changes to the edited page before creating the new page from the selected word.

[MountainPastor]

For now, at least, it's possible to escape a WikiWord with a slash to prevent it being a link.

/WikiWord ---> WikiWord

Does this work for you? For me, at least, escaping with a slash when I don't need a link is already more convenient than needing to use square brackets every single time I do want a link. The traditional behavior also has the advantage of making it very easy to make a link, then create the new note simply by tapping on the link, something that would need copy/paste and several taps if the behavior were changed to showing up as a link only if a note with that name already exists. If that's not good for others, though, as long as there's a pref to keep the current behavior, I'm happy.

[froggyntoady]

yes, i forgot about the escape mode, and that is a reasonable way to handle the situation. Thanks.....

[cjm]

You can add me to the list! I always hated CamelCase, both inside source code as well as in wikis. I just converted a bunch of old notes, one of which dealt with Windoze registry keys and half of those keys use CamelCase... as the saying goes: adding insult to injury

Having an option which completely disables any wiki word detection based on CamelCase would be extremely useful for me. Even if I would then have to go through all my notes and remove those extra slash characters. Speaking of which: when CamelCase detection is disabled, the '/' escape code should be disabled as well so we can finally insert path names etc. without the risk of slashes vanishing magically...

Thanks,
--Christian