FS#62338 - [putty] PyTTY support out-of-the-box
Attached to Project:
Arch Linux
Opened by Brian W (MrBW) - Sunday, 14 April 2019, 07:21 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 27 September 2023, 06:42 GMT
Opened by Brian W (MrBW) - Sunday, 14 April 2019, 07:21 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 27 September 2023, 06:42 GMT
|
Details
Description: Archlinux is not configured to work with PuTTY
default settings.
(I my world is a bug, but I think the maintainers wouldn't agree :-P) Additional info: I might have a wrong perception of PyTTY, but would it be wrong to say it's the de facto standard of terminal programs? I find it strange Archlinux is not configured to work with PuTTY default settings in regards to HOME(start-of-line), END(end-of-line) and the numpad. Last tested with the newest PuTTY 0.71 and Archlinux ISO from 13. april 2019 (but it has been like this at least for the past 2-3 years, probably "always") It's a pity you have to struggle with such trivial issue every time you install/ISO-boot Archlinux. But maybe there are good reasons for this? To get it to work correctly I do the following: #bindkey "^[[1~" beginning-of-line #bindkey "\e[4~" end-of-line And for numpad to work: see attached screen-dump |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 27 September 2023, 06:42 GMT
Reason for closing: Won't implement
Additional comments about closing: Refer PM's comments
Wednesday, 27 September 2023, 06:42 GMT
Reason for closing: Won't implement
Additional comments about closing: Refer PM's comments
For Linux I use one of the terminal programs in combination with openssh' cli tool 'ssh'.
There's nothing we change... All settings are from upstream source tarball.
But maybe they change the default settings from the upstream source tarball.
But if you use the default configuration then just close this request.
I've made a script to fix it.
It was just to make it easier for others new users who use Windows as client as me ;-)