Hopefully, the next version will support shortcuts in cmd.exe panel

[JiangBoy]

exp:
ctrl+a => cursor jump to line begin
ctrl+e => cursor jump to line end
ctrl+w/ctrl+backspace=> delete the previous word
ctrl+r => display cmd histroy
and so on

[kingToolbox]

Sorry for late reply.

Thanks for your advice. I have integrated cmd with clink and will release it in the next WindTerm_2.4.0_Prerelease_2 version. Please stay tuned. 😄

[JiangBoy]

Sorry for late reply.

Thanks for your advice. I have integrated cmd with clink and will release it in the next WindTerm_2.4.0_Prerelease_2 version. Please stay tuned. 😄

Thank you for creating such good-working software

[kingToolbox]

I am happy to inform you that WindTerm_2.4.0_Prerelease_2 has been released and clink has been packaged. You need to execute menu item Session pane - Right-click menu - Import - Shell Session to regenerate the cmd and admin:cmd sessions. Please download and check it, thank you.

BTW:
You can also try the new feature Free Type Mode, which will be more convenient. I hope you like it.

[jan-bar]

I like cmder, and cmder also uses clink, but it provides richer functions

The directory and the input command are displayed on different lines. If you go to the git project directory, the branch will be displayed. I love this feature

@kingToolbox But the command line recording of the outline doesn't work properly anymore. But I can use the history command to view the history command line record of cmder. If you can fix this, it would be much appreciated.

[kingToolbox]

I will solve the configuration problems of folding and outlining for you. But can the init.bat file of Cmder be used directly?

[jan-bar]

I will solve the configuration problems of folding and outlining for you. But can the init.bat file of Cmder be used directly?

Yes, I use it in both jetbrains ide and vscode as shown below. cmder.exe Also use the following command line to start the terminal.

[kingToolbox]

I am happy to inform you that WindTerm_2.4.0 has been released and folding and outling of Cmder have been fixed. Please download and check it, thank you.

BTW:
Currently folding and outline support the official prompt λ of Cmder, but may still not match your (py39) #. You can refer to the existing fragments to write your own matching rules.

Lexer: WindTerm_Profiles_Path\terminal\schemes\cmd\cmd.lexer
Folding: WindTerm_Profiles_Path\terminal\schemes\cmd\cmd.fold
Outlining: WindTerm_Profiles_Path\terminal\schemes\cmd\cmd.outline

If you have any questions, don't hesitate to ask me.

[jan-bar]

@kingToolbox

Thanks a lot, it works fine. the (py39) # It's python's conda tool result , # is the custom I'm used to.

[kingToolbox]

Glad to hear this good news. There are indeed too many types of command prompts, and it is unrealistic to support all of them. The best way can only be customized by users.

The focus of WindTerm is still SSH, and because of cross-platform, specific development for a certain Shell is not yet possible. However, I think that with the development of plug-in features in the future, it should be as convenient as Cmder one day.

[jan-bar]

Glad to hear this good news. There are indeed too many types of command prompts, and it is unrealistic to support all of them. The best way can only be customized by users.

The focus of WindTerm is still SSH, and because of cross-platform, specific development for a certain Shell is not yet possible. However, I think that with the development of plug-in features in the future, it should be as convenient as Cmder one day.

I have a good idea, to write a cross-platform executable program，This executable is deployed by the user on his server， that interacts with the executable program when windterm connects to the server, so that I can easily get some required data. For example, working directory, command history, so that you don't have to match terminal text, and running efficiency should also improve. It is even possible to define only the specification, and the executable program is written by the user, which will be more flexible

Because I see an issue that wants the file manager to follow the current working directory of ssh, as well as the current command history. I don't know if this proposal is feasible.