71–80 of 132 posts
The autocomplete popups are really cool. Does anyone know if there's a generic way to provide this for all tools with CLI's with help text? What about being able to parse a Programmable Completion file. I don't know much about this stuff, but the thought popped into my mind.
Earlier quoted context omitted.
I agree: to me this is like a car giving you driving directions by saying "turn north" instead of "turn left"; there are people who legitimately find either way to be easier, and if you give them the wrong way they are just going to have to convert it... I find absolutely dates and times to be super intuitive, and I have most of my life laid out in my head with absolute dates, and find relative dates and times to be…
Isn't your analogy flipped the other way around? "North" is technically correct but an absolute reference, just like a date. While "Left" is relative just like "two hours ago" With the relative reference you don't need to know which direction you are heading, or what time it is right now.
This is never going to be popular with French-speaking developers, haha.
I really liked the look of this, until I got to `save`/`sync` in the readme... That's not how I want to work, and it's not how I want other people to work in a repository I'm using. I know 'I don't have to use them then I can just use the git subcommands', but that's not the point, it's a big signal ('90% of the time the above commands will have you covered.') about the motivation/angle/philosophy of the project that…
The save command also accepts the commit message on command line only instead of opening an editor. I do not understand how people can live with only a single line for the commit message. For a new feature, I need to provide some details what is added and how it can be used. For a bugfix, a single line is rarely enough to describe the problem, what you changed, and why this change solves the problem. Writing good com…
I often go through list of recent commits and rebase them before sending PRs. That way, I save a bit of time not having to switch contexts with code and commit messages.
Earlier quoted context omitted.
"GMT" That alone hints you're either working in the UK or you're confusing GMT with UTC, or both.
Or, nobody cares about fractions of a second when organising a meeting, so to all intents and purposes they are the same.
The autocomplete/help popups didn't happen for me, is there something I need to do? I'm using zsh on a Mac, perhaps it assumes bash. Aside from that, I'm going to persist with this for a little while and see how it goes, the git interface does bother me.
I don't see autocomplete popups either - Fish on iTerm2 here. First thing I did was type `bit` and hit tab and I got a Go traceback - `panic: COMP_POINT env should be integer`
Earlier quoted context omitted.
Yes! A git cli with a good syntax which is the same for every command would be useful. It would not have to do every nifty git feature, just uses a senseful subset: git push/bull branching/merging/rebasing and add some nifty common problems like delete file from history, remove last x commits already pushed etc. The most popular git questions on stackoverflow tells a story on which tasks are more complex on git becau…
https://github.com/tj/git-extras/blob/master/Commands.md does it pretty well. Everything you've listed is covered there I think.
Earlier quoted context omitted.
Or, nobody cares about fractions of a second when organising a meeting, so to all intents and purposes they are the same.
Point being, they are not the same. There is one hour difference between UK Time, GMT and UTC for half of the year, due to daylight saving time.
I really liked the look of this, until I got to `save`/`sync` in the readme... That's not how I want to work, and it's not how I want other people to work in a repository I'm using. I know 'I don't have to use them then I can just use the git subcommands', but that's not the point, it's a big signal ('90% of the time the above commands will have you covered.') about the motivation/angle/philosophy of the project that…
The save command also accepts the commit message on command line only instead of opening an editor. I do not understand how people can live with only a single line for the commit message. For a new feature, I need to provide some details what is added and how it can be used. For a bugfix, a single line is rarely enough to describe the problem, what you changed, and why this change solves the problem. Writing good com…
I personally like this format more because it lets you both be "dirty" in your branch writing commits for yourself, and not have to use amends/rebasing. I can see how it would be annoying for someone that does all the digging on the terminal through git log and blame, but we all use gitlab instead.