Jonathan Fuerth jfuerth

Screen Resolution

Main gripe: at 100% scale, everything is too tiny; at 200%, everything is too big

You can enable advanced features and then select 125% scaling. Good size, but everything is blurry
My compromise: leave it at native resolution, and set Chrome and IDEA to scale their UI to 125%
- not ideal, because most apps still appear too small
There are reports that native Wayland apps can scale cleanly, but it's an uphill battle to ensure nothing is going through the X11 compatibility layer

Sleep/Suspend/Hibernate

	private boolean matchesAnyGlob(String value, Collection<String> globs) {
	// convert globs to regex
	StringBuilder sb = new StringBuilder();
	sb.append("(");
	for (String glob : globs) {
	if (sb.length() > 1) {
	sb.append("\|");
	}
	String[] parts = glob.splitWithDelimiters("[*?]", 0);
	for (int i = 0; i < parts.length; i++) {

	{
	"$id": "https://drs-concepts.example.com/drs-concepts.schema.json",
	"$schema": "https://json-schema.org/draft/2020-12/schema",
	"anyOf": [
	{ "$ref": "#/$defs/url" },
	{ "$ref": "#/$defs/curie" },
	],
	"$defs": {
	"url": {
	"title": "DrsObject URL",

	FROM alpine:3.15

	RUN echo "This Docker image exists so you can run the prebuilt memory calculator on MacOS and Windows.\n\
	There is no sense in using it on a Linux system.\n\
	You can find the Dockerfile at https://gist.github.com/jfuerth/f002f3dde9b54e5be67b43f0a85d59d7" \
	> /etc/motd

	# Grab the pre-compiled release binary
	RUN wget -O - https://github.com/cloudfoundry/java-buildpack-memory-calculator/releases/download/v4.1.0/memory-calculator-4.1.0.tgz \
	\| tar zxv

	openapi: "3.0.2"
	paths:
	/table/{tableName}:
	get:
	responses:
	'200':
	content:
	application/json:
	schema:
	$ref: "#/components/schemas/Table"

	// egl_bar.c - self-contained example of a vertical bar moving across the screen.
	// compile with gcc -Wall -O0 -g -o egl_bar egl_bar.c log.c -lX11 -lEGL -lGLESv2 -lm
	#include <stdio.h>
	#include <math.h>
	#include <malloc.h>
	#include <stdlib.h>
	#include <string.h>
	#include <sys/types.h>
	#include <sys/stat.h>
	#include <fcntl.h>

	# Sets up Xorg on Raspberry Pi 3b in FKMS mode for two screens.
	#
	# To put the Pi into FKMS mode, add one of the following lines to /boot/config.txt:
	# 1. "fake" KMS mode (exposes the proprietary vc4 firmware driver via KMS API):
	# dtoverlay=vc4-fkms-v3d
	# If you wanted "full" KMS mode, fully open source "vc4" driver in the Linux kernel, you
	# would use `dtoverlay=vc4-kms-v3d` instead, but then the identifiers in the Driver section
	# need to be different.
	#
	# To run X clients on one screen or another:

	if (!console.olog) { // eslint-disable-line no-console
	const escapeHtml = str => `${str}`.replace('&', '&').replace('<', '<');
	console.olog = console.log; // eslint-disable-line no-console
	console.log = (msg, ...args) => { // eslint-disable-line no-console
	console.olog(msg, ...args); // eslint-disable-line no-console
	document.getElementById('debugDiv').innerHTML += `<p>${escapeHtml(msg)} ${escapeHtml(args)}</p>`;
	};
	console.debug = console.log; // eslint-disable-line no-console
	console.info = console.log; // eslint-disable-line no-console
	console.warn = console.log; // eslint-disable-line no-console

	private static class TraceLogger implements okhttp3.logging.HttpLoggingInterceptor.Logger {

	/*
	.client(new OkHttpClient(new okhttp3.OkHttpClient.Builder()
	.addInterceptor(new okhttp3.logging.HttpLoggingInterceptor(
	new TraceLogger(LoggerFactory.getLogger(FEIGN_TARGET)))
	.setLevel(HttpLoggingInterceptor.Level.BODY))
	.build()))

	*/