termwnd

2025-12-10 0 942

TermWnd

The purpose of the code in this repository is both to distinguish between Conhost and Windows Terminal processes and to determine which terminal window hosts the current console process. Third-party terminal apps are not supported.
The source files are transcriptions of pretty much the same core code in different programming languages.

Minimum requirements to compile/run the code:

Source files in Windows Batch, C, C++, C#.Net, PowerShell, and VB.Net are published in the src folder. They all depend on Windows being the target operating system. Also, this code relies on the hidden ConPTY window being owned by the Terminal window. Presumably this has been first implemented in Windows Terminal v1.14. Other specific dependencies are listed below.

File Requirement
*.bat Windows PowerShell 5.1
*.c C99
*.cpp C++20
*.cs .NET Framework 4.5
*.ps1 Windows PowerShell 2
*.vb .NET Framework 4.5

Relevant code:

The source files in this repository contain fully functional code that demonstrates how to use the search procedure. However, if you intend to use it in your own code, it might be useful to know which essential pieces of code you need to include.

File Code of interest Value of interest
*.bat TermWnd macro defined in the :init_TermWnd routine the errorlevel returned by the TermWnd macro is the handle of the hosting terminal window (0 if an error occurred)
*.c GetWinterm function, along with structure type winterm_t and related code if the GetWinterm function returns true, the referenced object of type winterm_t is filled with properties of the hosting terminal window (false is returned if an error occurred)
*.cpp everything in namespace termproc, along with namespace saferes the values returned by the class methods winterm::hwnd(), winterm::pid(), winterm::tid(), and winterm::basename() (exception if an error occurred)
use the winterm::refresh() method to update the values after the tab has been moved to another window
*.cs class WinTerm the values of properties WinTerm.HWnd, WinTerm.Pid, WinTerm.Tid, and WinTerm.BaseName (exception if an error occurred)
use the WinTerm.Refresh() method to update the values after the tab has been moved to another window
*.ps1 Type referencing class WinTerm the values of properties [WinTerm]::HWnd [WinTerm]::Pid [WinTerm]::Tid [WinTerm]::BaseName (type WinTerm not defined if an error occurred)
use the [WinTerm]::Refresh() method to update the values after the tab has been moved to another window
*.vb Module WinTerm the values of properties WinTerm.HWnd, WinTerm.Pid, WinTerm.Tid, and WinTerm.BaseName (exception if an error occurred)
use the WinTerm.Refresh() method to update the values after the tab has been moved to another window

Background:

A few years ago Microsoft began to develop a new terminal application – Windows Terminal. The installation is available for Windows 10, and Windows 11 already ships with it. By an update in October \’22 Microsoft turned it into the default terminal app on Windows 11.
As of now, Windows Terminal coexists with the good old Conhost. Users are able to choose which is taken as their default terminal app.

In the past, it has been easy to figure out which terminal window hosts the shell/console application. Behind the scenes it was always the Conhost window. The GetConsoleWindow() function returned its window handle.
However, if the Windows Terminal hosts our app, GetConsoleWindow() returns the handle to the hidden ConPTY window.
Beginning with Windows Terminal version 1.18, all terminal windows run in only one process and tabs can be moved from one window to another. This makes it even more complicated to find the right window.

I tried to write a piece of code to find the window even if the tab has been moved out or attached to another window. This requires to involve some undocumented API. I left a couple of comments in the code that roughly explain how this all works.

In each file is also a piece of unrelated code that fades the window out and in again. I found it an impressive way of proving that the right window had been found.

Example output:

Note the updated thread id (TID) and window handle (HWND) in the newly written lines after moving the tab to another window.


下载源码

通过命令行克隆项目:

git clone https://github.com/german-one/termwnd.git

收藏 (0) 打赏

感谢您的支持,我会继续努力的!

打开微信/支付宝扫一扫,即可进行扫码打赏哦,分享从这里开始,精彩与您同在
点赞 (0)

申明:本文由第三方发布,内容仅代表作者观点,与本网站无关。对本文以及其中全部或者部分内容的真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。本网发布或转载文章出于传递更多信息之目的,并不意味着赞同其观点或证实其描述,也不代表本网对其真实性负责。

左子网 编程相关 termwnd https://www.zuozi.net/33310.html

常见问题
  • 1、自动:拍下后,点击(下载)链接即可下载;2、手动:拍下后,联系卖家发放即可或者联系官方找开发者发货。
查看详情
  • 1、源码默认交易周期:手动发货商品为1-3天,并且用户付款金额将会进入平台担保直到交易完成或者3-7天即可发放,如遇纠纷无限期延长收款金额直至纠纷解决或者退款!;
查看详情
  • 1、描述:源码描述(含标题)与实际源码不一致的(例:货不对板); 2、演示:有演示站时,与实际源码小于95%一致的(但描述中有”不保证完全一样、有变化的可能性”类似显著声明的除外); 3、发货:不发货可无理由退款; 4、安装:免费提供安装服务的源码但卖家不履行的; 5、收费:价格虚标,额外收取其他费用的(但描述中有显著声明或双方交易前有商定的除外); 6、其他:如质量方面的硬性常规问题BUG等。 注:经核实符合上述任一,均支持退款,但卖家予以积极解决问题则除外。
查看详情
  • 1、左子会对双方交易的过程及交易商品的快照进行永久存档,以确保交易的真实、有效、安全! 2、左子无法对如“永久包更新”、“永久技术支持”等类似交易之后的商家承诺做担保,请买家自行鉴别; 3、在源码同时有网站演示与图片演示,且站演与图演不一致时,默认按图演作为纠纷评判依据(特别声明或有商定除外); 4、在没有”无任何正当退款依据”的前提下,商品写有”一旦售出,概不支持退款”等类似的声明,视为无效声明; 5、在未拍下前,双方在QQ上所商定的交易内容,亦可成为纠纷评判依据(商定与描述冲突时,商定为准); 6、因聊天记录可作为纠纷评判依据,故双方联系时,只与对方在左子上所留的QQ、手机号沟通,以防对方不承认自我承诺。 7、虽然交易产生纠纷的几率很小,但一定要保留如聊天记录、手机短信等这样的重要信息,以防产生纠纷时便于左子介入快速处理。
查看详情

相关文章

猜你喜欢
发表评论
暂无评论
官方客服团队

为您解决烦忧 - 24小时在线 专业服务