This has very little utility, but might demonstrate a general
approach for using Lynx as a viewer for HTML files generated from some
other source and editing them from there. You hit `e` in Lynx and it
calls whatever editor is defined.
Hit `o` to set options and change the
editor in there to lynx-wrapper-edit, making sure to hit the "write
changes to disk" or whatever it says checkmark before applying changes.
This works by taking the path that Lynx passes off for the filename to
edit, changing part of that path with sed to reflect where the source
file is, and then handing that to vim to edit. After vim finishes, it
re-renders the static HTML files that Lynx is viewing.
I had to remember to install these by hand:
- redshift-gtk - make the screen burn my eyes less
- ranger - file manager
- rofi - thing for selecting from a menu, used by my xmonad config
- xsettingsd - using this in place of gnome settings daemon thingy
- wmctrl - util for manipulating x window stuff
Took cowsay out of the list, because if cowsay is available, then Ansible
uses it to display everything, no matter what you do with configuration
values, because Ansible is bad software.
No real need to have this copy photocp to /usr/local/bin any more.
I've come to rely on this thing, for better or worse. Mostly as a way
to paper over the hilariously inconsistent clipboard behavior of a modern
apps like browsers.
Turns on syntastic checking for Perl, and adds podchecker so it'll also
catch errors in POD.
Changes the marker xmobar is using for currently active workspace.
...uses the git-do in bpb-kit to run make in root of current repo. I
didn't replace ,m with this because it seems like a bit of a special case
- you may not be in a git repo, or your desired Makefile may live in the
current directory rather than the root of the repo.
It'd be nice to use myrepos to do this, but although you can use
`mr run make`, it does this in the current working directory rather than
the top-level, and I don't see an easy way to override this. (It might
also be kinda risky if you fired it off in, say, your home directory.)
This mostly covers things either bound to an F-key or to some leader
sequence. It's not something I'm likely to directly use too often,
but it seems like a good way to remember what things are on systems
where I haven't physically put a piece of tape across the top of
the keyboard.