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
Hyprland recently added a layerrule to allow certain layers to appear on the lockscreen, but layers only identify themselves by the namespace. --- main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/main.c b/main.c index 62c7297..7460b4f 100644 --- a/main.c +++ b/main.c @@ -28,7 +28,7 @@ #define countof(x) (sizeof(x) / sizeof(*x)) /* client state */ [message trimmed]
From Zach DeCook to ~mil/sxmo-devel
jk, this patch is bad On Sat Jan 18, 2025 at 3:38 PM EST, Zach DeCook wrote: > --- > main.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/main.c b/main.c > index 5ec1c45..00e6fa9 100644 > --- a/main.c > +++ b/main.c > @@ -133,6 +133,7 @@ static void layer_surface_closed(void *data, > struct zwlr_layer_surface_v1 *surface); > static void flip_landscape(); > static void show();
From Zach DeCook to ~mil/sxmo-devel
--- main.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/main.c b/main.c index 5ec1c45..00e6fa9 100644 --- a/main.c +++ b/main.c @@ -133,6 +133,7 @@ static void layer_surface_closed(void *data, struct zwlr_layer_surface_v1 *surface); static void flip_landscape(); static void show(); static void hide(); [message trimmed]
From Zach DeCook to ~earboxer/swipeKeyboard
On Fri Oct 11, 2024 at 6:48 AM EDT, Guido Günther wrote: > Hi, > I didn't spot list address to send swipeGuess patches to. I have two > small ones attached, let me know if they should go somewhere else. > Cheers, > -- Guido Thanks! I've pushed your patches, as well as some documentation for future contributors to find the mailing list: https://lists.sr.ht/~earboxer/swipeKeyboard I'm thinking about adding a section for setting this up, but haven't gotten it working. I think this would be right, but I haven't yet gotten it working in version 0.42.0 (should it work on gedit v48.0?)
From Zach DeCook to ~earboxer/HexBoard
On Tue Apr 2, 2024 at 6:46 PM EDT, Nicholas Fox wrote:
> I consent to license my hexperiment code under the GPLv3
Thank you!
I tried it out and it seems to work pretty well (though I haven't tested any of the MIDI stuff yet).
(I like how the encoder can turn multiple steps at once... though we might want to do some frame-skipping so the screen can keep up with it)
From Zach DeCook to ~earboxer/HexBoard
Thanks! I pushed this code to the hexperiment branch https://git.sr.ht/~earboxer/HexBoard/tree/hexperiment (had to fix some issues from the email -- some lines were breaking early, and there were some apostrophes where they shouldn't be... maybe sending it as an attachment instead of as the body would work better next time) It's compiled at https://builds.sr.ht/~earboxer/job/1185290 I haven't tested it (my production hexboard is currently tied up working as a QMK keyboard on a computer with almost dayly use) @Nicholas, if you want to say "I consent to license my hexperiment code under the GPLv3" (or some more permissive license), (it's required by the Rotary library for the binary to be under that license). Otherwise, the binary compiled at the link above could be illegal ;)
From Zach DeCook to ~earboxer/HexBoard
On Sat Feb 17, 2024 at 11:13 AM EST, Lewis McRae wrote: > > 'tuning to a color' is currently complicated > > Oh okay, what do you mean by that as opposed to the current alternate > colour mode? Or is it just that making it work with keys and > transposition is complicated? Yeah, I meant 'making it work with keys'. > I also like Nick's idea of using MIDI > note 69 = A4 as a constant for note mapping, as it seems like that's > the default for retuning in some software. I didn't know about the 69 = A4 thing. (currently, I made the microtonal thing include 440 somewhere, and have 0 ~= C, so that 'red' = C in the default coloring).
From Zach DeCook to ~earboxer/HexBoard
On Thu Feb 22, 2024 at 9:56 AM EST, Nicholas Fox wrote: > Hi Zach, > > Can you confirm if this is the correct ModelNumber 2 layout? > // > 1 2 3 4 5 6 7 8 9 > 10 11 12 13 14 15 16 17 18 19 > 21 ......................................... 29 > 30 ............................................... 39 > 41 ......................................... 49 > 50 ............................................... 59 > 0 61 ......................................... 69 > 20 70 ............................................... 79 > 40 81 ......................................... 89
From Zach DeCook to ~martijnbraam/public-inbox
--- createaport/aport.py | 13 ++++++++++--- createaport/license.py | 20 +++++++++++++++++++- 2 files changed, 29 insertions(+), 4 deletions(-) diff --git a/createaport/aport.py b/createaport/aport.py index c69e4be..175fa6e 100644 --- a/createaport/aport.py +++ b/createaport/aport.py @@ -1,3 +1,4 @@ from createaport.license import needs_license_file class Aport: def __init__(self): self.pkgname = None [message trimmed]
From Zach DeCook to ~earboxer/HexBoard
On Thu Feb 15, 2024 at 1:51 AM EST, Lewis McRae wrote: > Hey Zach, Lewis here. I made those mockups of the 41edo key mappings Thank you! It's one thing when Jared says 'people want X' vs actual pictures of what it looks like. > My original idea was mainly that there could be some way for people to > easily set up their own key colours alongside new note layouts, since > note layouts can be added pretty easily by editing the firmware. My > thinking was that you could do it by defining a set of colours and > either mapping each key on the board to a colour, or mapping each note > in a particular tuning to a colour. I figure it's possible that > someone might want to try different note colours for the same tuning Additional color modes can be added in the keyColor function like so https://git.sr.ht/~earboxer/HexBoard/commit/bdcd88f14f17a83bfbcc6c32fd0c3d54dc29ff3d