Lately, I’ve been unsure if I really want to use TiddlyWiki, because no 
matter how universal single HTML is, it’s still just a big file and it 
depends on the browser. Since plain text is the most timeless format 
possible (even a text file written in 1963 can still be viewed and edited 
today), I thought I would migrate to plain text files. Once I realized how 
I could convert the tiddlers extracted from HTML to the right format for 
me, I started looking for a text editor that included both preview and full 
text search. To my great surprise, the latter is supported by very few 
programs, so I can only solve it with my own Grep script. After sleepless 
nights and short circuits of thought, I came to realize that TiddlyWiki can 
handle separate files. Even if the Node.js TiddlyWiki itself ever ceases to 
exist, the notes will still be usable because they are just text files, and 
if I systematically name the tiddlers, the links between them will still be 
searchable with a simple, software-independent text search, so they remain 
usable.

The question is, how can TiddlyWiki be used as a simple text editor? I 
would like to emulate the operation of Boostnote / Joplin / Typora / ...

For example, if I install Ansel's Markdown 
<https://demo.santosa.family#tw5-markdown> plugin and then copy the 
Markdown files to the tiddlers directory, how can I edit them without 
adding extra metadata? If I edit ".md" files in Tiddly, then it writes them 
back to the drive in JSON format. If I change ".md" to ".tid" extension and 
write "type: x-markdown" at the beginning of the file, it will rewrite the 
file in its original form after editing, but add e.g. the "title" field 
with the current path to the file, which I don't want.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ed46b155-e3e6-44e4-b702-f113147f8d11n%40googlegroups.com.

Reply via email to