Klaus Buecher

@[ThomasHeinrichSchmidt](https://github.com/ThomasHeinrichSchmidt) > It seems that changes in keystroke detection (perhaps in N++ or in TB or both) also have an impact on several other issues, like #121 #122, #127, #130...

just tried this: f works, b is taken by my TB, so obviously does not work

in https://github.com/opto/nostalgy-xpi/releases/tag/v3.2.22

TB team (John) helped to optimise startup, I am interested whether this solves the problems. https://github.com/opto/nostalgy-xpi/releases/tag/v3.3.17 Klaus

I can confirm this and will have a look. You can try 3.0.8 solving another bug but not this one yet

workaround: select a letter you do not use anywhere. Set all keys that need to be disabled to that letter. So you 'free' the original letter. At the moment, the...

yes, I will make it an option. As a workaround until then, there is a regex for 'space' (maybe \c, I forgot). Maybe you can google for regex space and...

Here, it puts this view into a new tab. Probably, some code functions are not available there. This might be a starting point to solve thhis sometime.

it is working fine on win 11. What OS are you on? Please give better description of the problems if they are not yet in other issues. I know of...

for move > 100 messages and mouse up bounce for mouse gesturees, please try: https://github.com/opto/nostalgy-xpi/releases/tag/v3.2.18