>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.
Does anyone else actually do this besides OP. I've never heard of this problem until now.
Finally I've written a small shell function that corrects "gi tpull" to "git pull", because that happens at least once a day.
Keyword: Backups.
This is similar to how busybox binary implements a bunch of the tools from coreutils etc.
My wife drafts a lot of legal documents, and has a problem with "doe snot". Which unfortunately the spelling checker is perfectly happy with.
(That said, if it were me, I’m not sure if I would give up typing doe snot every once in a while.)
EDIT: as mentioned below, it is called 'sl'
I think any command where you might start to type something out, but then need to refer to another window or session to figure out what else you want to type, is vulnerable to this kind of mistake.
(me earlier this month: https://twitter.com/sailoremo/status/908390247548911617)
alias g='git status -sb'
alias ga='git add'
alias gac='git commit --amend'
alias gb='git branch'
alias gbb='git checkout -b'
alias gbm='git branch --merged'
alias gbn='git branch --no-merged'
alias gc='git commit -m'
alias gcp='git cherry-pick'
alias gco='git checkout'
alias gd='git diff'
alias gdc='git diff --cached'
alias gg='git status'
alias gl='git log --graph --pretty=format:"%Cred%h%Creset -%C(auto)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset" --abbrev-commit'
alias gla='git log --all --graph --pretty=format:"%Cred%h%Creset -%C(auto)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset" --abbrev-commit'
alias ggpublish='git push && git push --tags && npm publish'
alias gp='git pull --rebase && git push'
alias gpp='git push && git push --tags'
alias gpl='git pull --rebase --prune'
alias gpt='git pull --rebase && git push --tags'
alias grb='git rebase'
alias grc='git rebase --continue'
alias gsp='git stash ; gp ; git stash pop'
alias unfuckgitremote='git branch --set-upstream-to=origin/`git rev-parse --abbrev-ref HEAD` `git rev-parse --abbrev-ref HEAD`'
https://github.com/robbyrussell/oh-my-zsh/blob/master/plugin...
Not hatin. Just wondering if I'm alone.
[0] https://github.com/mtoyoda/sl [1] http://r-wos.org/hacks/gti
Can you disable that feature somewhere ? The suggestion is good, but automatically doing the corrected query is not!
why type 8 characters 100 times a day, when you can type 1?
This process should happen behind the scenes. And then train a RNN for translating it to the following command, which returns a success code. Perhaps, we need to add a few checks that successful command has the same intent as the one which returned 127 error code to the shell.
That danger doesn't apply when things are copied from the browser chrome (address bar) or other locations. So why would pasting then still be dangerous?
I think blindly passing on advices "because $SECURITY" can actually detrimental to security because you may end up with half a dozen esoteric practices without actually knowing what they defend against. (I know the parent was half-joking, I think that's a more general problem)
<p>un paragraphe <span style="font-size: 0;">pas si </span>innocent</p>
I don't think that can be solved here though.
`alias :q="echo NOT IN VIM!!!"`
> alias :q=vim -c ':q'
My friends have gotten used to see me part the channel and rejoin shortly after, cursing my fingers.
Then regular old Cmd + v.
You're welcome.
[1] https://addons.mozilla.org/en-US/firefox/addon/lazarus-form-...
https://github.com/jez/dotfiles/blob/master/util/aliases.sh#...
I also have clera, lcear, and lcera -> clear, and :tabe -> vim.
Guilty as charged. I'll commonly start typing git, think about something else, switch to my editor, browser or an other terminal tab, then come back and type "git <command>" in full.
Unsurprisingly…
> rg 'git =' ~/.gitconfig
7: git = ! gitSo, I need to more firmly hit the keys in my actual driver (MS Ergo Keyboard) and now building my own mech...
P.D: ie: Maybe one of the different mech switches are more suited to the way YOU type:
http://www.wasdkeyboards.com/mechanical-keyboard-guide
---
P.D 2: This is a reply to all the ones that state that type wrong some commands.
Also, and maybe more common, is just bad typing. I was far worse before the use of the MS Ergo Keyboard (it DEMAND to use both hands.) So, if the performance change by keyboards (happend to me) maybe is a indication that are the tools at fault here..
Besides on my FreeBSD system /usr/bin/vi is around 400kB while on my Debian machine /usr/bin/vim.basic is 2.4MB. It's not much these days but on embedded platform it could still make a significant difference.
As a related issue, it bothers me a lot when I type some command that I want to read the output, and then I proceed to run `ls` right in the sequence and move the output out of the screen.
So... I really fail to see why this article is of any relevance at all, really. Or at least a more global solution would have been better, but I think it's not really an annoyance. For me, it's the same as wanting to fix a UI so that I wouldn't re-double-click a software that I've already started (well, some prevent it, and generally when they do, it means there are sessions, and it annoys me).
Everyone is different. I know an electrical engineer who grew up with dyslexia. So everyone finds their own solutions.
Personally I very rarely spell things wrong in cli.
Then I get distracted on HN ...
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