West Michigan, USA
We start, around the turn of the millenium, with a dot on the map: a small city where tickets to the local cinema cost only two dollars. Just outside city limits sat a parsonage, inwhich memorable history was being formed:
"That's so easy, even Zach can read it!" called one of the others.
Now, others there were, in contrast to the big people, who, here, seemed to run the joint by joint-ownership.
I was beckoned toward a newspaper, where a three-panel cartoon was being indicated.
"Here, read this!"
My first test of skill... would I succeed, proving my capability, or fail, showing the known universe that I was most inferior.
Panel 1: Garfield sits on the counter, saying "Zzzzzzzz" Panel 2: Garfield is still sitting on the counter, Jon is watching. Garfield says "Zzzzzzzz" Panel 3: Jon breaks the pattern of Zee's, and says ________...
I couldn't do it. I was the only person who didn't know how to read.
From Zach DeCook to ~mil/sxmo-devel
On Thu Jan 26, 2023 at 12:35 PM EST, Peter John Hartman wrote: > If in screenoff, we will have a static red (if no notificaitons) > or a static red+green (if notifications). > --- I still use a static red to indicate the device is suspended (with two overridden hooks). What would you recommend for those who wish to distinguish suspend from shutdown and powered off?
From Zach DeCook to ~mil/sxmo-devel
On Saturday December 17, 2022 at 5:11 AM EST, Stacy Harper wrote: > > Mhh I think we prefer an empty output if there is no focused window no ? I originally tried that to detect the empty desktop, but some applications have windows which give an empty name. (I've configured oneleft, oneright, oneup, onedown to open apps when on the desktop, so if it fires while another application is running, that's annoying). Ideally, this just works the way it used to (so we can distinguish between un-named windows and the desktop, **and** XWayland works)
From Zach DeCook to ~earboxer/public-inbox
On Sat Dec 10, 2022 at 4:07 PM EST, wrote: > Big Gaps in knowledge...: > > One is web hosting/web server and everything that generally goes in this > direction. Nginx and Apache I have never touched, but the OpenBSD Httpd, > despite only rudimentary. Hard to give advice on where to start. I originally learned apache on ubuntu (at work), and when I got into self hosting, started learning nginx. Now, I use alpine linux for most of my servers. I've done cloud-hosting (first digital ocean, now linode), but also have done some hosting on various raspberry pis (not too convenient as I've moved recently).
From Zach DeCook to ~mil/sxmo-devel
--- Fixes a recent bug scripts/core/sxmo_wm.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/core/sxmo_wm.sh b/scripts/core/sxmo_wm.sh index 8fae90d..90bff68 100755 --- a/scripts/core/sxmo_wm.sh +++ b/scripts/core/sxmo_wm.sh @@ -117,7 +117,7 @@ swayfocusedwindow() { FOCUS="$( printf %s "$TREE" | jq -r ' recurse(.nodes[]) | select((.focused == true) and (.app_id != null)) | [message trimmed]
From Zach DeCook to ~earboxer/swipeKeyboard
On Thu Dec 1, 2022 at 6:05 PM EST, Eloi Torrents wrote: > Hi again, > > I just fixed this: > https://codeberg.org/PhoneInput/swipeGuess/src/commit/4fa7f9631d5003fca551c2f6ad6e7bc3b3aad8df/completelyTypeWord.sh > - POSIX complaint. > - Now it works with capitalized words in the word list. > - It adds a space after each word. > > I will try to make it work with diacritics too, but this will take > me some time. > Awesome!
From Zach DeCook to ~mil/sxmo-devel
On Monday November 7, 2022 at 7:55 PM EST, Aren wrote: > I would prefer to remove the alises entirely, this seems to perform very > poorly. On my system it takes about 20-30ms to run, which could add up > quickly if a few sxmo scripts get chained together. > > As a real example, I did some rough benchmarking of the context menu, > and found that it took about 60ms to 100ms longer to run with it. > (disclaimer I'm using bash because busybox breaks things on arch) > > without this patch: > sxmo_hook_contextmenu.sh sys 265ms > sxmo_hook_contextmenu.sh sys (with ash) 220ms > sxmo_hook_contextmenu.sh (with foot focused) 215ms >
From Zach DeCook to ~mil/sxmo-devel
--- scripts/core/sxmo_audio.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/core/sxmo_audio.sh b/scripts/core/sxmo_audio.sh index b4ef235..ca22ca1 100644 --- a/scripts/core/sxmo_audio.sh +++ b/scripts/core/sxmo_audio.sh @@ -61,7 +61,7 @@ pulsevolget() { } pulsevolset() { pact set-sink-volume @DEFAULT_SINK@ "$1"% pactl set-sink-volume @DEFAULT_SINK@ "$1"% [message trimmed]
From Zach DeCook to ~mil/sxmo-devel
On Thu Nov 3, 2022 at 3:05 PM EDT, Maarten van Gompel wrote: > Looks good to me, but I do wonder if the fairly complicated > colour conversion function is worth it, as opposed to just initialising > SPAN_RED and all the other vars with some fixed ANSI sequences if -a is set? > You *have* to have a conversion function in order to display both the ansi and pango versions at the same time because statusbar stuff is stored as files. That wasn't much of a problem with the dwm/sway distintion because 'toggle wm' is pretty rare, and triggers a full rebuild of the statusbar info anyway, but with this patch, you can always run `sxmo_status -a` from the terminal no matter if you're in dwm or sway.
From Zach DeCook to ~mil/sxmo-devel
On Monday October 31, 2022 at 5:17 AM EDT, Stacy Harper wrote: > I dont understand this change. Please submit more details if you think > this is really a mistake. I mark this as rejected for now. Yeah, so when I made the proximity lock event-driven, I implemented it like a themostat: When your face is very near the sensor (large values over 100), then it locks the screen, when your face is very far from the sensor (small values under 50), then it unlocks the screen. There's meant to be a soft area where no change happens (between 50 and 100) (it's not sure if you're about to pull it away from your face, or keep it near your face.) The current behavior misbehaves on prox-startup: it will turn the screen off when your face is in that 'middle-area'.
From Zach DeCook to ~mil/sxmo-devel
--- .../three_button_touchscreen/sxmo_hook_proximitylock.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configs/default_hooks/three_button_touchscreen/sxmo_hook_proximitylock.sh b/configs/default_hooks/three_button_touchscreen/sxmo_hook_proximitylock.sh index b206f0c..49b047f 100755 --- a/configs/default_hooks/three_button_touchscreen/sxmo_hook_proximitylock.sh +++ b/configs/default_hooks/three_button_touchscreen/sxmo_hook_proximitylock.sh @@ -54,9 +54,9 @@ awk ' AWKPID=$! initial_distance="$(cat "$prox_raw_bus")" if [ "$initial_distance" -gt 50 ] && [ "$INITIALSTATE" != "screenoff" ]; then if [ "$initial_distance" -gt "${SXMO_PROX_RISING:-100}" ] && [ "$INITIALSTATE" != "screenoff" ]; then [message trimmed]