> On Tue, 7 Jul 2020 at 22:14, N <nicklas.karlsso...@gmail.com> wrote: > > > I do not consider it a big problem and will probably connect other jogging > > method once machine is up and running but as it worked in old version it > > would of course be good to get it perfect again. > > https://github.com/LinuxCNC/linuxcnc/commit/29f52a6e2be42f7785e965a7002eaecf33f0b7aa#diff-5368256524ea7313310fa9c396bbbcf2 > > Might have made a problem with a bouncy keyboard more obvious? > > Try reverting to e09ae64fb0a76355b4f559e28c91a29fb25af8ce and seeing > if the behaviour changes. > > Is sounds like an easy problem to find, so a git bisect will probably > work well (if i am allowed to mention git on the Users list)
It seems I was wrong about old version, acceleration was so slow I never heard it but then checking with halscope there is a small spike downwards. Maybe there is no method to distinguish between auto repeat and key up except using "xset -r" that turn off auto repeat globally? Will probably leave this problem as is and not think about it more. For real machine I will probably connect something else anyway and there is the possibility to turn off with "xset -r" if needed Nicklas Karlsson _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
