sowhat VS todo

Hello HN,

The demo here shows the companion editor [0] for the sowhat language [1].

The purpose of the editor is two things:

- Makes building and organizing a collection of writing easier. It does this by extracting different elements such as tags and folders from a collection of writing then presenting those elements via in-context autocomplete.

- Makes the collection of writing more useful by including notation elements such as events, beans [2] and formulas to support computing within the writing itself.

A while back I released sowhat, the language supporting Tap [3]. Sowhat and the companion editor are, together, a cornerstone of Tap. Tap is a system for collecting writing and other digital matter.

The editor here can be used in conjunction with sowhat to build your own tools. Or, it can provide a foundation to augment and enhance Tap.

My goal is to open source as much of Tap as possible because:

- It's fun to build with other people

- It should be as easy as possible for someone to customize their Tap experience. There's no way to accommodate all the UXs one might want within Tap. These tools are intended to enable a developer to create their own experiences.

- For those that use Tap but the then leave, a person's exported notes can maintain their original organization and meaning.

- Opens a path for others to provide feedback and enhancements to the open source tools and Tap itself.

0. https://github.com/tatatap-com/sowhat-editor, demo: https://tatatap-com.github.io/sowhat-editor/

1. https://github.com/tatatap-com/sowhat

2. https://github.com/tatatap-com/sowhat#beans

3. https://www.tatatap.com

I hear you. What guarantees about how it works do you have in mind?

You may be interested in just the parsing component of /tap, which is open source https://github.com/tatatap-com/sowhat

Yay! Good to read validation after trying so many: wikis, org, TheBrain, Freemind, etc. It's like a return to the old .LOG in notepad trick.

After a score, I'm came to the same conclusion as the article; plain text just works. I log in vim using ISO 8601 date stamped records in the log format of (priority - datetime stamp - keywords/tag - content) inspired by Randy Pausch https://youtu.be/oTugjssqOT0 others noticed too: https://github.com/nrr-deprecated/todo

Sorting by date, priority or keyword keeps me on track and helps for quarterly summaries.

A simple bash loop runs annually to give me a fresh 365 dashboard of days but inserts are a datetime stamp command - keywords autocompleted - then actual typing the meat of the task/content

Because all text is in a single file, vim autocomplete saves typing as I use CamelCase for keywords; vim dict helps too.

Caveat: For enjoyment, I still use fountain pens and paper for a running top 3 priority and scribbling offline. Backup interop is via TiddlyWiki for reference archive and sync with a plain text Zettelkasten (heavy on vim gf, Rg, FZF and jq for TiddlyWiki json export)

Plain text is built to last.