You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test multiple versions of Package X against multiple versions of Package Y
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Easily disable fonts that aren't in your language, for Debian and derivatives (and possibly other Linux distros)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create symlinks in your ~/bin for Flatpak apps, with sensible names
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Query GitLab v4 API endpoints with curl and jq; handles record pagination
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bash programmable completion example for "cuddled" options + arguments
Bash programmable completion for -nvalue / --name=value options
I was reading [an old debian-administration.org post][debadm] about
[Bash programmable completion][pcomp], and I had the same question as this
person:
I created a script and I use bash_completion, but I cannot figure out how
to allow the completion of "--name=value1 --name=value2" (the "=" sign in
the middle stop any other completion, and I tried to play with
suffixes/prefixes without any success :s
If you have the ability to do so, please compute SHA1 hashes for any files you intend to share with the Weirauch Lab. These hashes, or "checksums," are critical for verifying that we've received your data 100% intact and unmodified.
You will need to save these checksums into a file, then transmit or store that file alongside the original data. Instructions for macOS and Linux are directly below. For Windows, please follow the instructions in the "Generating checksums on Windows" section.
Generating checksums on Unix
Here is a one-liner that will do the job on a typical Unix/Linux system. macOS is also Unix, but if you are not familiar with the command line, see the section "Extra guidance for Mac users," below. If you use Windows and have Git Bash or Cygwin available, this method should also work for you.
Boilerplat for a userscript that hooks into the XHR 'load' event, for handling lazy-loaded pages
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters