0.0.0.0 feedback.microsoft-hohm.com | |
0.0.0.0 search.msn.com | |
0.0.0.0 a.ads1.msn.com | |
0.0.0.0 a.ads2.msn.com | |
0.0.0.0 a.rad.msn.com | |
0.0.0.0 ac3.msn.com | |
0.0.0.0 ads.msn.com | |
0.0.0.0 ads1.msn.com | |
0.0.0.0 b.ads1.msn.com | |
0.0.0.0 b.rad.msn.com |
import os | |
import re | |
import subprocess | |
from bs4 import BeautifulSoup | |
import rules | |
def replacer(url, html): | |
new = html | |
reload(rules) |
SOURCES=$(wildcard **/*.md) $(wildcard *.md) | |
HTML=$(patsubst %.md, build/%.html, $(SOURCES)) | |
all: $(HTML) | |
build/%.html: %.md | |
mkdir --parents $(dir $@) | |
pandoc -s $< -o $@ | |
.PHONY: |
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.
This is a quick example showing how to use regexes to find tri-grams in Shakespeare...well, 570,872 of them, anyway, if we do some basic filtering of non-dialogue.
Though tokenization and n-grams should typically be done using a proper natural language processing framework, it's possible to do in a jiffy from the command-line, using standard Unix tools and ack, the better-than-grep utility.
# View public IP
- curl -s checkip.dyndns.org | sed 's#.Address: (.)</b.*#\1#'
- wget -qO - icanhazip.com
- curl ifconfig.me
- curl ident.me
- dig +short myip.opendns.com @resolver1.opendns.com
- lynx -dump ifconfig.me | grep 'IP Address'
- curl ipecho.net/plain
- curl bot.whatismyipaddress.com
- curl ipinfo.io
#!/usr/bin/env bash | |
# This script requires: | |
# - that the directory $HOME/.mpv exist | |
# - that the program socat be installed | |
# - that you start mpv with the unix socket feature pointing at that directory | |
# I recommend an alias in your .bashrc or equivalent file: | |
# alias mpv="mpv --input-unix-socket=$HOME/.mpv/socket" | |
socket="$HOME/.mpv/socket" |
_________ _____ _______________ _____
\_ ___ \\ \\___________ \____ / ____\ ~/.bash/cliref.md
/ \ \/| | | || _/ __ \ __\ copy/paste from whatisdb
\ \___|__ |_|_ || | \ __/|_ | http://pastebin.com/yGmGiDQX
\________ /_____ \_||____|_ /____ /_| [email protected]
20160515 \/ 1527 \/ \/ \/
alias CLIRef.txt='curl -s "http://pastebin.com/raw/yGmGiDQX" | less -i'
Unlike your typical computer where you usually shutdown properly, I cannot rely on this during the use of my Raspberry Pi. If the Raspberry Pi is improperly shutdown too many times, data corruption in the file system leading to unbootable SD card may result. So we should use a read-only file system.
Full instructions and explanations are obtained from this link but you can run these commands directly. I modified some of the instructions for personal convenience.
Login with default username: alarm, password: alarm
#Optionally enable root over SSH. The rest of these instructions assume u are in root.