Cli

For my ally is the Force, and a powerful ally it is.

Abstract

ThyForce is a long running personal software generation and maintenance infrastructure geared towards assimilating engineering acumen in an accelerated manner.

I’m going for a healthy mix of being pragmatic and principled when exploring and integrating different engineering paradigms and patterns into this code base.

The seeding incentives of the current repository structure (polylith and tech stack choices (hy, python)) are (inexhaustive list):

Fabric¹ is a collection of crowd-sourced prompts, exposed via a CLI tool. I used it for a while some time ago but never fully exploited it because I prefer Emacs.

Eshell buffers are an option, but I am principled in my tool usage and prefer to delegate longer-running CLI tasks to a combination of Alacritty and Tmux.

Maintaining my Emacs shell usage to ephemeral popups feels natural.

Gptel² is a versatile LLM client that integrates smoothly into my workflow (buffer/text manipulation and management) without disrupting my thought flow.

This is how I time my workblocks these days…

Prerequisites

• ALSA : https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture

Functions

single_beep() {
( \speaker-test --frequency $1 --test sine )&
pid=$!
\sleep  0.${2}s
\kill -9 $pid
}

morse(){
for i in {1..3};
do
        single_beep 400 $1
        \sleep 0.${2}s
done
}

sos() {
    morse 200 500
    morse 400 500
    morse 200 500
}

timer() {
    \sleep $1 && sos &
}

Usage

The above can be sourced in your shell rc.
I store it in a .bash_funcs where I have all my functions and source them in the end of my rc as source ~/.bash_funcs.