You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please read the FAQ and check existing issues before creating a new issue.
What steps will reproduce the problem?
1. putty to a remote computer (I only have access to one remote computer)
2. run gnuplot there
3. try to delete a character in the command, or move curse to front or end by
pressing Home & End, the action is not performed, but instead display 4~ etc
these kind of combinations.
What is the expected result? What happens instead?
It works fine when in the unix environment, but it does not work as expected
when in gnuplot. The response of the erroneous keys seen in gnuplot are the
following
delete --- 3~
insert --- 2~
home --- 1~
end --- 4~
pgup --- 5~
pgdn --- 6~
Just to mention, these keys are located on an isolated block of keys from the
main character keys. It's a x61s lenovo laptop keyboard. But these keys
function correctly in my winxp operation system.
It could be because of the gnuplot software. I had been to the forum for
gnuplot, but they suggest it could be due to the operation system.
PutTTYcyg version: 0.6
Cygwin version: 1.5
Windows version: xp with sp2 installed
Do you have any firewall software installed? No, but the router might have
built-in firewall
Please attach your PuTTY configuration. Use this Windows command to create
putty.reg:
REG EXPORT HKEY_CURRENT_USER\Software\SimonTatham\PuTTY putty.reg
Please provide any additional information below.
Original issue reported on code.google.com by jun.phys...@gmail.com on 25 Sep 2010 at 7:52
"putty to a remote computer"
It sounds like this issue is not PuTTYcyg-specific as you are using PuTTYcyg as
an SSH client. Does this problem also happen with PuTTY? If so, then you
should ask the PuTTY support folk about it. If this problem does not happen
with PuTTY, but does happen with PuTTYcyg, then it is probably a bug here.
Original comment by medgar123 on 29 Oct 2010 at 12:17
Original issue reported on code.google.com by
jun.phys...@gmail.com
on 25 Sep 2010 at 7:52Attachments:
The text was updated successfully, but these errors were encountered: