Unable to Start micro Under PuTTY Set For 256-Color Mode

[6XGate]

Description of the problem or steps to reproduce

1. Set PuTTY to use putty-256color as its Terminal-type string, under Connection > Data (in Terminal Details)
2. Connect to a system via SSH with PuTTY,
3. Run micro with or without any file path.

Specifications

Commit hash: 1856891 (1.4.1)
OS: Ubuntu 18.04 (under WSL or as the main OS)
Terminal: PuTTY, using putty-256color as its Terminal-type string.

[jackwilsdon]

What output do you get when trying to start micro? I can't reproduce the issue.

[MarcusE1W]

I just got my longstanding terminal problem resolved by using the latest nightly build 1.4.2-dev 29. You could try that.

[6XGate]

Sorry, it's returning:

terminal entry not found
Fatal: Micro could not initialize a screen.

[phorce1]

18 months later I have this same issue with the latest 2.07 installed tonight on a headless server I use through Putty.

It appears to work if I ssh in from a WSL2 Debian session. I guess it's time to start phasing out putty.

Well, both Putty AND screen cause the problem. In ssh if I go into my existing screen session with 'screen -dR" micro fails in the exact same way. It is not a combination of both, it is either or. If one is using screen or if one is connecting with putty then micro fails.

[zyedidia]

Maybe Putty doesn't report the TERM correctly? I have found KiTTY works better (it's a fork of Putty). Also, you can try setting the option xterm to true. This will make micro believe that your terminal is "normal" despite what it might be reporting. You can run micro -xterm true, and then set the option globally once micro is running (or you can place the setting in ~/.config/micro/settings.json).

[mrx23dot]

KiTTY works great with micro.
Could we make micro -xterm true default or auto detect?
It makes font more readable.

Home directory config file is cumbersome, I have create dir tree, then set it up for all users.