TFW You Learn There's a Vim Mode in Bash...

[@LukeSmithxyz]

Btw, zsh users can get an equivalent mode by putting `bindkey -v` in their zshrc, IIRC.

[@vison360]

There is fish_vi_key_bindings for Fish shell too.

[@leberkassemmel]

Daniel Lewan Nice! I like fish!

[@jfkd2812]

zsh doesn't use readline IIRC

[@jamesrustler2075]

What about the ultra hipsters of us that use Fish?

[@spikespiangel]

by default bash is in emacs mode which is "set -o emacs" try some emacs command to navigate your command line

[@BillSteinhauser]

Nice description of "set -o vi" cmd line editing Luke... Korn shell was the first Unix shell to have "vi" style editing on the command line, from the latter 1980s. The bourne shell did Not have command line editing at all... you just had to backspace and retype if you needed to change/correct anything before pressing enter. I have been using unix+ksh+shell since before bash shell or Linux existed. The command line editing features from Ksh were re-written & added to bash shell using library code called "readline" to make bash shell nicer to use. The reason you find command line editing when using "sh" on Linux, is that /bin/sh on Linux is actually running /bin/bash binary executable (via fs link) with a Bourne compatibility mode, but "readline" is still active. Some vim key editing combinations are not available, like "ciw" or "ca)" because command line editing supports the original "vi" editing features from about 1977, and not "vim" features from around 1998. When you type the "bind -P" command, you are getting a response back from the readline library code used by bash. (just to clarify some shell history, and details on command line edit functionality)

[@harshallele8309]

Thanks for showing all the vim commands that I didn't know about. I basically use vim like I use nano. I don't know most of the features, I just use it to convince myself that I'm cool

[@tibfulv]

Nano has features? :D

[@harshallele8309]

Well, so speaking of vim, I updated vim on my raspberry pi just now, and now it segfaults lol

[@tibfulv]

+Harshal Lele Copy the current version to your home directory, and install its sources. Then install the previous version so you have a usable vim. Now you can see why it segfaults with _gdb_ or one of the IDEs. Especially if you got the core file. Cool project if you know C/C++ or want to learn. I fixed vixie-cron that way twenty years ago.

[@harshallele8309]

Hmm, i actually do know basic C++, but yeah, can't really be bothered. But thanks for reminding me about the downgrade, had the previous version in the pacman cache

[@jonathanwarner1844]

Nano is cool?

[@tttt-tj4rg]

you can enable the mode globally, meaning not just for the bash shell but also for the other programs using the readline library such as mysql command-lineutility, in /etc/inputrc configuration file

[@danilodistefanis5990]

Which mode? Set -o vi ? Also zsh will take it ?

[@djamison9r]

I have been using vi / vim for a month or so now and just the other day, I was wishing I could use vi commands on the command line... and then I found this video... YES!!! Thanks.

[@mattlawyer3245]

This was amazing! I've heard of this before but never bothered looking into how to do it. Thanks a ton!

[@germangb8752]

I pressed V and I'm able to edit the current command inside of Vim. woah

[@loarto]

Goddamn was going to say this.... something I use occationally :)

[@davidh.4944]

You can give yourself a visual representation of which mode you are in by adding the following to your inputrc. The given character string will appear in front of your $PS1 prompt. personally use the circle-i and circle-c unicode characters myself, but you can get creative. set vi-ins-mode-string "Ⓘ " set vi-cmd-mode-string "Ⓒ " If you want to enable it only in bash, use bind in your bashrc to set the same line. Notice the quoting. bind 'set vi-ins-mode-string "Ⓘ "' bind 'set vi-cmd-mode-string "Ⓒ "'

[@pcfreak1992]

I knew vi-mode in zsh, but I still always used bash. Great to see that this exists in bash too. :D

[@Zaurthur]

That's amazing! I can't wait to try this.

[@oefzdegoeggl]

you should mention that this kills CTRL+L to clear the screnn. to get it back, add this to .bashrc: bind -m vi-insert "\C-l":clear-screen

[@Neonb88]

Is there a way to remap so I don't have to move my hands all the time?

[@calleha01]

It's because CTRL+L is an emacs command, and bash uses emacs mode as its default editing mode.

[@alexanderkuznetsov7597]

​@@Neonb88 you can also use "Ctrl + [" to go into normal mode just like "Esc" does

[@raktom]

Instead of this binding hit ESC or Ctrl+[ to get to normal mode (still in bash vi-mode) and then Ctrl+L to clear screen

[@statuschannel8572]

no thanks, I usually type "clear" and it does the work

[@gavinvales8928]

i watched this a while back and thought i didn't need it. but now, nearly a year later, i do.

[@soham7510]

Same

[@SamSam-df4xp]

Everyday learning from you Luke!!! Thanks.

[@craterface12]

Your channel has opened my eyes to so many things This was built into fish shell and I never knew

[@rednight2476]

Bash is clone of ksh that's about 20 times more blated with a bad case of creeping-feature-itus. vi mode is the default in Unix ksh and can be changed to emacs mode with set -o emacs. It's command set is pretty much the same as actual vi.

[@lolisamurai]

btw busybox's shell supports this as well by recompiling it with CONFIG_FEATURE_EDITING_VI enabled and setting the same vi option

[@geoptus]

Does anyone know if there's an equivalent for 'insert last argument' - \e. - while in vi mode? it's definitely not in the bind lists of either 'insert' or 'normal' modes

[@vmisev]

This is what I have in my '~/.inputrc' and that puts (left of prompt) nice green (c) for command mode and blue (i) for insert mode. imgur.com/DBUNmMw set editing-mode vi set show-mode-in-prompt on set vi-cmd-mode-string \1\e[32m\2(c)\1\e[0m\2 set vi-ins-mode-string \1\e[34m\2(i)\1\e[0m\2

[@reformed_attempt_1]

wtf only now I learned about ~/.inputrc file Thanks

[@giobot]

2:57 bbw ;)))))))))))))

[@LukeSmithxyz]

FATT

[@mrinfernodude1]

Christmas came 8 days early this year!

[@tactical_shift]

was using bash vi for quite a while, then after looking for a way to show the current mode, i found zsh, added a few lines from stack overflow and never had to look back ever since

[@Awwe12675]

I’m not speaking English language This video is the bast video for me I use vim more one year I don’t have any idea about vi on all my system This video changed my mind for every 👏🏻 thank you bro

[@103-krithickumarub6]

is there a way to change the bindings?

[@MrChozo]

You had (have?) a real Cypher-from-the-Matrix-Joe-Pantoliano-eating-a-steak thing going on here, and you were (are?) killing it, my dude. Good video, useful stuff.

[@finndriver1063]

Wondering if you have ever used fish? It also has a vi-mode and some pretty cool features right out of the box.

[@LukeSmithxyz]

I've tried fish and I especially like some features like abbreviations, but fish takes way to long to load for me to use it comfortably.

[@magnusphilosophus506]

Soo, I have dvorak and how can I configure it?

[@jonesbbq307]

Longest command I have ever typed: four words. Me: I need to use Vim mode to speed up my terminal.

[@hejhog1961]

FYI this works also in Bourne and Korn shells in Unix - it was ported over from Unix to Linux Bash shell.

[@BillSteinhauser]

Korn shell was the first Unix shell to have "vi" style editing on the command line, in latter 1980s. The bourne shell did Not have command line editing at all... you just had to backspace and retype if you needed to change/correct anything before pressing enter. I have been using unix+ksh+shell since before bash shell or Linux existed. The command line editing features from Ksh were re-written & added to bash shell using library code called "readline" to make bash shell nicer to use. The reason that you find command line editing when using "sh" on Linux, is that /bin/sh on Linux is actually running /bin/bash binary executable with a Bourne compatibility mode setting, but "readline" is still active. The reason that some vim key editing combinations are not available, like "ciw" or "ca)" is that command line editing supports the original "vi" editing features from about 1977, and not "vim" features from around 1998. When you type the "bind -P" command, you are getting a response back from the readline library code used by bash. (just to clarify some shell history, and details on command line edit functionality)

[@kid-vf4lu]

Is there a way to navigate into the whatever you `cat` or `ls` for copying in vim-mode?

[@jamieg2427]

my life suddenly improved so much. i've been wishing for this forever

[@VaclavKosar]

I cannot find Command-Mode. Is it available? Except for "v" which switches to full vim?

[@atimholt]

Didn't even mention “`v`”, which will literally take you into Vim to edit the current contents of the command line (i.e. what you’ve typed so far, or “↑/↓/j/k”'d to). Save and exit to run the command (ZZ in normal mode).

[@davidh.4944]

Specifically, 'v' opens the current readline in your default $EDITOR. The option is available in emacs mode too, under a different binding. I forget what it is.

[@eduardojreis]

Wow. It changed my life (as a computer user)

[@amosnimos]

was about time KZbin recommend me this video!

[@rafaelmartineztomas4911]

Use tmux you got vi mode and can copy paste any line of the ouput

[@Sun-po4zv]

What window manager thing is that? How does it work???

[@zlovredniyTip]

how do you make your desktop panel like this?

[@ReneKnuvers74rk]

Is there a vi-mode in st?

[@magnusanderson6681]

I'm not sure exactly why this is but it seems that bash is the one that controls the keyboard shortcuts for the command line, not st. So this works in theory on any terminal emulator

[@alexstone691]

is there set -o neovim

[@saeidsaati4021]

Thanks for the video, can you show how I can change the Esc to jk here in bash ? is it possible here ?

[@Sumguy21]

Thanks, luke. Great video!

[@uncle_esau]

Yeah but what about bash mode in vi

[@MrMhornberger]

To get around the lack of, say, yi" or ci], you can hit ctrl-x-e and it'll open up that entire command line in vim itself.

[@LukeSmithxyz]

That's in emacs mode though. In vi mode it's just v in normal mode.

[@tarasywszedzie]

What have you done to DIO, Luke? :I

[@AhmedKhaled-sj1zx]

what is DIO?

[@LukeSmithxyz]

That's DIO-sama to you.

[@rexevan6714]

KONO DIO DA !!

[@AhmedKhaled-sj1zx]

@@abdulwahabjag thnx for replying. Didn't watch that Anime

[@jantoth4699]

Great video, guys do you think that we will see sometime in future features like ci", vi", ya(

[@yussefakl8731]

Hey Luke! I’m a bit late seeing this :D when I compile code and get errors usually the compile output is several times the terminal output screen and I want to scroll to see what happened. How do I do that with vim bindings?

[@jasonxoc]

Well this blows my mind. Been using bash for over 20 years and never knew this. You should put it in your bash_profile though, not your bashrc... profile is for shell, bashrc is loaded any time bash is loaded... like running commands from ssh.

[@8cyl6speed]

How did you get that pdf preview thing in your bash

[@rochr4]

Ranger, FM with vi like bindings.

[@michalski9141]

line completion mode using your bash history would be nice

[@MrHatoi]

Ironically, this is actually the way I found out about Vim to begin with.

[@Mawkler]

What's in his terminal in the very beginning of the video? Looks sorta like a file browser. Is it a tmux plugin?

[@gz6616]

that is ranger, a terminal file manager

[@FH-ux4rf]

Hi Luke Smith. I just gave LARBS a shot, and well, I'm not experienced with VIM at all so I'm struggling a bit, but from what I can tell, it is amazingly well made! So many props to you. The whole thing, from design, to functionality, to ease of installation is just amazing! However, I noticed one thing and I tried to look it up in your nifty help document, but without luck. This video as well as a few others can be opened within the i3WM with the super + shift +e command, which is so cool, but at least on my setup the audio is unbearable. I'm guessing it's a missing codec or something, but I have no idea how to find out what is causing it. Do you (or anyone reading this) have any idea what could be causing the poor audio quality on these "internal" videos?

[@calmarcalmar]

I have these in .inputrc (since thousand years) set editing-mode vi set keymap vi So maybe I try out that "set -o vi" .. .seems to be pretty equivalent.. not sure so.

[@noscreadur]

It was there all along! I have been a ghost in a world of half arsed bindings. I set -o vi, and I am born whole at last!

[@grahamjoss4643]

that a great tip. thanks for sharing.

[@TroyFletcherKeyboards]

I liked this, but since it didn't run my bashrc I was kind of meh. I prefer Ctrl+x,Ctrl+e. Opens a proper vim session (if you've 'export EDITOR=vim' otherwise pico) and lets you set up multiple commands. Executes on save and close. Though I would prefer to see the current session command history in it. Otherwise, super comfy. :)

[@LukeSmithxyz]

The ctrl-x ctrl-e in emacs mode exists in vi mode as well: just press v while in "normal".

[@rohanghige]

Amazing video. Does it exist in cshell also. What is command for it. Can you make video for set-up of screen-key.

[@Christopher-ew7jw]

You are my hero.

[@davidjacobs7308]

Can I do more than 1 :+1 ?

[@MrSushant3]

I always wondered there must be some plugin out there for this, and here I find this. 😻

[@fubukimaru]

WOW MAN. WOW. The other day I was thinking about this feature. Thanks for your video!

[@christianlarsen2404]

Gamechanging. Thank you for this gift.

[@MarekKowalczyk]

Excellent stuff! I've had the same problem, twisting my fingers in bash. BTW, is the bashrc you're using on your GitHub?

[@svenwindpassinger2170]

super tip! thx!

[@VictorRodriguez-zp2do]

Use athame it gives you the full vim experience and it even work with vim plugins

[@gz6616]

But this disables the Ctrl+L short cut for clear screen.

[@MrSushant3]

i don't mind typing *clear* for this feature 😊

[@magnusanderson6681]

I'm only a couple days late but run bind -m vi-insert '"\C-l": clear-screen' and it sets up the keybinding - so put that in your bashrc. Also by default ctrl-l clears in normal vi mode, just not insert. Use help bind and then bind -p (lowercase)

[@somebodyoncetoldme1704]

Yiw doesn't work :(

[@0felex01]

Mind sharing that wallpaper?

[@ne6totapo]

www.pinterest.es/pin/74590937551754212/

[@zenist69]

The wallpaper its cool. Where is it from? Movie, game?

[@ploutosroman4206]

www.toca-ch.com/data/walls/120/25421037.jpg

[@ne6totapo]

link above is dead www.pinterest.es/pin/74590937551754212/

[@seneketh]

Thank you so much!!!!!!!

[@b0nes95]

I saw you press CTRL + L I assume that stopped working when using Vi mode? ^^

[@davidh.4944]

Most of the major default emacs bindings remain available. Only the ones specific to vi-mode are changed. Of course you can always manually override any of them with bind or your inputrc.

[@hassanshabbir8254]

Also check out github.com/ardagnir/athame which runs an actual vim session in the terminal.

[@bananmanx4764]

Was a bit annoyed that you could not tell if you were in insert mode or in normal mode with this so I looked up a solution for that online. check the first answer here: stackoverflow.com/questions/1039713/different-bash-prompt-for-different-vi-editing-mode If you have trouble editting the file also check this: stackoverflow.com/questions/8253362/etc-apt-sources-list-e212-cant-open-file-for-writing in short: go to /etc/inputrc and add "set show-mode-in-prompt on"

[@marauderinchief6858]

That wallpaper... WOW..

[@AndyRufasto]

I can't use Ctrl+L to clear :(

[@magnusanderson6681]

This is the only sad but I need to try to find a way to re enable it I imagine it is possible EDIT: figured it out. Run bind -m vi-insert '"\C-l": clear-screen' and it sets up the keybinding - so put that in your bashrc. Also by default ctrl-l clears in normal vi mode, just not insert. Learned by using help bind and then bind -p (lowercase)

[@drewberchtolzthofen886]

4:48 works for zsh users hehe

[@RS-hg3rp]

love u chan, more terminal arch linux stuff ;)

[@amirul264]

Thanks, is like a dream come true lol.

[@openfrom03]

thank you)

[@daffybox]

let me get that wallpaper bru

[@ne6totapo]

www.pinterest.es/pin/74590937551754212/

[@MarkBlakeney]

Adding "set -o vi" to your bash config is not the optimum way to do this! See www.reddit.com/r/vim/comments/8j589n/til_bash_ships_with_a_vi_mode/dyxh0dc/

[@8sync735]

Perturbator. Kudos.

[@aarav3890]

first thing I noticed too

[@H32-u7d]

Holy shit my mind is blown

[@Robert-dB]

Personally I've always found VI mode on the command line an evil hack ... like evim! I use emacs mode as a pico/nano mode but bind a couple of real keys to different functions. eg: Ctrl-Left/Right move by words and most importantly Insert is bound to "edit-and-execute-command" that way one keypress gets me into the _real_ VIM. (If slumming ^X^E gets you $EDITOR, but that's 3 or 4 presses)

[@DrathVader]

Pls share the wallpaper, senpai, I need it for my rice.

[@ne6totapo]

a bit late www.pinterest.es/pin/74590937551754212/

[@Cheng32290]

Love videos about VIM tips, thank you so much

[@danplt]

Vi editing is part of POSIX sh.

[@ИванКалашников-ц8л]

nice cell luke o.0

[@LukeSmithxyz]

my warden doesn't allow anime posters

[@xtdycxtfuv9353]

DIO!!!

[@sharperguy]

Funny I knew about this for a few years because I tried it and didn't like it. Just started again last week and I can never go back now.

[@breakername9995]

thankyouuuuu

[@MixterFox]

I use vi mode all the time in zsh.

[@possumcode]

Coooooool

[@marianoforti1737]

I have a serious problem with your videos. I cant stop watching. I need to go back to work. I found about vi mode in bash recently too. now I want vi mode everything.

[@DraganAlves]

Mind blown

[@HansPeter-qg2vc]

Pfff, always those vim users using vim commands in bash whilst Emacs users use bash in Emacs.

[@calmarcalmar]

Maybe .. who knows what you know or not: one of the very very useful commans in bash.. is Ctrl-r xxx I use this.. very very often.. where xxx is the a search-thing... until you find your command in the histroy. with Ctrl-r.. again.. the next will arrive i.e: Ctrl-r ssh Ctrl-r Ctrl-r Ctrl-r enter. this will select the 3rd last ssh..... command in history

[@rochr4]

Try fzf or hstr.

[@markcuello5]

Help me

[@joao_lubien]

Dio thumb? Instasub

[@francoisgervais1]

I was like, would be so nice to move through my command with h and l just like in vi... casually browsing for a solution and then.. THERE IS AN ACTUAL VI MODE???

[@magnusanderson6681]

Use b and w