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
#!/bin/bash | |
### This produces a list of all QSOs that are confirmed by *either* LoTW or eQSL | |
### from a given log file -- in my case, a cqrlog backup file, which keeps | |
### these flags separately -- to be used with diploma applications that | |
### accept either of the two and verify them by their own mysterious means. | |
# Requires: | |
# * adifmt - https://github.com/flwyd/adif-multitool | |
# * ripgrep - https://github.com/BurntSushi/ripgrep |
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
;; hack-load-history.el -- Fix broken load-history alist. | |
;;; Commentary: | |
;; On Termux and apparently, certain other Android builds of Emacs, | |
;; something weird happens to load-history at the last stages of | |
;; initialization. This variable contains the list of all loaded | |
;; packages and the objects they provide, and mysteriously, one of them | |
;; turns up nameless. |
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
#!/bin/bash | |
GITDIR=RasterPropMonitor.wiki | |
HTMLDIR=html | |
cd `dirname $0` | |
cd $GITDIR | |
git pull | |
#gollum-site import | |
gollum-site --working --base_path ./ generate |
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
/* | |
This is an example of getting at a module and it's parameters using reflection. | |
It's already out of date, but remains here for the benefit of others who need to do something like this in KSP. | |
Since the whole raster screen project started as an attempt to get a Firespitter MFD to show | |
what I wanted, I tried to duplicate what Snjo's own FSmonitorInterface class did | |
to address the screen in my own plugin, without actually duplicating the screen | |
module itself. That did not work -- KSP loads assemblies in an alphabetical | |
order, and aggressively checks them for using types that are not currently in memory, |