Diego,
I use command line tools to search these flat files and that lets me escape > many of TW idiosyncrasies. > That's where we differ, although inhabiting the command line (WIndows), much of my life, I always seek out a way to do it in the interactive wiki. I use tiddlywiki to capture knowledge and methods rather than needing to use various memorised command lines. I still have not found something I can't do in the interactive wiki. I leverage tiddlywiki fully, code mirror is a good editor but I can also use an external editor on text areas using a browser extension if I want. But increasingly the interactive tiddlywiki is all I need. Personal opinion By operating within the wiki, any process or workflow is open to enhancement, innovation and new User Interface options. Command lines are not so much fun. The die hard linux fans often say the command-line is their preferred interface and even say its easier, but they are ignoring the years of learning that brought them to that point. They forget, it is harder to help new users, if the methods they refine are at the command prompt/shell, without forcing the new user on the same long journey. This bias is evident in many of the Node Enthusiasts use of tiddlywiki. As long as one command line is necessary the take up of node implementations is limited. Jed's bob.exe goes a long way to doing this, but barriers remain. I think embracing the TW idiosyncrasies is better in the long run. Each to their own. Regards Tony -- 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/92539769-dd47-42be-afe5-52ca2791218co%40googlegroups.com.
