Why tiddlywiki.info not tiddlywiki.json

#1

Is there any particular benefit to using .info as the file extension?

1 Like
#2

I belive its historical, similar to other node solutions and perhaps a little safer if someone exported a json file and named it tiddlywiki.json

#3

Is there any particular benefit to using .info as the file extension?

Back when I was starting TW5 in 2011/12, it was an attempt to convey the semantics of the file. Modern tooling doesn’t really like it (eg VSCode complains every time you click on a tiddlywiki.info file), and so I think now I would stick with the json extension.

3 Likes
#4

In VSCode you can set a relation between .info and json

The easiest way:

  • Go to File > Preferences > Settings.
  • Search “File associations”
  • Click on “Add Item”
  • Add your extension (*. ext) and the preferred language.

There are probably some other TW related settings already. eg. .tid … So you can change them too if you want.

There is a VSCode plugin, which works TiddlyWiki5 Syntax and is associated with .tid …

#5

Now I use tiddlywiki.json5 as the configuration file, just want to add some friendly comments, and finally generate a new info file

1 Like
#6

Here is the related issue [IDEA] Configuration files support multiple file extensions · Issue #7713 · Jermolene/TiddlyWiki5 · GitHub

#7

It suddenly occurred to me that it might be better to add a configuration here, such as allowing users to specify a configuration file at startup

#8

Good idea. At the moment the first command line argument to tiddlywiki is a path to the wikifolder. We could instead support paths that point directly to a valid JSON file. So the logic would be to first check for the argument existing and being a valid JSON file. If it is not, append /tiddlywiki.info and try again.

3 Likes