Hi, I have quite a large wiki, I turned off automatic CamelCase linking and it’s so much better.
But although I have moved quite a lot of links by running regexes on the tid files, etc., I wonder if there’s a smart technique to move all in one go? (Or few “gos” 
Thanks,
Gabriel
I’m not sure what CamelCase linking has to do with moving things…? I never use CamelCase, and I have no trouble moving / migrating.
So maybe I don’t know what you mean by “moving links”… If you’re migrating a wiki, you just be able to specify which tiddlers you want (in the advanced search filter area), and then export the tiddlers you need.
Can you say more about what the problem is — the problem that you’re having trouble solving?
Ah, maybe you want to convert links…
Some combo of relink plugin (where if you rename a tiddler, links to it are also renamed), the freelinks option, this thread about “baking in” free links, and Commander plugin (for refactoring things) may help you think through how to refactor a CamelCase wiki so that things behave well with your new natural-looking tiddler titles…
Thanks. Yes, I have a wiki with more than 10k tiddlers, which used to be CamelCase–automatically linked. I switched over to be explicitly linked with brackets. I caught the bulk of links by operating on the tid files, but still I find links I didn’t catch on that big sweep. It’s too many to do one by one. I was hoping someone might have a “just flip it back, run this thing, flip it again” technique that would make them all explicit.
I am experimenting with usingTW in the Comet browser [1] and have discovered the Comet Assistant can change the content of and create new Tiddlers. I’ve not tried it but I think that if you had a TW open in the browser you could get Assistant to create the links
Alex
Thanks all for your ideas.
In the end I used this GitHub - yegappan/greplace: Vim plugin to search and replace a pattern across multiple files interactively across the raw .tid files.
It allows me to search for the camel case patterns, in a Vim buffer replace their usage, tweak by hand, and then commit wholesale.
Cheers,
G.
@gabrielmontagne I just wanted to add whether or not a link exists because it is camel case or has a title in the text, you can see these all with the freelinks plugin. So just moving your tiddlers to the new wiki and using the links operator and or camel case switched on you can search for tiddlers that do not meet your requirements. Open the tiddler and rename it with relinks active.
- It sounds like you are happy with what you have but I think there may have bee simpler ways to tackle this all along. Of course renaming a tiddler away from camel case will thus be reflected everywhere it is mentioned (with relink).
- However like most migration processes it can be influenced greatly by the nature of the data you wish to migrate.
I suppose you have now decided how you like to do it going forward and can write your content to suit your exacting requirements.
- I find camel case useful for indicating more content is needed and maybe a new tiddler. Although the editor toolbar buttons also help you select a piece of text or a work to make a tiddler reference as does the control-L to insert an existing title (or html link) via a search.
The freelinks plugin and a huge number of tiddlers is not recommended, since it will create a performance problem.
As I understand it it acts only on the visible tiddlers so its possible to not lean too hard on it, and I am only proposing to use it to find and implement the links. Then it can be turned off.
It can actualy help identify when you have used words for which an link exists already if the idea is to maximise links in the text.
I think somone may have made a tool to comit found links to the tiddler text from the view template, perhaps it was just a good idea 
once that done no freelinks needed.
- Interesting if it was combined with you alias tool for editors.