@bryansmart [mstdn.social] @simon I don't github. Could someone please flag this? It's just bad UX.
@FreakyFwoof @bryansmart@mstdn.social If someone at @NVAccess wants to do this before I get done with work, feel free. otherwise, I will.
@tspivey @FreakyFwoof @bryansmart@mstdn.social @NVAccess Why amI not surprised this is ancient?
@simon @tspivey @FreakyFwoof From the issue: I can see no point in setting up people with CAPS LOCK by default when that changes the behavior of the CAPS LOCK key when using it for its native purpose. That's just asking for unnecessary confusion, whether Narrator does it or not.
lol but the insert key is fine? That one also has a native purpose, you know. Also capslock is one of my least used keys for its intended purpose. In fact, every single time, and I do mean literally every single one as far back as my memory goes, turning capslock on was a mistake, and not something I actually wanted. Am I alone here? I always use laptop layout. Always. Even on desktop keyboards. I don't even have to think about it at all, it should be on by default.
You have two options. Option one only works on some keyboards, option 2 works on all keyboards. Which one do you pick? I know which one I'm picking.
@talon @simon @FreakyFwoof I never want caps lock to turn on. I use an addon to block it from turning on, but it still can turn itself on if the keyboard hook lags, and I don't notice for a while until my next command fails. There's no API to turn it off, so you just have to send the key again, I just haven't patched the addon to do it.
@tspivey @talon @simon @FreakyFwoof Yep, I can't tell you how many times I've typed stuff in terminals only for it to totally not work... but wait, how does this system not have ls?
Oh, it's LS. That again.
@BorrisInABox @tspivey @talon @simon @FreakyFwoof I have that problem all the damn time and man its annoying. It usually happens when I type long commands, because of course.
@BorrisInABox @tspivey @talon @simon I don't want it on either. Sometimes my keyboard misfires and turns it on, and I don't realise for a while. This is particularly noticeable in virtual machines.
@FreakyFwoof @BorrisInABox @talon @simon There's this: https://github.com/TheQuinbox/capblocker if it turns on, just pass it through and it'll turn off again.
@tspivey @FreakyFwoof @talon @simon That's what I've been using for a while. Damn useful. Too bad other things outside of NVDA's control turns on caps lock when it lags, but it is at least less annoying now.
@BorrisInABox @FreakyFwoof @talon @simon I think I can fix that, either I fix the addon so it checks caps lock status on every key, or use SharpKeys to remap caps lock to one of the extra keys that keyboards don't usually have, then tell NVDA it's the new modifier.
@tspivey @BorrisInABox @talon @simon Doing that really makes the remote addon go crazy. If you use a different modifier for one system, then speech never interrupts. It's not a fun time.
@FreakyFwoof @BorrisInABox @talon @simon Didn't think of that. NVDA on the other end of the remote session wouldn't know what to do with that key unless it had the same mapping, or unless the remote on the local system remapped it back before sending it.
@tspivey @BorrisInABox @talon @simon Didn't know about this, thanks.
@FreakyFwoof @BorrisInABox @tspivey @talon @simon One of the weirder consequences is that when using a Matias bluetooth keyboard, when connecting to another device, it likes to blink the caps lock on the chosen device. It apparently does this by quickly hitting caps lock twice, thus turning it on then immediately off again. Except that if NVDA is running, the first press of caps lock is absorbed by NVDA and the second one turns it *on*.
@jaybird110127 @FreakyFwoof @tspivey @talon @simon That was one of the main reasons I stopped using that keyboard. You can't turn this off, and it got really annoying really fast.
However, the addon mentioned in this thread should take care of that.
@simon @FreakyFwoof @bryansmart@mstdn.social @NVAccess You could report a bug. The welcome dialog doesn't appear when resetting your config, and you can't easily revert without an insert key. That would help resolve this specific issue.
@simon If that's ancient, how would you classify this? https://github.com/nvaccess/nvda/issues/374 @tspivey @FreakyFwoof @bryansmart@mstdn.social @NVAccess
@simon I think the fact it's been open for 14 years without someone correcting the spelling of "link" in the title sums it up. @tspivey @FreakyFwoof @bryansmart@mstdn.social @NVAccess
@simon One more, for luck. From a comment left in May 2008:
> This is not particularly important, so can be done after 0.6.
Yeah... still open, and I find this one particularly annoying. https://github.com/nvaccess/nvda/issues/49 @tspivey @FreakyFwoof @bryansmart@mstdn.social @NVAccess
@jscholes @simon @tspivey @bryansmart [mstdn.social] @NVAccess If you go with K and shift K it announces after, if you arrow, it announces before. How odd.
@jscholes @simon @tspivey @bryansmart [mstdn.social] @NVAccess This page for example, demonstrates this quite well. https://www.tunestotube.com/
@jscholes @tspivey @FreakyFwoof @bryansmart@mstdn.social @NVAccess Ok, you win.
@simon And yet... we still all lose. @tspivey @FreakyFwoof @bryansmart@mstdn.social @NVAccess
@jscholes @simon @tspivey @FreakyFwoof @bryansmart@mstdn.social @NVAccess How's this one? https://github.com/nvaccess/nvda/issues/46
@jscholes @simon @tspivey @bryansmart [mstdn.social] @NVAccess AS this is a thread with enough clever people in it, maybe one of you can answer me this.
Many, many times I'll be reading by character, hit the end of a line and the start of the next line looks like it's part of the previous.
Copying a code out of an email just now in Thunderbird as an example, I hit the letter 'I' which is just the word 'I' on the next line down, but there's no end of line announcement, no space, nothing. It looked like it could well have been part of the previous line. Is this a setting I broke or is this an actual thing? I see it a lot in virtual cursor applications.
@FreakyFwoof NVDA applies soft wrapping to the browse mode buffer. A sighted reader may see 80 characters on a line because of the styling, while an NVDA user might be able to read 125 because that's more efficient. You can control the "Maximum number of characters on one line" setting in the browse mode options. In some cases, the text does legitimately flow to a new line, but via HTML and/or CSS semantics and styling rather than a line break, which are used very rarely in web development. @simon @tspivey @bryansmart@mstdn.social @NVAccess
@FreakyFwoof @jscholes @simon @bryansmart@mstdn.social @NVAccess IF you have two paragraphs, NVDA won't give you any indication that you're moving from one to the other when moving by character.
@jscholes @simon @tspivey @FreakyFwoof @bryansmart [mstdn.social] We could just close stale issues like many projects do, if you'd prefer? It's old, but the fact it is still open does at least accurately reflect the status of it. If you are passionate about that issue, you are of course welcome to submit a PR for it (I'm not trying to be snarky in saying that). Also, new information commented on issues always helps. Please do ensure any valuable information from this thread makes it to the issue, for instance
@jscholes oh funny you bring up that bug, because it's one that still impacts me at work with links and NVDA and where I need to explain to engineers that in fact it's a screen reader specific quirk and not all of them will treat their link the same way. Yeah, very fun when little SR issues get to make it into daily work life too. @simon @tspivey @FreakyFwoof @bryansmart [mstdn.social] @NVAccess