kingToolbox / kingToolbox/WindTerm

some bugs

Open
#1,590 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
32.3k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Description

1. Immediately after running WindTerm and opening multiple ssh sessions at the same time, you will be asked to enter the WindTerm password multiple times. It should only be entered once to be correct. Or should ask for the password immediately after the software starts.
2. Session list, when expanding multiple session groups, there is no function to close all session groups quickly.
Cannot import mobaxterm session list.
3. The font of the session list does not seem to be high DPI, including the top switch tab is not high DPI, and the icon is not high DPI.
4. In the lower right corner, under the light color theme, the green word looks blinding.
5. There are frequent flashbacks, whether when executing commands after connecting to ssh, or when transferring files in sftp.
6. can not bring up the management of each session of the password management function, including copying the saved user name and password.
7. After hiding all the menus, it is impossible to bring up the main menu again.
8. Sometimes the ssh window can not render the output logs in color. Only the pure black and white logs are displayed.
9. When logging into a remote server using jumpserver, when copy session, you have to re-enter the Google Authenticator code.
10. no multiple windows to execute commands at the same time, refer to mobaxterm, the function of writing commands in all terminals.
11. it is recommended that the switch tab and session list merge.
12. File manager and session list together in the sidebar, should add a button to hide and display the entire sidebar.

The above advice may not be correct, for reference only.

![image](https://user-images.githubusercontent.com/22386267/229073164-92b9c3f2-bd3e-49ff-8987-14b6c7cc25eb.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified. The report combines twelve separate bugs, feature requests, and design suggestions, so each item would need to be split into a scoped issue with a reproducible case and an explicit completion condition.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli, desktop-dev, networking
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.