I want a terminal that highlights things it thinks are off. Like when I type cd cd or git git. But I don't want it to auto fix nor wait until the command is issued to complain. This is because I want to be the sole controller of what command is actually issued. Call me an old curmudgeon but I just don't trust the auto fix solutions. Edit: had no idea about Fish. Thank you, all.
Hey, don't forget about zsh with a highlighting plugin! :)
Git git git git git
161–170 of 244 posts
Re: Git git git git git
#162Earlier quoted context omitted.
What kind of evil system ships with both vi and vim?
OpenBSD comes standard with vi. Vim is a package.
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.
Re: Git git git git git
#163Earlier quoted context omitted.
Not this, but I do fairly often think assume I'm in vim when I'm not. `alias :q="echo NOT IN VIM!!!"`
My favorite one of these is typing ctrl-w (cut in emacs) in a browser tab as I am editing a bunch of text in a text box.
[1] https://addons.mozilla.org/en-US/firefox/addon/lazarus-form-...
Re: Git git git git git
#164> git config --global alias.git '!exec git' Is the exec really required? git config --global alias.git '!git' Will also work. Am I missing something? EDIT: From git doc, "If the alias expansion is prefixed with an exclamation point, it will be treated as a shell command" So exec is not required then.
Re: Git git git git git
#165Re: Git git git git git
#166>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.
Not this, but I do fairly often think assume I'm in vim when I'm not. `alias :q="echo NOT IN VIM!!!"`
https://github.com/jez/dotfiles/blob/master/util/aliases.sh#...
I also have clera, lcear, and lcera -> clear, and :tabe -> vim.
Re: Git git git git git
#167Works fine, but when I press quit (q), it says `error: exec git died of signal 13`
Re: Git git git git git
#168Earlier quoted context omitted.
Non-idempotent options are always unsafe; safe operations are a subset of idempotent operations. (I suspect you meant “safe” in a different sense, but I couldn't resist.)
> safe operations are a subset of idempotent operations Definitely not. 'Safe' means too many things in different contexts to make sweeping statements like that. Here's one i came across recently. You are interacting with a stock exchange. You have sent an order to buy 100 shares of Twitter stock at some price, and it is now resting on the order book, waiting for orders to sell at that price. You see that the charact…
Only if you can be sure the non-idempotent message arrived. It's not safe to re-send the delta message.
Re: Git git git git git
#169Earlier quoted context omitted.
It’s probably just a shell script or an alias
An alias would work but it wouldn't say rebnooting. That was my initial fix. But I was learning things at the time and I learned how to recompile parts of the distribution. I also learned how programs in Unix could invoke different effects based on name. Coming from DOS, it was a real surprise that reboot was a link to shutdown.
This is similar to how busybox binary implements a bunch of the tools from coreutils etc.
Re: Git git git git git
#170Earlier quoted context omitted.
I do. And I also write "vim vim thefile.txt" and stuff like that. Finally I've written a small shell function that corrects "gi tpull" to "git pull", because that happens at least once a day.
Personally, I don't want my typos corrected when I enter commands. I prefer the negative reinforcement to encourage fewer errors. I also don't mind an occasional error. Not hatin. Just wondering if I'm alone.
Can you disable that feature somewhere ? The suggestion is good, but automatically doing the corrected query is not!