WindTerm 2.7.0 Prerelease 2

[kingToolbox]

Spotlight

Tmux Integration (tmux -CC)

Tmux Integration making it easier and more efficient for you to work with tmux. With this integration, tmux sessions, windows, and panes are mapped and displayed in the native user interface. All commonly used tmux features are fully supported, creating a near-perfect fusion between tmux and WindTerm.

Tmux Integration supports:

• Tmux Integration
• Tmux Integration / Common Keyboard Shortcuts
• Tmux Integration / Attach Session
• Tmux Integration / Detach Session
• Tmux Integration / Execute Tmux Command
• Tmux Integration / Kill Pane
• Tmux Integration / Kill Window
• Tmux Integration / Kill Session
• Tmux Integration / Move Pane To New Window
• Tmux Integration / New Window
• Tmux Integration / Rename Pane
• Tmux Integration / Rename Window
• Tmux Integration / Rename Session
• Tmux Integration / Resize Pane
• Tmux Integration / Select Layout
• Tmux Integration / Select Pane
• Tmux Integration / Select Window
• Tmux Integration / Split Pane
• Tmux Integration / Swap Pane
• Tmux Integration / Swap Window
• Tmux Integration / Synchronize Panes
• Tmux Integration / Toggle Pane Zoom

Usage:

Windows

Version	Architecture	Operating Systems
WindTerm_2.7.0_Prerelease_2_Windows_Portable_x86_64	x86_64	Windows 7, Windows 8, Windows 10, Windows 11
WindTerm_2.7.0_Prerelease_2_Linux_Portable_x86_64	x86_64	Generic Linux (glibc 2.17 and later)

Installation

• Download portable packages and uncompress it.

MacOS
Please open dmg file and drag WindTerm.app to the Applications folder.

Linux
Please use the following command to run the WindTerm after downloading.

tar -xzvf WindTerm_2.4.0_Linux_Portable_x86_64.tar.gz && cd ./WindTerm_2.4.0 && chmod +x ./WindTerm && ./WindTerm

• Scoop

scoop bucket add extras
scoop install windterm

• Chocolatey

choco install windterm

Upgrade

Versions before Version 2.4.0

1. Start WindTerm and select the profiles directory and quit.
2. Replace the new .wind/profiles folder with the old profiles folder.
3. Restart WindTerm and all the sessions and configuration will be restored.

Versions after Version 2.4.0

1. Start WindTerm and select the profiles directory containing the old .wind folder.
2. It is recommended to choose the Home Directory to facilitate subsequent upgrades.

If the .wind folder needs to be moved to another system:

1. Quit WindTerm.
2. Replace the new .wind folder with the old .wind folder.
3. Restart WindTerm and all the sessions and configuration will be restored.

The .wind folder is cross-platform.

Known Issues:

• [ZMODEM] Only support file names contains ASCII characters in Windows, otherwise the file name of the transfered file will be garbled after transmission, but it does not affect the correctness of the file content. Linux and MacOS version does not have this problem.
• [TMUX] Tmux integration lacks support for Sender Pane and Sync Input.
• [TMUX] Tmux integration does not support nesting.

Changes in Version 2.7.0 Prerelease 2 (2025-1-11):

Features:

• [APP] Supports Tmux Integration.

Shortcut	Action
Alt + B	Show Mux/Tmux Command Palette
Alt + X	Close the current pane
Alt + Z	Zoom the current pane
Alt + Left Arrow	Select the left pane
Alt + Right Arrow	Select the right pane
Alt + Up Arrow	Select the pane above
Alt + Down Arrow	Select the pane below
Alt + [	Select the previous window
Alt + ]	Select the next winodw
Alt + -	Split pane right
Alt + Shift + -	Split pane left
Alt + |	Split pane down
Alt + Shift + |	Split pane up

• [GUI] Default font updated to RobotoMono Nerd for proper icon display in WindFind. can support nerd font https://www.nerdfonts.com/ ? #2413
• [SESSION] Supports syntax highlighting, folding, command history, and autocompletion for Fish shell.
• [SCHEME] Supports highlighting four or eight consecutive hexadecimal digits.
• [SCHEME] Supports highlighting for words following negations (e.g., "not," "don't").
• [TERM] Added tmux-256color.term configuration file.
• [TERM] Supports CSI ?4m to allow query key modifier options. 'ESC[?4m' is displayed when vim opens the file #1623 When using vim/vi, ESC[?4m will be automatically added to the screen #1814 Regarding the ESC[?4m problem with vim 9 can you update a temporary version first or is there a patch for that? #2016
• [TERM] Supports ESC k ... ESC \ to allow screen to set the window title.

Improvements:

• [SESSION] Enabled keep session alive by default to avoid unnecessary disconnections after long idle periods; default interval is 60s. [Feature Request] Add new ssh keep alive method #2051
• [GUI] No longer draws a rectangular caret when focus is lost.
• [GUI] Splitting or merging panes now only resizes adjacent panes, not all panes.
• [GUI] Improved width calculation for text displayed in the margins.
• [GUI] Reassigned shortcut for action Window.SetLocalMode and Window.SetRemoteMode from Alt+Enter to Ctrl+Enter.
• [GUI] Reassigned shortcut for action Window.ToggleFocusMode from Ctrl+Enter to Alt+Enter.
• [MODEM] Replaced progress bar widget with a text-based progress bar to avoid unnecessary resizing of the terminal window.
• [TEXT] Improved text insertion by reducing memory moves from two to one, resulting in better performance.

Bugs:

• [SSH] Unable to connect to OpenWrt, regression from v2.7.0 Prerelease 1.
• [SHELL] Temporarily replaced ConPty with WinPty to prevent illegal character CSI 0%m in vi. vim shows unexpected characters #1114
• [GUI] No longer uses full hinting for text rendering to avoid potential blurry text, regression from v2.7.0 Prerelease 1. The text rendering needs to be optimized #2438
• [GUI] No longer prompts to import Shell configuration on startup, as this was only necessary for pre-2.5 compatibility. How can I solve the problem where macos uses windterm and pops up a window every time it restarts? #2100 I have to re-import shell sessions every time #2119 Mac每次重启WindTerm都会弹窗提示“The following new features have been added to shell sessions” #2525 Prevent Shell Sessions Pop-up #2536
• [GUI] Entering protocol://host:port in the address bar would incorrectly ignore the specified port and use the protocol's default port instead. There is a bug in the address bar 地址栏存在bug  #2255
• [GUI] File dialog returns folder path instead of entering folder on "Open" after folder selection.
• [GUI] Double-pressing the Alt+; key results in an empty list in the Command Palette.
• [GUI] Preview window continuously shrinks as the mouse moves downwards over the scrollbar. [bug] In the 2.7-prerelease version, the size of the window preview is abnormal.(2.7-prerelease 版本，窗口预览功能异常) #2634
• [GUI] The screen flickers in fullscreen mode when opening a menu via the Layout button, regression from v2.7.0 Prerelease 1.
• [FILER] Infinite loop of Failed to open directory errors occurs when switching to a session where filer's current folder has been removed.
• [FILER] Unnecessary //wsl$/ditroname/ is included in paths generated by Copy Directory Path To Terminal and Copy Paths To Terminal menu items.
• [FILER] Failed to enter the user's home directory when starting WSL, defaulting to the root directory.
• [FILER] When browsing the cmd or wsl system, folder properties dialog is blank when right-clicking empty space and selecting menu item "Properties...".
• [FILER] When browsing files in the wsl subsystem, the option Show Hidden Items does not hide files starting with a dot.
• [SESSION] Default window size used on initialization even when Adjust the windows rows and columns is true, leading to incorrect scrollbar display.
• [TERM] Previous term type was not properly restored after exiting vt52.

Checksums:

WindTerm_2.7.0_Prerelease_2_Windows_Portable_x86_64.zip

• md5: 31c56c8007c98cd65461753e6a8d07fd
• sha256: d58fecd477e3bc6e4d3eb5fd52ca910d51b1beea483dfc1c8aba73de3f9f98fe

WindTerm_2.7.0_Prerelease_2_Linux_Portable_x86_64.tar.gz

• md5: 6991090a634ba46f9a6dd100590051bd
• sha256: 648140dc049adef41dd73afef2fe1b035f0dc46ba634a3fb7f4704cc95403448

---

This discussion was created from the release WindTerm 2.7.0 Prerelease 2.

[cusclo]

没有2.7的mac版本。。

[Igzak]

Linux?

[err0rcat]

Will the sudden crashes under Linux and Mac be cured?

[wyslmt]

In the ver 2.6 and ver 2.7 pre1, the shell path for WSL only needs to be filled in: wsl
In version 2.7 pre2, the following errors will occur:
wsl.exe: WinPty Error: start terminal process -> CreateProcess failed

Need to change the shell path to the full path: C:\Windows\System32\wsl.exe
If you have the same problem, you can try it out.

[kingToolbox]

Thanks, I'll look into this issue.

[kingToolbox]

In the previous version, ConPty was used to create a shell process by default and launched via C:\Windows\System32\kernel32.dll. Since kernel32.dll and wsl.exe were in the same directory, wsl.exe could be found directly. However, ConPty is currently temporarily disabled due to a bug. The alternative solution, WinPty, uses winpty.dll to create a shell process. Because this DLL is not in the same directory as wsl.exe, wsl.exe cannot be found correctly.

Although ConPty will be re-enabled in version 2.8.0, it's likely that kernel32.dll will no longer be used to create a shell process for performance reasons. Therefore, please use the full path. The previous ability to use wsl.exe directly was just a coincidence, not by design.

[wyslmt]

A coincidental feature 😃

[Nexiuss]

bro, please help support the 2.7 MAC Apple chip version @kingToolbox

[kingToolbox]

@cusclo
@Igzak
I'm currently working hard to fix some critical issues in the prerelease version, mainly focusing on SSH and ZModem. After that, version 2.7.0 Prerelease 3 will be released. If all goes well, the official release, including versions Windows, MacOS, and Linux, will be out soon.

@err0rcat
@Nexiuss
I'm not sure what sudden crash issue you're referring to, but version 3.0 will be completely rewritten, both the interface and the core. Therefore, any hidden crash issues should be thoroughly resolved. A macOS ARM version will also be available at that time.

Version 2.8's main features are complete and it is expected to be released in March.

Version 2.9 will be an LTS (Long-Term Support) release and is unlikely to include new features. However, I will continuously release bugfix versions to address as many issues mentioned in the existing issues as possible, until version 3.0, which will feature a complete rewrite of all functionalities, is finished.

Version 3.0 will first implement RDP and a completely new interface, and then integrate existing features such as Shell, Telnet, SSH and Serial. The development cycle for the first version of 3.0 is estimated to be six months.

[err0rcat]

@kingToolbox Thank you for your reply.
The sudden crashes I'm refering to occur only in Linux and MacOS.
The closest I've gotten to notice it is when you reboot the server and then close the tab it was open in - it crashes. It doesn't do it every time, but occasionally it does and its very annoying cause it closes everything (10-12 working tabs).

[err0rcat]

Will try to produce one. Will post here as soon as I get one.

Thank you for the amazing tool you've built. I use it every day. The best one out there so far. Please keep up the amazing job!

[err0rcat]

@kingToolbox as promised, heres the fresh CR. See attachment.
windterm_crash_report_short_20250127.txt

Actions:

1. opened a tab with a random server, logged in
2. opened another tab, logged in updated another server and rebooted it. then reconnected by hitting ENTER after some time and logged in again.
3. opened 3 more tabs. all logged in. Left them be.
4. opened another tab, logged in, updated another random server and rebooted it.
5. after a shord period of time closed the tab in nr.4 with cmd+shift+w. no problem.
6. went for coffee :)
7. got back and selected tab in nr.2
8. pressed cmd+shift+w and got a CRASH!

Hope it helps :)

[kingToolbox]

Thanks, reproducing the steps is a little tricky, and I appreciate you going through the trouble 👍 . From the symptoms and logs, it seems very similar to issue #2666, both involving a null pointer when trying to activate after closing a tab. I'll look into it further and hope to fix it thoroughly.

[kingToolbox]

Unfortunately, I haven't been able to reproduce the issue following the steps you provided. However, based on the information from the error reports, I've rewritten the relevant code to be more robust, hoping to reduce or even eliminate this problem.

The Mac version will be released soon. Please download and use it when available. If you still encounter crash issues, please submit a new issue, and I will continue to investigate. Thank you.

[err0rcat]

Yea, I agree this situation is pretty tricky to reproduce. It's almost spontaneous.
Waiting for the release :)
Thank you for your work.

[darkhandz]

Hi, when will the Linux version be released? I'm looking forward to testing it.
Today, I used v2.6.1 on Linux for the first time, and I noticed that WindTerm keeps showing this prompt window. Clicking [Yes] or [No] doesn't resolve the issue.
KDE Plasma, EndeavourOS

[err0rcat]

Hi, when will the Linux version be released? I'm looking forward to testing it. Today, I used v2.6.1 on Linux for the first time, and I noticed that WindTerm keeps showing this prompt window. Clicking [Yes] or [No] doesn't resolve the issue. KDE Plasma, EndeavourOS

locate the file <path-to-windterm>/global/wind.config
find and set the following line inside:
set "terminal.reimportShellSessions": false

[darkhandz]

Oh man, you saved my day!

[kingToolbox]

Thank you, @err0rcat. This issue has been fixed in version 2.7.0 Prerelease 2.

This bug was caused by a design error in the configuration value terminal.reimportShellSessions. Therefore, the simplest fix was adopted: completely removing the relevant code. This code was only used for compatibility with configurations from versions prior to 2.5.0, so it is no longer needed.