|Brennen Bearnes 0e67e3de4d||1 month ago|
|etc||1 year ago|
|home||1 month ago|
|.gitignore||11 months ago|
|README.md||4 months ago|
|install.sh||2 months ago|
|ns-control||1 year ago|
If you're reading this on GitHub, it may be out of date. The canonical copy of this repository lives on code.p1k3.com.
This repo is for dotfiles, utility scripts, and other things in my personal setup. Ideally, it includes most of the bits and pieces that make a personal machine usable for me. It may occasionally serve as a testbed for things that will eventually become standalone projects.
I generally use Debian and Debian-like GNU/Linux systems (including Ubuntu), with the xmonad tiling window manager rather than a full desktop environment like Gnome or KDE. I usually edit text in Vim, with VimWiki for notes. I maintain a blog called p1k3 using wrt.
I have a partially-finished book about the command line which may be relevant.
As of October 2020, this collection is actively maintained, although it doesn't meet the standards of quality, consistency, or documentation you might want from a real software project.
(Then again, neither do most software projects.)
Except as noted below or in the body of specific files, and to the extent possible under law, I, Brennen Bearnes, waive all copyright and related or neighboring rights to the contents of bpb-kit. Go to town.
In the general case, I'm a proponent of Free Software, and correspondingly of the pragmatic value of strong copyleft licenses like the GNU General Public License. Where I have the option, I'll generally license more substantial projects under the GPL, with a view towards impeding the corporate capture of every available computational resource and generally throwing a little grit in the gears of capital in these latter days before it finishes murdering the entire biosphere. (As no one uses my software, this is a purely symbolic gesture, but what the hell.)
All that said, this is a trivial repository of configuration fragments and small utility scripts for a very limited audience. It seems likely to do the most good if nobody has to worry about the bureaucracy of grabbing bits and pieces of it.
From time to time, I may incorporate code from other sources in this collection, as long as it's in the public domain or under a license that meets the Debian Free Software Guidelines. In the latter case, I'll do my best to ensure that said code is clearly marked.
I have thiefed ideas and bits of configuration from the following projects and people:
At this writing I use ZSH on personal systems and Bash when writing tutorials, doing tech support, or working on production server systems. I like to keep lots and lots of history. I think shell scripting is a nightmare for most real tasks, but I do it pretty often anyway.
.zshrc- nothing fancy
.sh_common- aliases and variables for both Bash and ZSH; no Bash compatibility guarantees here, since I mostly don't use custom aliases in Bash
Scripts here fall into a handful of categories:
Many of these are unlikely to be portable, useful, or documented.
cheat: a place to hang a personal cheatsheet of sorts
chrome-incognito: run Google Chrome in incognito mode
dmenu_unique: run dmenu with big fonts and vertical, only showing each entry once
dog: concatenate argument strings with stdin
edit-clipboard: edit the current text selection in
enterprise: play a sound like the USS Enterprise engines in TNG
filter-decorate: splat some text dingbats into HTML I write sometimes
filter-exec: replace text in-between markers with result of shell-script execution
filter-exec-raw: like above, but different
filter-exec-stdin: feed text in-between markers to standard input of a command, replace it with output
filter-markdownify: convert a few things in old DigitalOcean tutorials to Markdown
filter-vertical: verticalize a string
firefox-fromselection: open a selected url in firefox
fragment-bullet: print out a "random" dingbat character
fragment-entry: stub blog entry
fragment-entry-gallery: stub blog entry with gallery
fragment-entry-poem: stub blog entry with poem
get-external-ip: print public IP address
gif-sel-15: take an animated gif of selected screen region
git-diff-wrapper: use vim with
grab-sel: take a screenshot, take a screenshot of a selected region
json_decode.php: decode JSON into PHP data structures
jsonprint.pl: pretty-print JSON with Perl
dmenuto pick a window to jump to
listusers: print an HTML list of users
lynx-wrapper-edit: edit a p1k3 entry in vim and re-render everything
dshto check status on a list of machines (stub)
mostrecent: print the name of newest file in the current directory
notesession: start a tmux named session for notes
photocp: copy photos from various media to a home directory location
pmwhich: find the on-filesystem location of a Perl module
rightnow: print the current time in a variety of formats
saytime: speak the time with Festival
snowday: is it a snow day for the Boulder Valley School District?
ssh-nofucks: SSH to an address, I don't really care if the key has changed
st: get status using myrepos
timelog: parse a timelogging format (I use this to bill for contracting)
timeslice: aggregate some data for a given date range or file's implied date
today: print a date
todaydir: find a p1k3 dir for the current date
uni: search unicode codepoint names (via @chneukirchen)
unsorted-unique: print all lines of input once (just an
wip: move a p1k3 file into a work-in-progress directory
words: split input into individual words
wthr: use unicode snowflakes to display CPU load
xm: call xmodmap
xmonad.start: personal version of xmonad startup script
xtfix: do a subtle color shift within the current xterm
put-mv: stash a file path, copy or move it to the current directory
The fragments directory is for code snippets that I write in the course of testing some idea, checking a technique, or trying to solve a problem posed by friends on IRC.
They're typically the kind of thing I'd throw in a random file called something
test.sh and overwrite later. It seemed useful to start collecting these
The cheatsheets directory is mostly empty, but may become a repository of useful shorthand documentation for the increasingly-many things I use that are not discoverable or memorable enough for my deteriorating long-term memory.
tmux for terminal multiplexing (i.e., most of what GNU Screen does).
In practice, this means that I rely on it for
.tmux.conf is brief, but does contain one useful
snippet for correcting weird Esc-key behavior in Vim.
My Vim setup was once written to be easily copied by new users. It's gotten a little out of hand since then.
.vimrc- see file for installation details
.hacksrcif it exists
.Xresourcestweaks xterm behavior and a number of fonts
.hacksrcis linked to
bin/xmonad.startfor a drop-in replacement for default XMonad startup on some Debian-like systems, including Gnome/Unity stuff and the like. Perpetually not-quite-right.
See instructions in ns-control.