Where does this show???
A Pen by erika harvey on CodePen.
| // | |
| // Variables | |
| // -------------------------------------------------- | |
| // Variables directly translating Bootstrap variables | |
| // ------------------------- | |
| $s2bs-border-radius-base: $border-radius !default; | |
| $s2bs-border-radius-large: $border-radius-lg !default; | |
| $s2bs-border-radius-small: $border-radius-sm !default; |
Where does this show???
A Pen by erika harvey on CodePen.
| #!/bin/bash | |
| ## | |
| ## Simple logging mechanism for Bash | |
| ## | |
| ## Author: Michael Wayne Goodman <goodman.m.w@gmail.com> | |
| ## Thanks: Jul for the idea to add a datestring. See: | |
| ## http://www.goodmami.org/2011/07/simple-logging-in-bash-scripts/#comment-5854 | |
| ## Thanks: @gffhcks for noting that inf() and debug() should be swapped, | |
| ## and that critical() used $2 instead of $1 |
| # vim:fileencoding=utf-8:ft=conf | |
| # Font family. You can also specify different fonts for the | |
| # bold/italic/bold-italic variants. By default they are derived automatically, | |
| # by the OSes font system. Setting them manually is useful for font families | |
| # that have many weight variants like Book, Medium, Thick, etc. For example: | |
| # font_family Operator Mono Book | |
| # bold_font Operator Mono Thick | |
| # bold_italic_font Operator Mono Medium | |
| font_family Hack |
| " copy all this into a vim buffer, save it, then... | |
| " source the file by typing :so % | |
| " Now the vim buffer acts like a specialized application for mastering vim | |
| " There are two queues, Study and Known. Depending how confident you feel | |
| " about the item you are currently learning, you can move it down several | |
| " positions, all the way to the end of the Study queue, or to the Known | |
| " queue. | |
| " type ,, (that's comma comma) |
| function! yankring#reset() abort | |
| let s:yankring = [] | |
| for l:i in range(1, 9) | |
| execute 'let l:contents = @' . l:i | |
| call add(s:yankring, l:contents) | |
| endfor | |
| endfunction | |
| call yankring#reset() | |
| function! yankring#yank(contents) abort |
| import logging | |
| import threading | |
| import os | |
| import subprocess | |
| logging.basicConfig(format='%(levelname)s:%(message)s', level=logging.INFO) | |
| class LogPipe(threading.Thread): |
| package channel | |
| import ( | |
| "fmt" | |
| "sync" | |
| "time" | |
| ) | |
| func ExampleUnbufferedSend() { | |
| c1 := make(chan string) |
| #!/usr/bin/sh | |
| if [[ $# -eq 0 ]]; then | |
| echo "Usage: $0 <backup_dir>" | |
| exit | |
| fi | |
| destination=$1 | |
| if ! type "pv" > /dev/null; then | |
| echo 'pv' command not found on your system, install it to get a nice progress indicator... | |
| else |
Answer by Jim Dennis on Stack Overflow question http://stackoverflow.com/questions/1218390/what-is-your-most-productive-shortcut-with-vim/1220118#1220118
Your problem with Vim is that you don't grok vi.
You mention cutting with yy and complain that you almost never want to cut whole lines. In fact programmers, editing source code, very often want to work on whole lines, ranges of lines and blocks of code. However, yy is only one of many way to yank text into the anonymous copy buffer (or "register" as it's called in vi).
The "Zen" of vi is that you're speaking a language. The initial y is a verb. The statement yy is a simple statement which is, essentially, an abbreviation for 0 y$:
0 go to the beginning of this line. y yank from here (up to where?)