181–190 of 244 posts
Why is this a problem? Is the author blind? If this happens with git then surely it happens with every command. What about "rm"? What if I type "rm -Rf", leave, then come back and type something else? Maybe a better solution is to change behaviour, or if there really is some reason for this behaviour, have something delete the currently entered command after it's been idle for some seconds.
Earlier quoted context omitted.
Knowing software developers, probably entirely serious.
The seasoned sysadmins are a little more careful before smacking the enter key...
Earlier quoted context omitted.
Relatable. For years, I aliased mroe to more. Now I alias mroe and more to less. My wife drafts a lot of legal documents, and has a problem with "doe snot". Which unfortunately the spelling checker is perfectly happy with.
There's defintitely room for an advanced spell checker that can say "This is valid, but probably wrong".
>I quite often type git then go away and come back, then type a full git status after it. Does anyone else actually do this besides OP. I've never heard of this problem until now.
gs = git status
ga = git add
gc = git commit
gp = git push
gl = git pull
gt = git tag
Earlier quoted context omitted.
I had a senior dev interview with a major company in SV last year where the lead and hiring manager claimed that the description for this behavior was "side-effect free". I didn't want to ruin my chances by correcting him that side-effects and idempotence refer to different qualities. I passed the interview, but I've never forgotten that. The guy also seemed to have washed into the interview off his surf board. Oh we…
In the context of software it seems like the word has pretty broadly adopted the meaning of "side-effect free". It's even made it to Wikipedia: https://en.wikipedia.org/wiki/Idempotence#Computer_science_m... One notable example: Stripe's "idempotency keys": https://stripe.com/blog/idempotency
>I quite often type git then go away and come back, then type a full git status after it. Does anyone else actually do this besides OP. I've never heard of this problem until now.
No. I have aliases for most things git: gs = git status ga = git add gc = git commit gp = git push gl = git pull gt = git tag
- gs is ghostscript
- gc is a component of graphviz
...and all of a sudden your text editor can't generate PDFs anymore when started from the shell.
Instead, I use four-letter aliases which work fine:
- gits = git status
- gitd = git diff
- gitc = git commit
..etc
Earlier quoted context omitted.
No. I have aliases for most things git: gs = git status ga = git add gc = git commit gp = git push gl = git pull gt = git tag
I never started with those two-letter aliases because they're bound to become problematic: - gs is ghostscript - gc is a component of graphviz ...and all of a sudden your text editor can't generate PDFs anymore when started from the shell. Instead, I use four-letter aliases which work fine: - gits = git status - gitd = git diff - gitc = git commit ..etc
alias gti=git