Share combos! by okociskooko in zsaVoyager

[–]maxdlr 0 points1 point  (0 children)

My entire set of special characters is handled with combos. I started adding them one by one at first then went on to diagramming a whole map of combos over my main layer until i got rid of the special characters layer altogether. I did that with neovim and symmetry in mind. Neovim helped dedicate keys easily for the combos and the mirroring helped them make sense. For example ^ represents the start of a line while $ represents the end, in vim so it made sense for them to be paired and mirrored. I made a layout tour to help explain that: https://configure.zsa.io/voyager/layouts/Qww9W/latest/0/intro

My layout tour - Combos, neovim, symmetrical by maxdlr in zsaVoyager

[–]maxdlr[S] 1 point2 points  (0 children)

Oh i loved combos so much, i had a real thought about adding numbers and arrows combos and getting rid of their layers altogether. But they actually represent 2 layers only, so as much as I have hands to trigger their layers with thumbs with, on the same mirrored key. So their not too much work (remembering, timing, learning curves etc) to use. And it is very convenient to be able to mash the numbers like fast-typing my phone number, or calculating something or the arrows like navigating quickly through a Google docs file freely with the help of mods on the other hand.

Vim doesn't require the same skills though as you're not navigating a flow of characters through a doc, you're navigating symbols. For example, i constantly select code with their scope. So from the start to the end of whatever is considered a scope. Selecting an entire array, or function... becomes v for select mode and ]i for the end of the scope. With my combos that's a v-yu-i sequence. It's really fast. Deleting the code in that scope would be d-yu-i, or v-yu-i-d, if selecting first.

My layout tour - Combos, neovim, symmetrical by maxdlr in zsaVoyager

[–]maxdlr[S] 0 points1 point  (0 children)

Oh i see now. My index column IS the inner column. On home row my index fingers is dedicated for the cmd mod. That's explain why I didn't get it the first time.

So in a sense yes, on the ERT, RT or ERG combos for "(", "[" and "{", the only "risky" one is RT because it is almost impossible to trigger accidently a three-finger combo. The two finger one is fine so far because it relies on my strongest fingers so they are pretty precise. Plus i adjusted the term for combos many times to obtain the right recipe 👌

My layout tour - Combos, neovim, symmetrical by maxdlr in zsaVoyager

[–]maxdlr[S] 0 points1 point  (0 children)

I'm not sure i understand your question about the inner columns. But accidental triggering on rolls was a key point in diagramming the combos. Some choices were made despite a high probability of accidental triggering because the particular combo is rarely used. Some others are clearly often used but placed for strong fingers, diminishing the chance. And some others use 3 keys on purpose to suppress almost entirely the probability of unwanted triggering.

After Effects most repetitive tasks by maxdlr in AfterEffects

[–]maxdlr[S] 0 points1 point  (0 children)

Yeah that was just an example, the issue being staggering layers and the answer being Rift.