Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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 David Runge (dvzrv) - Friday, 17 January 2020, 13:09 GMT
Task Type Feature Request
Category Packages: Extra
Status Assigned
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

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

Comment by Christian Hesse (eworm) - Friday, 17 January 2020, 13:22 GMT
IMHO the "de facto standard" applies for MS Windows only...
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.
Comment by Brian W (MrBW) - Friday, 17 January 2020, 13:39 GMT
I just don't have these issues with Debian, Ubuntu or any other distros (as I can recall).
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 ;-)

Loading...