Each day at our company, developers are required to document their activities, painstakingly jotting down their daily work and future plans. A monotonous chore that I just really dislike.
So now, there's a scribe for that :
Each day at our company, developers are required to document their activities, painstakingly jotting down their daily work and future plans. A monotonous chore that I just really dislike.
So now, there's a scribe for that :
| #! /usr/bin/env bash | |
| usage() { | |
| echo " | |
| Bind/unbind a USB device from a given vendor:product id | |
| Usage: $(basename "${BASH_SOURCE[0]}") [-h] [-d|--dry-run] [--hdmi|microsd|usba|ssd250] [--detect=deviceid:vendorid] [on|off] | |
| Example usage: $(basename "${BASH_SOURCE[0]}") --hdmi off | |
| Example usage: $(basename "${BASH_SOURCE[0]}") --detect=27c6:609c | |
| " >&2 |
| #!/usr/bin/env bash | |
| # !!!!!!!!!!!!!!!!!!!!!!!!!!! | |
| # This script is unmaintained | |
| # !!!!!!!!!!!!!!!!!!!!!!!!!!! | |
| # !!!!!!!!!!!!!!!!!!!!!!!!!!! | |
| # This script is unmaintained | |
| # !!!!!!!!!!!!!!!!!!!!!!!!!!! |
Highly extensible software like Emacs, Vim, and Neovim tend to grow their own package managers. A software developer, for example, might want to install editor plugins that hook into a particular programming language's linter or language server. The programmer's text editor is therefore extended to support managing additional software to extend the text editor. If this loop continues for too long, the programmer's editor becomes more delicate and complex. The remedy for this problem is to manage software using dedicated tools apart
How to configure FreeBSD and applicable applications to work with Yubikey for authentication. This serves as my work-in-progress documentation of the configuration knobs needed to make this work properly.
libykcs11.so)| #!/usr/bin/env julia | |
| function ts_to_s(ts::AbstractString) | |
| secs = tryparse(Float64, ts) | |
| if secs !== nothing | |
| return secs | |
| end | |
| hours, mins, secs = parse.(Float64, split(ts, ':')) | |
| return (hours * 60 * 60) + (mins * 60) + secs | |
| end |
Native wayland support is now working consistently for me in VSCode, giving much better text rendering. Unfortunately, it's still hidden behind some command-line flags.
By adding some files to /usr/local/*, you can ensure that VSCode always launches with these flags.
Assuming that the VSCode launcher is /usr/bin/code-oss (as is the case in Arch):
/usr/local/bin/code-oss with the following content:I got Arch Linux ARM installed on a Lenovo Chromebook Duet! I mostly used the instructions from the Arch Wiki as reference.
You can use this diagram as a template to create your own git branching diagrams. Here's how:
https://gist.githubusercontent.com/bryanbraun/8c93e154a93a08794291df1fcdce6918/raw/bf563eb36c3623bb9e7e1faae349c5da802f9fed/template-data.xml