![]() ![]() ![]() ![]() which seems to be mapped to Ctrl+^ (Set Mark) in Nano. Then, caffeine.exe -key:07 was received on the other side as ^[[28~. I used caffeine.exe -key:07 for years before having to deal with a pfsense 2.3.3-RELEASE-p1 (based on FreeBSD 10.3-RELEASE). I would recommend avoiding that if you can. Note: Once it gets to step 4., it becomes very difficult to precisely control the different layers of 'translations'/'mappings'. This pipeline can get even longer by adding the screen program (which includes a $TERM=screen for step 5.bash or readline (not sure which one) sends the translated Key Code to nano (my text editor).bash does some translations/mappings based on ~/.bashrc (based on the builtin bind command).the readline library does some translations/mappings based on ~/.inputrc.On the remote host, the 'terminal' program (e.g: $TERM=xterm, vt100, vt102, vt220, etc.) translates from the 'line protocol' into key codes.Putty sends the 'translated'/'mapped' key code to the remote host.Putty does some 'translations'/'mappings' based on some session settings in:.Windows sends that Virtual-Key Code to Putty.Caffeine sends a Virtual-Key Code to Windows.The keystroke 'pipeline', as I understand it: Launch read program on the remote host and watch how keystrokes are received every 5 or 50 seconds.In order to easily test the above, exit Caffeine & re-launch it with 5 seconds interval and Virtual-Key Code 07: readline/bash translated version of it (from '"\e[28~"' to '""' (blank key ?) caused the remote session interaction to hang for several seconds.Which I would normally want, but only when I (the human) is pressing the key but not regularly by caffeine :) it triggered a 'Reset scrollbar on keypress' (setting on.The side-effect of that (on my config) was that, with each keystroke that putty forwarded from caffeine to the remote host: Shreyansp proposed a solution where a fix would be applied between steps 5 and 10 (see below). Launch read program on the remote host and watch how no keystrokes are received every 5 or 50 seconds.TL DR: My solution is applied between steps 2 and 3 (see below) with the -key:0E caffeine param:Ĭaffeine.exe 5 -key:0E (for easy testing)Ĭaffeine.exe 50 -key:0E (for a mandatory screen saver set at 1 minute) either is not sent to Putty or is ignored by Putty.does not otherwise generate any side-effects on Windows neither alone nor in combination (no Ctrl, Shift, Alt, Alt-Gr, Win, F1-F5, F10, etc.).prevents Windows from going to sleep or idle.caffeine sends to Windows an appropriate Virtual-Key Code which:.Hope this may be of use to those looking for a solution :) Here's my attempt on improving that (of course YMMV). I found shreyansp's solution to be the most (but not quite) satisfactory one :) My question is this: Has anyone else experienced this sort of behavior in PuTTY? And if so, what can be done to prevent/correct this behavior? ![]() If left for long enough, it will spit tildes at random intervals (average is about 1 minute).įinally, this behavior seems to be inconsistant when running programs such as nano or the mysql interface: in nano, instead of inserting tildes, it will set marks (ctrl-^) in mysql, lines will become un-editable. It will only occur when I am focused on the window, whether I am typing or 20 feet away from the keyboard. Most of the time it is just a single tilde, but rarely it spits out what looks like some escape sequence ([[^8 or the like). However, there is one thing that has always irked me when using it: for seemingly no reason random characters are sometimes inserted at the cursor. I found that a relatively painless way to access it on a windows machine is through PuTTY. I recently started renting space on a remote server so that I could work on a project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |