In a way, the default git CLI is just the one alternative git interface that "won".
My favourite one is still hg-git, despite its warts.
I mean, git had tools that could do that too, but built-in! Then I discovered GitHub.
- A simple query language that can be used to filter commits. For example: authordate >= "2017-09-01" AND authordate < "2017-10-01" AND authorname = "John Smith" AND parentcount < 2.
- View layout is more flexible. Each tab in GRV can have any view added to it as a vplit or hsplit. Users can create their own tabs and populate them with any combination of views they want. The long term idea is that when GRV supports more views (tree view, file view, etc) it will be possible to create quite a custom experience.
Oh, nice, finally someone implemented something like Mercurial revsets for git:
I've been hoping that even if nobody ever uses Mercurial, I was hoping at least they would manage to implement some of its better ideas for git.
Any chance that I can do basic stage/unstage/commit etc with grv?
I can't tell if this is a joke comment or not but both tools are run in the terminal so the font would be whatever the terminal uses. What you're doing is essentially comparing the typeface of `sed` verses `awk`
Yeah it's probably the best way to interactively stage only changes you want to commit (`add --patch`)
There is a use case which seems to be missed by all git-related tools: Reading Code on Github.
I would really like to have a tool that would allow me to easily browse my starred repos on GitHub, on my iPad, in offline mode (one-click update of all repos please). And by "browse" I mean read code, so the main focus is not on tags/branches, but viewing files and changesets.
There are plenty of tools that try to let you edit code, access repos, browse tags/branches, but they all assume that you are willing to spend time manually cloning/syncing/resyncing/downloading/uploading repos. This quickly gets tedious (Textastic on iPad is a good example).
Reading code is important, and it seems to have been forgotten.
I know right!
I also like to do all my reading on a Tab (Android) - be it books or code. My current approach to reading code is to first convert all the files to PDF! (I wrote a script uses LaTeX etc. to do this) and then sync all the files to my Tab.
It's okay for code that isn't changing frequently and PDFs also have annotations etc, which I use.
> spend time manually cloning/syncing/resyncing/downloading/uploading repos. This quickly gets tedious
These should all take little-or-no-time and be far from tedious in any half-decent Git client. Have you tried Working Copy? (I haven't but it seems competent from reviews)
Yes, I have Working Copy. I also have several other applications that are in various ways related to git and github, but do not solve the problem.
The initial blog-post which announced the editor is worth a read, as is the discussion here:
My own version adds Lua support, multiple buffers, and similar features. It is by no means the best of the editors but I had fun playing with it - to the extent I was almost tempted to write an editor. (But then I realized I already have vim for writing email, and emacs for everything else. The world really doesn't need another editor!)
While you're at it, consider rewriting everything you have in Rust. (obligatory statement as the member of ritf)
PS: the termion suggestion is not a joke
For actually shipping the code around, you could use pkg  to generate a single binary. That lets you avoid having to install node or any supporting libraries.