Jiří Špaček geostarling

geostarling / guix-bug-39671-boot-ok

Created February 19, 2020 21:35

	[ 0.000000] Linux version 5.4.8 (nixbld@) (gcc version 7.4.0 (GCC)) #1 SMP 1
	[ 0.000000] Command line: BOOT_IMAGE=/gnu/store/niii7081g3w6k5rd0dbildp0kx25jfy8-linux-libre-vanilla-5.4.8/bzImage --root=my-root --system=/var/guix/profiles/system-42-link --load=/var/guix/profiles/system-42-link/boot rootflags=compress=lzo
	[ 0.000000] KERNEL supported cpus:
	[ 0.000000] Intel GenuineIntel
	[ 0.000000] AMD AuthenticAMD
	[ 0.000000] Hygon HygonGenuine
	[ 0.000000] Centaur CentaurHauls
	[ 0.000000] zhaoxin Shanghai
	[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
	[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'

geostarling / mozlz4a.py

Last active October 6, 2020 19:36 — forked from Tblue/mozlz4a.py

MozLz4a compression/decompression utility

	#!/usr/bin/env python3
	#
	# Decompressor/compressor for files in Mozilla's "mozLz4" format. Firefox uses this file format to
	# compress e. g. bookmark backups (*.jsonlz4).
	#
	# This file format is in fact just plain LZ4 data with a custom header (magic number [8 bytes] and
	# uncompressed file size [4 bytes, little endian]).
	#
	# This Python 3 script requires the LZ4 bindings for Python, see: https://pypi.python.org/pypi/lz4
	#

geostarling / mbsync-notify.sh

Created October 26, 2018 10:02 — forked from dennisse/mbsync-notify.sh

mbsync-notify.sh

	#!/usr/bin/env bash
	# This file:
	#
	# - Uses mbsync to check your email if you have a connection to the server.
	# - Slows down syncing if you're on battery
	# - Notifies you of new emails
	#
	#
	# Usage:
	#

geostarling / README.adoc

Created May 6, 2018 13:35

rust apks

TODO

geostarling / clj-callgraph.txt

Created February 1, 2018 14:33

	Rachna [12:21 AM]
	Hello everyone.
	I need to document a big clojure project which i did not create(but trying to understand it at my best). It has lots of namespaces and functions. Any suggestion which software design diagrams(UML or any thing else) should I use for the design specific documentation.
	It would be great if it can show which function is calling what. Or can show some kind of control flow.


	andy.fingerhut [12:50 AM]
	I do not have any recommendations for you, but I wanted to pile on another question -- in such a control flow graph, does anyone have good conventions for how to show that visually when functions are passed as arguments to other functions, and are then called, i.e. higher-order functions? Also for functions that return functions as return values. And of course even crazier is when you start getting into futures, promises, core.async, etc. But even ignoring those last possibilities, the earlier questions are interesting.

	alexmiller [1:04 AM]

geostarling / oauth-token.sh

Created September 7, 2016 07:35 — forked from jirutka/oauth-token.sh

	#!/bin/bash
	# vim: tabstop=4

	GRANT_TYPE='client_credentials'

	############### Functions ###############

	parse_json() {
	local input=$1
	local attr=$2