neeasade

from the readme:

> it maps possible futures, and shows you which key(s) you will need to press before you actually need to do that.

In the preview gif it's showing the matched hintkeys LIVE as you search.

I think this is actually a huge different in UX. I'm using the emacs equivalent in avy, avy-goto-char-timer[1], and that small pause between searching and acting (typing the hints) makes the experience jarring enough that I don't want end up using goto-char-timer in motions that much (only for jumping across windows and panes)

With no delay between <leap key> and <hint key>, the UX of d<leap key><hint key> is much smoother

[1] https://github.com/abo-abo/avy#avy-goto-char-timer

obligatory vanity link: http://noriceno.life

It helped re-instill my faith in creative computing and reminded me that on the other side of the text there are people on keyboards doing the thing. I spent most of my time there messing with emacs (shoutout Eric+Zach @ emacs-nyc!), collaborating, and giving small talks on things like mpd and colemak -- you really are encouraged to share whatever you want (I remember someone's tutorial about home cultivated yogurt that was really cool).

My time there helped set the "hacker spirit" tone of my sabbatical (which I took with a goal of pivoting to being a hired clojure programmer), and drove me to write and share much more, one post of which even ended up here![1]

There is a lot of communication that comes for "free" with the physical space -- I was much more active in the zulip chat after my RC batch than I ever was during my time there. They have done a good job mimicking the physical experience in a virtual setting now though, and have iterated nicely on what makes a virtual experience different than the physical.

If you're curious about attending and can take the time, would recommend! (there's no cost): https://www.recurse.com/apply

[1] https://notes.neeasade.net/color-spaces.html

It's very comfy. The client is close to the shell, and you can have both automatic and manual tiling modes. When there is some feature you like that the author did not account for, you can query the state of the world in json and make decisions based on that.

A comment here mentions herbstluftwm, which came before BSPWM and I would even call a sister WM -- Baskerville even announced BSPWM on the Herbstluftwm mailing list when it was initially released[2]. I would say BSPWM has less to think about than in the other window manager (everything is a node vs climbing frames with nested layouts). It can be thought of as a kit for building what you want, even. For instance, I use a tag-based workflow[3], where I toggle the hidden flag of nodes, and keep only one desktop.

WRT the windows being kept as nodes in a binary tree, this is useful because you can then climb the tree and perform balances and rotations within a subselection of the whole thing. You can also use the tree datastructure to enforce layout, like here[1], a DWM-like stacking layout.

With monocle mode, you can add fake padding for fullscreen windows, allowing you to have comfy fullscreen stuff that still accounts for a panel presence. With an external rules script, you can make decisions about what to do with windows as they appear, allowing dynamic layouts and decision making.

I'm sure at the end of the day, you can get what you need with any window manager if you drill far enough (year of the linux desktop is here, if you are willing to read the source). BSPWM has been a nice base for flexible workflow types for me. I will also share screenshots I've taken over the years here: https://notes.neeasade.net/rice.html (all bspwm past mid 2014).

[1] https://old.reddit.com/r/bspwm/comments/euq5r7/a_dwmlike_sta...

[2] https://herbstluftwm.org/archive/msg00052.html

[3] https://github.com/neeasade/dotfiles/blob/master/bin/bin/bta...

It's awesome because I use it for things I want to reference later.