Installing a man page is not easy as there are little infos out there about it.
After a lot of trial and error, google searches and alpha publishing my app I finally have a collection of things I need to do to get it working:
// <script> | |
/* sample output | |
$ node ../bind-for-arrows.html | |
_this: 4ms | |
.bind: 25ms | |
bind: 4ms | |
_this, calls only: 1ms | |
.bind, calls only: 4ms | |
bind, calls only: 0ms |
setmetatable(_ENV, { __index=lpeg }) | |
VARS = {} | |
function eval(...) | |
local args = {...} | |
local accum = args[1] | |
for i = 2, #args, 2 do | |
local operator = args[i] | |
local num2 = args[i+1] |
setmetatable(_ENV, { __index=lpeg }) | |
Scopes = { {} } | |
function eval_expr(expr) | |
local accum = eval(expr[2]) -- because 1 is "expr" | |
for i = 3, #expr, 2 do | |
local operator = expr[i] | |
local num2 = eval(expr[i+1]) |
;Recommended, but not required: | |
SendMode Input | |
#NoEnv | |
#SingleInstance force | |
#Include <dual/dual> | |
dual := new Dual | |
#Include <dual/defaults> |
#!/usr/bin/env bash | |
# the directory that contains this script | |
base=$( cd "$(dirname "${BASH_SOURCE[0]}")" ; pwd -P ) | |
# ----------------------- | |
# Hugo Version Manager | |
# Author: Jim Frenette | |
# May 21, 2019 |
//------------------------------------------------------------- | |
// | |
// Hypothesis: | |
// | |
// Promises/A is a Monad | |
// | |
// To be a Monad, it must provide at least: | |
// - A unit (aka return or mreturn) operation that creates a corresponding | |
// monadic value from a non-monadic value. | |
// - A bind operation that applies a function to a monadic value |
mix3d asked for some help using this guide with windows so here we go. This was tested with Windows 10. Run all commands in Git Bash once it's installed.
Github will be the main account and bitbucket the secondary.
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?)
These are my own personal notes on how i setup a Pi Zero W as an access points it is a blatant copy of this: https://gist.github.com/tcg/0c1d32770fcf6a0acf448b7358c5d059 but is just missing a couple of things from: http://imti.co/post/145442415333/raspberry-pi-3-wifi-station-ap and like tcg, this is not intended as a guide but notes as i will invariably have to rebuild this sometime and i have broken biscuits for brains.
this is really just the same info as here https://gist.github.com/gbaman/975e2db164b3ca2b51ae11e45e8fd40a
cmdline.txt
add: modules-load=dwc2,g_ether
after the word rootwait
config.txt
and add dtoverlay=dwc2
to the end of the filessh