orgajs VS bash-modules

Depending on how you log data and take notes you might find the orgparse Python library or the orga JS library useful.

That is perfect, all org-syntax features we need are done properly. I can manage to use the orgapp code in some simple tool.

org syntax isn't as confined to the emacs world as it used to be. Check out, e.g., https://github.com/orgapp/orgajs, which parses org files into an 'abstract syntax tree', which can then be transformed/picked for info/indexed, etc. etc. by any number of tools. Pandoc's support is also improving as far as I'm aware.

I am an avid emacs user! Lately, I found a tool named orgajs (https://github.com/orgapp/orgajs/). This seemed great for my needs but it is behind on maintenance.

Thanks @preek. I mentioned you guys in [3] above. BTW I'm actually using this parser: https://github.com/orgapp/orgajs for my product (https://braintool.org), so there are other choices. I guess the key thing is a single well defined grammar.

Is GDrive syncing working in Organice these days? I've wanted to demonstrate interop with BrainTool (which syncs to GDrive files) but last I checked there was some bug.

Overall Orga's great and I really don't mean to diminish the author's work in any way, but I have had a couple issues. A number of them have been fixed, which is great, but I got stuck on this one about line breaks when using auto-fill mode. I think it's fixed in a newer version of Orga, but upgrading broke my build and I've spent enough hours trying to fix it that I'm looking for options.

MDX is non-trivial. But if all you need is gatsby with org, a simpler plugin similar to gatsby-transformer-remark is doable. gatsby-transformer-orga would be a good inspiration here.

Bash is turing-complete, so it's possible to write automated test cases in bash. Example: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...

Template in article is awful. It's better to use this one, which is a real CLI tool: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...

IMHO, you are mixing TODO lists and task management/planning software. No, I don't know a good task manager or business process manager for command line. Instead, I created a simpler TODO list manager, called `td`[0], which supports flat TODO lists only, and use directories and command-line generators to manage todo's. `td` prints top item only, by default, leaving little room for procrastination. I'm keeping one `TODO.md` file per project instead of one large TODO file for all todo's.

[0]: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...

Documentation: http://vlisivka.github.io/bash-modules/ Project home page: https://github.com/vlisivka/bash-modules

I'm preparing to release bash-modules 4.0 [0]. Can you give me feedback, please? I'm a non-native English speaker, so I need someone to help fix spelling mistakes, at least.

https://github.com/vlisivka/bash-modules

It works in my shell. :-/ It looks like you forgot to insert `false` command.

You are pointing to the problem with -e not working in subshell/deep functions, because of POSIX. Right? It's described in bash documentation: http://www.gnu.org/software/bash/manual/html_node/The-Set-Bu...

> I think just defining a die() function and using it after any command that must succeed is more verbose, but less error prone:

Yep. It's the style I developed 12 years ago, when working at Bazaarvoice, when I was lead of devops team. I created the whole library for bash, to use this pattern consistently. See https://github.com/vlisivka/bash-modules#error-handling