Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

navigation arrows do not work #171

Open
metallyuga13 opened this issue Aug 23, 2021 · 6 comments
Open

navigation arrows do not work #171

metallyuga13 opened this issue Aug 23, 2021 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@metallyuga13
Copy link

Good afternoon. When I use ssh on a linux server and start Midnight Commander, the navigation arrows on the keyboard do not work. Is this a problem or do you need to change something in the settings?
MacOs big sur 2020 intel.
thanks

@kingToolbox
Copy link
Owner

Hello. What $TERM do you use? You can print it by the command echo $TERM.

I tested it on the Windows system and found no problems, at least the up and down keys can be used. I will do further testing on the MacOS system.

@metallyuga13
Copy link
Author

Hello.
xterm-256color
When opening MC, you always have to turn off word wrap. Pressing the arrows prints DCBA characters.
Снимок экрана 2021-08-24 в 17 51 35

@kingToolbox
Copy link
Owner

This is indeed abnormal. The window size should be adaptive. But I cannot reproduce this bug. Would you like to provide a little more information to help analyze and locate this problem? If you want, please follow the steps below:

  • Open the session.
  • Turn on the "Word Wrap" mode.
  • Before opening MC, check the menu item "Mode(7) - Debug Mode" to enter the debug mode.
  • Enter "mc" to open MC and make sure the illegal screen content appear.
  • Press some navigation arrows and make sure the illegal ABCD content appear.
  • Uncheck the menu item "Mode(7) - Debug Mode" to leave the debug mode.
  • Click the menu item "Right click menu - Log - Open Log Folder".
  • Open the folder debug, zip and upload the newly generated log file as an attachment when you comment this or email to WindServices@yandex.com to better protect privacy.
  • Done.

Please don't worry about the content of the log file, it will only record the current command input and output, and will not record any sensitive information, including passwords, ip, computer information, etc.

The log file is in plain text format. You can use any text editor to open and review the content. If there is any information you don't want to disclose, you can delete it or replace it with "#" manually. Thank you very much.

@kingToolbox kingToolbox self-assigned this Aug 24, 2021
@kingToolbox kingToolbox added the bug Something isn't working label Aug 24, 2021
@metallyuga13
Copy link
Author

Ready. I sent it by mail.

@kingToolbox
Copy link
Owner

Sorry for the late reply. I just finished a long trip, and because there is no Internet, I can't deal with the issue in time.

I have received your email. I will analyze the debug file and find out the problem. If there is any progress, I will update it here. Thank you very much!

@kingToolbox
Copy link
Owner

The new WindTerm_2.2.0_Prerelease_4 version has been released and this issue has been fixed, please download and check it, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants