People who have neofetch in their .bashrc/.zshrc: *Pathetic*

...I don't even see the code. All I see is blonde, brunette, redhead....

....it is him.... and we are in the matrix D:

Cypher wanted that steak!!!😎

Yeah I used to have surround, which I guess it very useful, but I just never got in the habit of using it.

yes it is... it could be said im an older user... cos, i started with line numbers as a kid and still need them now

I don't take notes.

I don't record on a 1080p screen, so that's why there's no 1080p option.

#Vi ftw

ed is standard editor for UNIX

The only reliable benefit of using emacs is that people would stop nagging me to use emacs.

@@LukeSmithxyz oh ok honestly I should get back to watching you more because last video I watched was with you using emacs lol and your content is really enjoyable

Well I've never used emacs in a video here.

@@LukeSmithxyz Hmm seems like my memory is getting rusty oof

@@LukeSmithxyz Vimmachines will nag you much harder than emarcsists if you were to switch.

practice practice... vim tutor practice yt vids practice practice vim tutor practicepracticepracticepracticepracticepracticepracticepractice ive been using vim for a while now and I still learn new stuff every time I use it

he uses ffmpeg for screen recording and mpv to play his webcam feed.

Your compilation script is good stuff man, i made a few tweaks to auto open and/or refresh pdf upon compilation since i never want to compile without seeing what is actually happening. .vimrc: autocmd VimLeave *.tex !~/.local/bin/compiler.sh % vimleave compile.sh: if [ "$2" == "" ]; then pdflatex "$1" # Open corresponding .pdf document if not already open. Otherwise, # reload .pdf file by sending an 'r' keypress via xdotool. if [ ! $(pgrep -f "mupdf-x11 .*($file).pdf") ]; then mupdf-x11 $(echo "$1" | sed 's/tex$/pdf/') & disown else xdotool search --name "$file".pdf | xargs -I "$file".pdf xdotool key --window "$file".pdf r fi elif [ "$2" == "vimleave" ]; then # Close corresponding .pdf document if open. [ ! $(pgrep -f "mupdf-x11 .*($file).pdf") ] && exit 0 || xdotool search --name "$file".pdf | xargs -I "$file".pdf xdotool key --window "$file".pdf q fi

Nevermind. I just found it at kzfaq.info/get/bejne/odlxmdB7y8rZkmQ.html thanks for the great content!

Pete West is a variable holding a key. Luke's leader is space, but by default it is one of the slashes, "\" I think.

@@TheJamesconroy Thanks, James.

it was probably set in defaults.vim which is not loaded if you have any .vimrc

vim is legend :)

You will want to install UltiSnips (to make quickly editable and expandable pieces of code) and the ALE linting plugins (for good code practices). I then use a short script to compile the current file and bind it to r.

i'd like to interject for a moment. "vi" is the "vi"sual editor for ed and vim is just vi improved. The commands used in ed also work in vim, so in a sense he is actually using ed.

spoiler: he will start using neovim

Vim 8 has asynchronous support also :terminal now. What's neovim got removed that bloats vim?

​@@rolandicus1771 1) Neovim has removed all the code for all the dead systems that wouldn't be able to run Vim anyway. 2) Neovim can be retrofitted with other languages without recompiling it every time 3) Lua as an alternative to VimScript 4) Neovim separates the interface from the editor 5) Neovim has an API 6) Neovim does it better :P About 1), this removes tons of code that doesn't do anything anyway. I know they also replaced some parts of Vim's own code with libraries, which should at least in theory make it more maintainable, but you will have to ask the devs about details. About 2), if you want to write a Vim plugin in for example Python you need to compile Vim with Python embedded. That's not a big deal for something as common as Python, but it is a big problem for other languages. Either your package manager offers an option, or you will have to get all the dependencies and compile it yourself. And not just that, now support for that language is tied to Vim's development, adding yet another maintenance burden. In Neovim support for other languages can be just retrofitted. Want to write a plugin in your obscure pet language? Just hook up the API client and you're good to go. I even wrote my own for Racket (a type of Lisp), you can find the whole list here: github.com/neovim/neovim/wiki/Related-projects#api-clients This alone removes tons of bloat and maintenance nightmare out of the editor. I can update and maintain my Racket client completely at my own pace instead of being tied down to Neovim's release schedule. About 3), VimScript is not going anywhere, and it's a good language for what it is meant to be: a configuration language for a text editor. But if you want to do more complicated stuff, Lua is a better choice. About 4), just as support for plugins in other languages can be retrofitted, so can a GUI be retrofitted. The GUI is really just a plugin. Lots of interesting stuff, you can even embed Neovim into another editor or IDE. So even if you are forced to use a certain IDe at work, you could just embed Neovim into it and have the real things instead of an approximation. github.com/neovim/neovim/wiki/Related-projects#gui About 5), this is the killer feature for plugin authors. If you have ever written a plugin for Vim you will know how to accomplish the simplest of tasks you will have to go through a series of rituals. The API gives a set of primitive building blocks to work with, so you no longer need to sacrifice a virgin goat on a full moon to set an option in a buffer that is not the current one. Even if you don't write full plugins, the API can allow you to write much nicer mappings. I really regret not making Info.vim just Neovim-only and using the API. About 6), that one is intentionally provocative :) But seriously, all the features Vim copied, it copied in an incompatible and worse manner. There is no reason to use JSON over MessagePack, it's slower and uses more memory. People who have worked with both editors agree that Neovim's way is easier to work with.

@@HiPhish The best sales pitch I've ever read and it's for a free program.

@@HiPhish neovim sounds the balls for development. I use vim for bash scripting so I guess in that respect its available on most servers I bother so it's fine. Enjoy the neovim silver ship as you glide through the high altitudes ;)

in 20 years time I expect to hear the same arguments again, like last time

What about the pinky injuries

I don't use tmux except as a dropdown terminal (super+u). I do all my real tiling in i3.

:set spell!

:e $MYVIMRC

just in case you haven't figured that out already: its probably because tmux doesn't support 256 colors by default. unix.stackexchange.com/questions/1045/getting-256-colors-to-work-in-tmux TLDR: ~$ which tmux tmux: aliased to TERM=xterm-256color tmux set -g default-terminal "screen-256color"

vim awesome

trash dont use it lmao

You never realize how fast you are with a keyboard until you use shortcuts.