Hi guys!
Just like @madmalik I’m new to Pijul but I already love it. Reading the docs I thought that some command names are inconsistent with the docs itself though so I’m happy to find this thread.
For example pijul status says:
use “pijul add …” to track them
Why not call the command track then? If the idea is to remove confusing metaphors and being clear with the command function then I think commands name should look just as they are described in the docs. Also if it is called track then the inverse operation would be called untrack instead of the confusing remove.
Another example: pijul revert is described in the docs as “Reset the working directory to the state of the pristine”. Why not call it reset then?
That lets revert free to being used to “revert a patch” and maybe pijul patch should be “the only command for creating patches in Pijul” which currently is record. (The current behavior of pijul patch could be pijul dump 
)
That being said I really like @pointfree’s idea of a compassable TUI. He gave more details in the linked issue and I just wanted to point out that in the case of pijul branch [new|delete|switch|list] I would replace new with create. A little bit longer, but it is imperative, right?
About @flobec idea on add being obsolete I have my doubts. I use a lot git clean -df here, but maybe it is a necessary command because Git itself is messy.