Jed,

I have only raised the  ⚒.tid issue to simply put it on your radar and if 
you had any suggestions. I think this may have being the cause of me not 
being able to "import" other wikis into bob.

In my sentence 'Auto Populate and Remove links to missing wikis is not 
regenerating this list without __path' I was just telling you I used Bobs 
facility to regenerate the list of wikis from the folders.

Regards
Tony

On Tuesday, April 2, 2019 at 7:17:27 PM UTC+11, Jed Carty wrote:
>
> Tony,
>
> That is how the settings.json is supposed to look. That is what the third 
> line in the changelog in the original post is talking about. It is required 
> to allow wikis to be hosted on paths that contain other wikis, otherwise I 
> have no way to list in the settings that you can have a wiki called foo and 
> a wiki called foo/bar.
> And I am sorry, but I don't know how to interpret 'Auto Populate and 
> Remove links to missing wikis is not regenerating this list without __path'.
>
> Windows is the bane of my existence, at least in the context of developing 
> Bob. If windows doesn't support unicode filenames than I do not think that 
> I can do much about it. Although in this case it may be a limitation of the 
> zip implementation if the wiki works other than not being able to be put 
> into a zip file.
>
> There shouldn't be any problem renaming tid files regardless of what is in 
> their titles. But if you do this with Bob running it won't work and the 
> tiddler files will have their names changed back to match the tiddler 
> title. If you change the title than the filename will change so that is an 
> option, or you could change the filenames manually before ziping it, but 
> this seems like a time consuming solution.
>
> If you change a the name of a .tid file with running than Bob will change 
> it back to match the tiddler title, respecting the modifications from the 
> FileSystemPaths filters you may have. So if unicode titles are giving you a 
> problem on your system you have to change the titles to have it may any 
> effect. I can see about adding a no unicode filename option for systems 
> that don't support it. This may cause some confusion because then you would 
> have filenames that look like %23%45%24.tid or something like that, but it 
> may remove the filename problem.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f6a7fe3e-1d08-4234-86a8-6754502c0b12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to