folke

-- put this file somewhere in your nvim config, like: ~/.config/nvim/lua/config/lua-lsp.lua
-- usage: require'lspconfig'.sumneko_lua.setup(require("config.lua-lsp"))

local library = {}

local path = vim.split(package.path, ";")

-- this is the ONLY correct way to setup your path
table.insert(path, "lua/?.lua")
table.insert(path, "lua/?/init.lua")

LukeSmithxyz

# Luke's config for the Zoomer Shell

# Enable colors and change prompt:
autoload -U colors && colors
PS1="%B%{$fg[red]%}[%{$fg[yellow]%}%n%{$fg[green]%}@%{$fg[blue]%}%M %{$fg[magenta]%}%~%{$fg[red]%}]%{$reset_color%}$%b "

# History in cache directory:
HISTSIZE=10000
SAVEHIST=10000
HISTFILE=~/.cache/zsh/history

danielmiessler

" (Neo)Vim Configuration
" By Daniel Miessler
" August 2019

" BASIC CONFIGURATION

" Remap Escape
inoremap jk <ESC>

" Remap the leader key to the spacebar

romainl

Linting your code, the vanilla way

You may want a linter plugin to lint your code in Vim but you probably don't need it. At least try the built-in way before jumping on the plugin bandwagon.

Defining makeprg

autocmd FileType <filetype> setlocal makeprg=<external command>

This autocommand tells Vim to use <external command> when invoking :make % in a <filetype> buffer. You can add as many similar lines as needed for other languages.

romainl

My Vim-related gists

Long-form

• How to use Tim Pope's Pathogen
• Idiomatic vimrc (superseded by idiomatic-vimrc)
• Clipboard sharing on Mac OS X is easy
• Apprentice — The Making Of
• Vim: pushing built-in features beyond their limits
• The right way to override any highlighting if you don't want to edit the colorscheme file directly

csswizardry

Vim without NERD tree or CtrlP

I used to use NERD tree for quite a while, then switched to CtrlP for something a little more lightweight. My setup now includes zero file browser or tree view, and instead uses native Vim fuzzy search and auto-directory switching.

Fuzzy Search

There is a super sweet feature in Vim whereby you can fuzzy find your files using **/*, e.g.:

:vs **/*<partial file name><Tab>

itod

• Kinesis Freestyle (Terrible key switches. Mushy and un-lovable)

• Kinesis Freestyle Edge (Traditional layout with too many keys, mech switches, proably too big to be tented easily/properly)

• Matias Ergo Pro (Looks pretty great. Have not tried.)

• ErgoDox Kit (Currently, my everyday keyboard. Can buy pre-assembled on eBay.)

• ErgoDox EZ (Prolly the best option for most people.)

romainl

Vim: pushing built-in features beyond their limits

The situation

Searching can be an efficient way to navigate the current buffer.

The first search commands we learn are usually / and ?. These are seriously cool, especially with the incsearch option enabled which lets us keep typing to refine our search pattern. / and ? really shine when all we want is to jump to something we already have our eyeballs on but they are not fit for every situation:

• when we want to search something that's not directly there, those two commands can make us lose context very quickly,
• when we need to compare the matches.

zchee

set smoothscroll
set autoupdategist

map .t :tabnew chrome://newtab<CR>

let configpath = '/path/to/your/.cvimrc'
set localconfig " Update settings via a local file (and the `:source` command) rather"

dkasak

" XDG Environment For VIM
" =======================
"
" References
" ----------
"
" - http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html#variables
" - http://tlvince.com/vim-respect-xdg
" - https://gist.github.com/kaleb/3885679 (the original version)
"