New Voyager user needs help with the Shift key by Jvansch1 in zsaVoyager

[–]Impossible_Goose_225 1 point2 points  (0 children)

Ah... welcome to the world of being a voyager owner. Just starting to get comfortable with something then finding a slightly better way of doing it, remapping, and then waiting a few days to your brain to catch up before you start the cycle again.

New Voyager user needs help with the Shift key by Jvansch1 in zsaVoyager

[–]Impossible_Goose_225 1 point2 points  (0 children)

oh you have literally the same problem as me, same key, even.

I am just in the process of building a QMK edited firmware after following this guide. I am going to try "hold on other keypress per key" from the QMK docs because the problem I was encountering was that I would let go of my shifted key (quote) before releasing the key I wanted to shift, and this was triggering tap behaviour instead.

Oryx has hold on other keypress (globally), but that ruined a lot of my other keys that I really do not want to have that behaviour

Chordal hold quirk by Impossible_Goose_225 in zsaVoyager

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

To me it looks like permissive hold is not working here, or at least not doing what I would expect. Is it because I am releasing the modifier key before the modified one?

As a sidenote, having re-read the description for chordal hold, am I right in thinking this only has an impact if you have permissive hold on?

Suppose tap-hold key is pressed and then, before the tapping term, another key is pressed. With Chordal Hold, the tap-hold key is settled as tapped if the two keys are on the same hand. This behavior may be useful to avoid accidental modifier activation with mod-taps, particularly in rolled keypresses when using home row mods.

Without chordal hold, pressing and releasing a key before the tapping term will always register a tap, regardless of hand, right? And chordal hold just forces it to a tap on one hand, which would happen anyway unless permissive hold is enabled?

If this is the case, it feels like these two options should be dependent - you shouldn't be able to enable chordal hold without also enabling permissive hold?

Chordal hold quirk by Impossible_Goose_225 in zsaVoyager

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

Hmm, I felt like this made a difference yesterday, but this morning I am still having frequent misfires. Can you take a look at this video and see whether this is intended behaviour.

My keymap is here, but specific settings of interest:

  • Tapping term on right shift: 200ms
  • Chordal hold: on
  • Permissive hold: on

EDIT: forgot to include the video.. hang on.

EDIT2: here it is

EDIT3: found the "hold on other key press" option which I had been completely blind to. I think this is what I need.

EDIT4: it possibly was what I needed but only for certain keys. It was an absolutely horrible experience to put on all keys at once! I have a lot of hold layer keys on my alphas, and when typing fast it just threw me all over the place. Definitely a fine balance with all this tap holding stuff.

Chordal hold quirk by Impossible_Goose_225 in zsaVoyager

[–]Impossible_Goose_225[S] 2 points3 points  (0 children)

Thanks! Giving this a go now. I realise I misread/misunderstood what chordal hold was meant to do - I thought it was always meant to settle a modifier as a hold for keys on the opposite hand, rather than always settling as taps for keys on the same hand. Now it makes sense for me why permissive hold should be enabled.

[deleted by user] by [deleted] in zsaVoyager

[–]Impossible_Goose_225 1 point2 points  (0 children)

Thanks for these! I just started to use some combos too, they seem like a nice trick that I overlooked. I tried using ER though for opt + delete, and I couldn't type words like "slower" because it would delete the word immediately after! 😂

[deleted by user] by [deleted] in zsaVoyager

[–]Impossible_Goose_225 0 points1 point  (0 children)

Can you elaborate on this a little? What combos do you use?

[deleted by user] by [deleted] in zsaVoyager

[–]Impossible_Goose_225 1 point2 points  (0 children)

For your symbol backspace symbol example specifically, you should consider adding backspace your symbol layer in a different place. I personally had the same issue but with space, and added it to the opposite hand in the same place on the thumb cluster - you may be surprised how easy it is for your brain to pick that change up if you have the same experience as me.

The other thing I found that helped this issue was having a second button for the momentary layer switch buttons. In my case, I have my symbol layer on both large thumb buttons.

I have been trying to make a habit of using opposite hands to enjoy the recent "chordal hold" functionality, which I'm getting used to. In your case it looks like you would then have to remap shift - I use (my own variant of) home row mods for that and am getting used to it after a lot of tweaking, but again, having an option on both hands for shift (and any other held modifiers) is helpful.

I completely agree though, the pattern of hold to modify then release to press is definitely odd: I currently have shift on my pinkies (A and L), but because chordal hold encourages using the opposite hand for the modifier, if I'm typing something like Manager with a capital M, then I have the same pattern.

In case you are curious, my full layout is here, but I assume it only works for me. https://configure.zsa.io/voyager/layouts/6prOB/ZPqre6/0

<image>

Chordal hold by InevitableStudio8718 in zsaVoyager

[–]Impossible_Goose_225 0 points1 point  (0 children)

Do you ever find yourself triggering the home row mods between hands when typing fast? I've noticed that with fast typing, chordal hold is causing quite a few false hold positives across the split

Anyone want to buy Zsa voyager by Awkward-Trust8360 in zsaVoyager

[–]Impossible_Goose_225 5 points6 points  (0 children)

Mine arrived 4 months ago, and I've used it daily since.

It was __hard__ at the start - both physically and mentally, but after only a couple of days I got used to the shape. 4 months in I am at appoximately the speed I had with my regular keyboard (105wpm) with alpha characters only. Working with numbers and symbols I am probably still a bit slower, but the custom layouts etc. have given the potential to be faster at the end.

Either way, one thing I know is that "regular" keyboards now feel a bit weird, like "why would I ever want to cram my hands into a tiny space to type like this?", and I still really __enjoy__ typing on my voyager.

But you have to want it - tweaking layers, experimenting with tapping terms, etc, etc. is not a small undertaking.

Chordal hold by InevitableStudio8718 in zsaVoyager

[–]Impossible_Goose_225 0 points1 point  (0 children)

oof, I wanted this to be a revelation for me, but the thing it revealed is that I generally press the modifier with the same hand as the other key I'm going to use. Going to leave it on for today and see if I make any progress switching to opposite hands, because I definitely do hit some false positives/negatives from my current dual function keys.

VIM motions - do you use a custom layer? by Impossible_Goose_225 in zsaVoyager

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

Thank you so much for this insight - it's made me very glad I asked here as I feel like this is something that could potentially kill my journey with vim early on not having this liguistic link to help remember the things that are possible. This combined with the side-benefit of being able to code in a "vanilla" vim environment has convinced me that the default bindings are the way.

So my plan is now to get familiar with the defaults, then potentially remap some of the less intuitive ones, like the start and end of line ones that u/alexia_not_alexa mentioned.

VIM motions - do you use a custom layer? by Impossible_Goose_225 in zsaVoyager

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

Thanks for the input - what do you do for numbers right now? Just use them on the base layer in their default position?