- using Ansible command line:
ansible-playbook --connection=local 127.0.0.1 playbook.yml- using inventory:
127.0.0.1 ansible_connection=localansible-playbook --connection=local 127.0.0.1 playbook.yml127.0.0.1 ansible_connection=local| #!/bin/bash | |
| less_command='| less $less_no_init -aiF -Ps"Manual page\: $man_page (?ltline %lt?L/%L.:byte %bB?s/%s..? (END):?pB %pB\%..)"' | |
| # Get section | |
| if [[ $1 =~ [0-9]+ ]] | |
| then | |
| section=$1 | |
| shift | |
| fi |
| ## MPV Keyboard Shortcut to match VLC | |
| ## Path: /etc/mpv | |
| ## ================== | |
| UP ignore # ignore keybinds for | |
| DOWN ignore # directional keys | |
| LEFT seek -10 | |
| RIGHT seek 10 | |
| SPACE cycle pause # toggle pause |
04/26/2103. From a lecture by Professor John Ousterhout at Stanford, class CS142.
This is my most touchy-feely thought for the weekend. Here’s the basic idea: It’s really hard to build relationships that last for a long time. If you haven’t discovered this, you will discover this sooner or later. And it's hard both for personal relationships and for business relationships. And to me, it's pretty amazing that two people can stay married for 25 years without killing each other.
[Laughter]
> But honestly, most professional relationships don't last anywhere near that long. The best bands always seem to break up after 2 or 3 years. And business partnerships fall apart, and there's all these problems in these relationships that just don't last. So, why is that? Well, in my view, it’s relationships don't fail because there some single catastrophic event to destroy them, although often there is a single catastrophic event around the the end of the relation
I should preface this by saying that I got a Withings Smart Body Analyzer for Christmas last year and I’ve been generally happy with it. It purports to be able to take my heart rate through my bare feet and that seems not to work for my physiology, but overall I’m a fan. If if their Wikipedia page is to be believed they are having a pretty rad impact on making the Quantified Self movement more for normal people and they only have 20 full time employees. Also they try hard to use SI units, which I can get behind. Anyway, on to the rant.
I originally called this post “Everything wrong with the Withings API” and I meant it. For every useful field I can extract from their “award winning” app, I have spent an hour screaming at the inconsistencies in their implementation or inexplicable holes in their data
| #!/bin/bash | |
| # | |
| # rotate_desktop.sh | |
| # | |
| # Rotates modern Linux desktop screen and input devices to match. Handy for | |
| # convertible notebooks. Call this script from panel launchers, keyboard | |
| # shortcuts, or touch gesture bindings (xSwipe, touchegg, etc.). | |
| # | |
| # Using transformation matrix bits taken from: | |
| # https://wiki.ubuntu.com/X/InputCoordinateTransformation |
| #!/bin/bash | |
| # backlight brightness controls. use freely | |
| # and adjust sysfs directory if not on toshiba | |
| # $author Brice Burgess @iceburg | |
| sysfs="/sys/class/backlight/toshiba" | |
| max=`cat ${sysfs}/max_brightness` | |
| level=`cat ${sysfs}/brightness` |
This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.
The script is here:
#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
| #!/bin/bash | |
| # Hacked together by JeroenJanssens.com on 2013-12-10 | |
| # Requires: https://github.com/joewalnes/websocketd | |
| # Run: websocketd --devconsole --port 8080 ./chat.sh | |
| echo "Please enter your name:"; read USER | |
| echo "[$(date)] ${USER} joined the chat" >> chat.log | |
| echo "[$(date)] Welcome to the chat ${USER}!" | |
| tail -n 0 -f chat.log --pid=$$ | grep --line-buffered -v "] ${USER}>" & | |
| while read MSG; do echo "[$(date)] ${USER}> ${MSG}" >> chat.log; done |