-
Set and export shell variables
Use a helper variable for the prefix name:
MYPREFIX=cudatest
#!/bin/bash | |
# | |
# Extract list of zero-based frame indices with timestamps. | |
# | |
ffprobe -v error -show_entries frame=pkt_pts_time \ | |
-select_streams v -of csv=p=0 "$1" | grep -n '^' \ | |
| while read L; do | |
i="${L%%:*}" | |
echo "$((i-1)):${L#*:}" |
#!/bin/bash | |
# | |
# Doesn't print the content of the actual diff yet. | |
# Probably fails to produce identical output in some | |
# cases. | |
# | |
git log --pretty='format:From %H%nFrom: %an <%ae>%nDate: %aD%nSubject: [PATCH] %s%n%n%b%n' "$@" |
#!/bin/sh | |
# | |
# The Folding@home Web Control UI seems to bug out | |
# frequently (at least on Chrome). It'll go into a | |
# page refresh loop from which it will not recover | |
# until the browser cache is cleared manually. | |
# | |
# This script launches a fresh Chrome window using | |
# app mode and incognito to eliminate any leftover | |
# cached data. If the UI bugs out, just ctrl-w the |
#!/bin/bash | |
clear | |
while z="$(cpupower monitor -i .3333 -m Mperf)"; do | |
echo $'\e'"[0;0H$z" | |
done |
#!/bin/false | |
# | |
# This file exists because i3 really sucks at starting dmenu_run. | |
# | |
# Very often when I type mod4+d followed by "steam" and an enter keypress | |
# the first letter gets dropped (I assume because dmenu_run hasn't captured | |
# the keyboard yet). What ends up happening is that dmenu_run sees "team" | |
# and automatically finds the closest match which happens to be "teams". | |
# | |
# I almost never fucking want to launch Microsoft Teams, but I launch the |
Xcursor.size: 24 | |
Xft.antialias: true | |
Xft.rgba: none | |
Xft.hinting: true | |
Xft.autohint: true | |
Xft.hintstyle: full | |
! black | |
URxvt*color0: #000000 | |
URxvt*color8: #686868 |
#!/bin/bash | |
set_git_configs() | |
{ | |
git config --global pull.ff only | |
} | |
set_git_aliases() | |
{ | |
local -A ALIAS name |
/** | |
* Overrides the glibc function. Will always return true. | |
* | |
* Note: Although this should be ok for most applications it can | |
* lead to unwanted side effects. It depends on the question | |
* why the programm calls isatty() | |
* | |
* Compiling | |
* | |
* $ gcc -s -fpic -shared -o libtricktty.so trick_tty.c |