I'm guilty of the Lua feature, and even though it's only covering the existing muttrc API, it can already do quite a lot. The Lua feature is (not yet) turned on by default at compile time (and thus in systems distributions).
I'd be very happy to have more feedback and help to extend further that API and have some great scripts happening!
I think the point where Lua gets interesting is when it can be invoked when a new message is received, or you can iterate over message heads & the message-list(s) and process them automatically.
For example you might have a folder of "backup results", you'd want to mark all that have a subject of "Backup OK" as read, and flag the ones that have a subject of "Backup FAILED" as "important". Those are the kind of tasks I automate with my lua-based mail-client.
You can get more interesting and say "Keep only the most recent 100 messages in folder XXX" which applies whenever you either launch the client, or open a given folder too.
Well as I said for another post I'm aware of that. As the google project is mostly used only for android and chromium, and as the canonical name of the tool really is /repo/ and not /git-repo/, there's no real name clashing.
The only issue might be my project being shadowed by google and go, but the more people will like and use the tool I baked with , the more it'll appear on their first page. So it's not really up to me, but up to you all liking it!
And finally, if someone comes with a nicer better name than what I chose (I actually did not spend more than 2.42 minutes on the name when I had to mkdir the project's directory), I might be happy to rename :)
Otherwise, I hope you'll like the tool and send me patches and <3
note that I did not say that git has a good UX, I said it's /rather well designed/… Maybe should I have emphazised on the /rather/, or used something stronger like /relatively/ .
But anyway, designing the command line API of my own tool took me enough headaches — and I'm still not 100% satisfied — to understand how hard it is to have a consistent and great UX for something that offer as many features as git does. Though, I'm trying my best to avoid the decade old troll about git's UX (like vs mercurial)…
In the end, what I try to make clear it's that I'm not trying to replace what git does, but cluster a bunch of repository actions tied with some service's API operations.
And I try my best to offer a pleasant UX doing so. But please, help me making it better!
I agree with you on everything, except the "easy to remember" part. Git's UI is very convoluted and inconsistent. Designing a good UI is really hard, but I see too many people fall into the "I learnt it, so it must be easy!" trap.
Congratulations for making git-repo, by the way! It looks extremely useful.
Bitbucket support is there. But it's not feature complete, and not up to my standards…
The issue I have is that I got to implement OAuth2 for bitbucket, because the privatekey scheme offered by bitbucket does not work for a CLI tool use case. So currently, the credentials (login/password) of bitbucket are stored in CLEAR in the configuration file, which really, really sucks…
And some new features (like the snippets) are not implemented in third part python libraries, because most of the libs are old and unmaintained.
Anyway, following some discussions I had with atlassian bitbucket developers, bitbucket (like gitlab) is planning to switch to swagger, which will help automagical generation of client-side feature complete libraries. So I'm planning to level bitbucket feature set as soon as they land the new API.
So I hope it won't be long before all the features will land for the three services!
And I hope also level the game for alternatives to github. Git is distributed by nature, and we should only be happy to see cross services forks happening!
