{"id":36385,"date":"2025-12-15T11:31:28","date_gmt":"2025-12-15T08:31:28","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/windows-terminal-conpty-ve-win32-input-mode-nedir\/"},"modified":"2025-12-15T11:31:28","modified_gmt":"2025-12-15T08:31:28","slug":"windows-terminal-conpty-ve-win32-input-mode-nedir","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/windows-terminal-conpty-ve-win32-input-mode-nedir\/","title":{"rendered":"Windows Terminal, ConPTY ve win32-input-mode Nedir?"},"content":{"rendered":"

Go ConPTY Uygulamalar\u0131nda Windows Terminal Girdilerini Y\u00f6netme<\/p>\n

Modern terminal uygulamalar\u0131 geli\u015ftirirken, kullan\u0131c\u0131 girdilerini do\u011fru bir \u015fekilde yakalamak ve i\u015flemek \u00e7o\u011fu zaman b\u00fcy\u00fck bir zorluk haline gelebilir. \u00d6zellikle Windows platformunda, Windows Terminal’in ortaya \u00e7\u0131k\u0131\u015f\u0131 ve beraberinde getirdi\u011fi win32-input-mode<\/code> adl\u0131 \u00f6zel girdi modu, Go ile ConPTY (Console Pseudo-terminal) uygulamalar\u0131 geli\u015ftirenler i\u00e7in beklenmedik karma\u015f\u0131kl\u0131klar yaratmaktad\u0131r. Peki, bu durumun ard\u0131ndaki nedenler nelerdir ve Go kullanarak bu girdileri nas\u0131l “evcille\u015ftirebiliriz”? Bu makale, ConPTY’nin temel dinamiklerinden win32-input-mode<\/code>‘un derinliklerine, Go ile bu zorluklar\u0131n \u00fcstesinden gelmek i\u00e7in ad\u0131m ad\u0131m \u00e7\u00f6z\u00fcmlere kadar uzanan kapsaml\u0131 bir rehber sunmaktad\u0131r. Okuyucuyu s\u0131f\u0131rdan konuya dahil ederek, hem teorik bilgiyi hem de pratik uygulama \u00f6rneklerini bir araya getirmeyi hedefliyoruz.<\/p>\n

Windows i\u015fletim sistemlerinde terminal deneyimi, uzun y\u0131llar boyunca genellikle cmd.exe veya PowerShell gibi geleneksel konsol pencereleriyle s\u0131n\u0131rl\u0131 kalm\u0131\u015ft\u0131. Ancak, Microsoft’un Windows Terminal’i piyasaya s\u00fcrmesiyle bu durum k\u00f6kten de\u011fi\u015fti. Windows Terminal, sekmeli aray\u00fczler, GPU h\u0131zland\u0131rmal\u0131 metin i\u015fleme, Unicode ve emoji deste\u011fi gibi modern \u00f6zelliklerle donat\u0131lm\u0131\u015f, geli\u015ftiriciler ve ileri d\u00fczey kullan\u0131c\u0131lar i\u00e7in tasarlanm\u0131\u015f g\u00fc\u00e7l\u00fc bir ara\u00e7t\u0131r. Bu modernle\u015fme, terminal uygulamalar\u0131n\u0131n altyap\u0131s\u0131nda da \u00f6nemli yenilikleri beraberinde getirdi.<\/p>\n

Bu yeniliklerden en \u00f6nemlisi \u015f\u00fcphesiz ConPTY veya “Console Pseudo-terminal” kavram\u0131d\u0131r. Geleneksel olarak, Windows’taki konsol uygulamalar\u0131 do\u011frudan konsol API’lerini kullanarak input ve output i\u015flemlerini ger\u00e7ekle\u015ftirirdi. Bu da \u00fc\u00e7\u00fcnc\u00fc taraf terminal em\u00fclat\u00f6rlerinin veya kabuklar\u0131n\u0131n, bu uygulamalar\u0131n davran\u0131\u015flar\u0131n\u0131 manip\u00fcle etmesini veya \u00e7\u0131kt\u0131lar\u0131n\u0131 d\u00fczg\u00fcn bir \u015fekilde ayr\u0131\u015ft\u0131rmas\u0131n\u0131 zorla\u015ft\u0131r\u0131yordu. ConPTY, bu sorunu \u00e7\u00f6zmek i\u00e7in geli\u015ftirilmi\u015f bir aray\u00fczd\u00fcr. T\u0131pk\u0131 Linux’taki PTY (pseudo-terminal) gibi, ConPTY de bir alt s\u00fcreci (\u00f6rne\u011fin, bir CLI uygulamas\u0131) izole bir konsol oturumunda \u00e7al\u0131\u015ft\u0131rman\u0131za olanak tan\u0131r. Ancak, PTY’den farkl\u0131 olarak, ConPTY, alt s\u00fcrecin Windows konsol API’lerini kullanmaya devam etmesini sa\u011flar. Yani, alt s\u00fcre\u00e7 kendini ger\u00e7ek bir konsolda \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 zannederken, asl\u0131nda onunla ConPTY arac\u0131l\u0131\u011f\u0131yla ileti\u015fim kuran bir ara program vard\u0131r. Bu ara program, alt s\u00fcrecin girdilerini yakalayabilir ve \u00e7\u0131kt\u0131lar\u0131n\u0131 y\u00f6nlendirebilir.<\/p>\n

Peki, win32-input-mode<\/code> bu denkleme nerede giriyor? ConPTY, alt s\u00fcrecin \u00e7\u0131kt\u0131s\u0131n\u0131 VT (Virtual Terminal) sekanslar\u0131na d\u00f6n\u00fc\u015ft\u00fcrerek ana s\u00fcrece (yani bizim Go uygulamam\u0131za veya Windows Terminal’e) g\u00f6nderir. Bu, \u00e7\u0131kt\u0131lar\u0131n modern terminal em\u00fclat\u00f6rleri taraf\u0131ndan kolayca anla\u015f\u0131lmas\u0131n\u0131 ve i\u015flenmesini sa\u011flar. Ancak, girdi taraf\u0131nda i\u015fler biraz daha karma\u015f\u0131kla\u015f\u0131r. Windows Terminal, varsay\u0131lan olarak, daha zengin etkile\u015fimlere olanak tan\u0131mak i\u00e7in win32-input-mode<\/code>‘u kullanabilir. Bu mod etkinle\u015ftirildi\u011finde, kullan\u0131c\u0131dan gelen klavye tu\u015flar\u0131, fare hareketleri ve t\u0131klamalar\u0131 gibi girdiler, do\u011frudan VT sekanslar\u0131 olarak de\u011fil, Windows’un kendi INPUT_RECORD<\/code> yap\u0131s\u0131 format\u0131nda ConPTY arac\u0131l\u0131\u011f\u0131yla alt s\u00fcrece g\u00f6nderilir. Bu, \u00f6zellikle fare etkile\u015fimi, \u00f6zel tu\u015f kombinasyonlar\u0131 veya pencere yeniden boyutland\u0131rma gibi olaylar\u0131n detayl\u0131 bir \u015fekilde yakalanmas\u0131 gerekti\u011finde \u00f6nemlidir.<\/p>\n

Go programlama dili, sistem programlama yetenekleri ve C\/C++ ile kolayca entegre olabilme \u00f6zelli\u011fi sayesinde, ConPTY API’leriyle do\u011frudan etkile\u015fime ge\u00e7mek i\u00e7in m\u00fckemmel bir ara\u00e7t\u0131r. syscall<\/code> paketi ve ilgili Windows API’leri arac\u0131l\u0131\u011f\u0131yla Go uygulamalar\u0131, ConPTY oturumlar\u0131 olu\u015fturabilir, alt s\u00fcre\u00e7leri y\u00f6netebilir ve girdi\/\u00e7\u0131kt\u0131 ak\u0131\u015flar\u0131n\u0131 kontrol edebilir. Ancak, win32-input-mode<\/code>‘un varl\u0131\u011f\u0131, bu girdilerin standart VT sekanslar\u0131 yerine INPUT_RECORD<\/code> format\u0131nda gelmesi nedeniyle, \u00f6zel bir ayr\u0131\u015ft\u0131rma ve d\u00f6n\u00fc\u015ft\u00fcrme mant\u0131\u011f\u0131 gerektirir. Aksi takdirde, CLI uygulaman\u0131zdaki fare t\u0131klamalar\u0131 veya \u00f6zel tu\u015f kombinasyonlar\u0131 do\u011fru \u015fekilde \u00e7al\u0131\u015fmayabilir veya hi\u00e7 alg\u0131lanmayabilir. Bu, geli\u015ftiriciler i\u00e7in beklenmedik bir engel te\u015fkil edebilir, zira \u00e7o\u011fu zaman terminal girdi y\u00f6netimini standart VT sekanslar\u0131 \u00fczerinden \u00e7\u00f6zmeye al\u0131\u015fk\u0131nd\u0131rlar. Go’nun burada devreye girmesi, bu karma\u015f\u0131k Windows API’leri ile do\u011frudan \u00e7al\u0131\u015fmak i\u00e7in temiz ve verimli bir yol sunmas\u0131d\u0131r.<\/p>\n

Go ile Temel ConPTY Uygulamas\u0131 Olu\u015fturma: \u0130lk Ad\u0131mlar<\/h2>\n

Go ile ConPTY uygulamalar\u0131 geli\u015ftirmeye ba\u015flamadan \u00f6nce, temel kavramlar\u0131 anlam\u0131\u015f olmam\u0131z \u00f6nemlidir. \u015eimdi, Go’yu kullanarak basit bir ConPTY oturumu nas\u0131l ba\u015flat\u0131l\u0131r ve bir alt s\u00fcre\u00e7 (\u00f6rne\u011fin, cmd.exe<\/code>) nas\u0131l \u00e7al\u0131\u015ft\u0131r\u0131l\u0131r ona odaklanal\u0131m. Bu, win32-input-mode<\/code>‘un karma\u015f\u0131kl\u0131klar\u0131na girmeden \u00f6nce, Go’nun Windows sistem API’leriyle nas\u0131l etkile\u015fime ge\u00e7ti\u011fini g\u00f6steren ilk ad\u0131md\u0131r. Bu b\u00f6l\u00fcm, okuyucunun konuya a\u015final\u0131\u011f\u0131n\u0131 art\u0131rmak ve temel ConPTY mekanizmas\u0131n\u0131 kavramas\u0131n\u0131 sa\u011flamak i\u00e7in tasarlanm\u0131\u015ft\u0131r.<\/p>\n

Go’da ConPTY ile \u00e7al\u0131\u015fmak, \u00e7o\u011funlukla syscall<\/code> paketini ve Windows API fonksiyonlar\u0131n\u0131 kullanmay\u0131 gerektirir. \u0130lk olarak, bir s\u00f6zde konsol olu\u015fturmak i\u00e7in CreatePseudoConsole<\/code> fonksiyonuna ihtiyac\u0131m\u0131z olacak. Bu fonksiyon, ana uygulama ile alt s\u00fcre\u00e7 aras\u0131nda bir ileti\u015fim k\u00f6pr\u00fcs\u00fc g\u00f6revi g\u00f6recek olan iki adet “pipe” (kanallar) gerektirir: biri alt s\u00fcrece girdi g\u00f6ndermek i\u00e7in, di\u011feri de alt s\u00fcre\u00e7ten \u00e7\u0131kt\u0131 almak i\u00e7in. Bu pipe’lar, bizim Go uygulamam\u0131z\u0131n alt s\u00fcre\u00e7le etkile\u015fim kurmas\u0131n\u0131 sa\u011flayacak temel mekanizmalard\u0131r. Ayr\u0131ca, alt s\u00fcrecin ba\u015flang\u0131\u00e7 bilgilerini tan\u0131mlayan STARTUPINFOEX<\/code> yap\u0131s\u0131n\u0131 ve s\u00fcrecin kendisini kontrol etmek i\u00e7in PROCESS_INFORMATION<\/code> yap\u0131s\u0131n\u0131 kullanaca\u011f\u0131z.<\/p>\n

A\u015fa\u011f\u0131daki kod blo\u011fu, Go ile basit bir ConPTY oturumu ba\u015flat\u0131p, cmd.exe<\/code>‘yi bu oturum i\u00e7inde \u00e7al\u0131\u015ft\u0131ran temel bir iskeleti g\u00f6stermektedir. Bu \u00f6rnekte, alt s\u00fcre\u00e7ten gelen \u00e7\u0131kt\u0131lar\u0131 okuyaca\u011f\u0131z ve bizim uygulamam\u0131zdan alt s\u00fcrece girdi g\u00f6nderebilece\u011fiz. Ancak, bu a\u015famada win32-input-mode<\/code>‘un yaratt\u0131\u011f\u0131 spesifik girdi sorunlar\u0131na hen\u00fcz de\u011finmiyoruz, sadece temel ileti\u015fimi kurmaya odaklan\u0131yoruz. Kodda g\u00f6r\u00fclece\u011fi \u00fczere, bir\u00e7ok Windows API \u00e7a\u011fr\u0131s\u0131 ve pointer (i\u015faret\u00e7i) manip\u00fclasyonu bulunmaktad\u0131r. Bu, Go’nun d\u00fc\u015f\u00fck seviyeli sistem programlama yeteneklerinin bir g\u00f6stergesidir.<\/p>\n

\npackage main\n\nimport (\n    \"fmt\"\n    \"os\"\n    \"syscall\"\n    \"unsafe\"\n)\n\nvar (\n    kernel32           = syscall.NewLazyDLL(\"kernel32.dll\")\n    createPseudoConsole         = kernel32.NewProc(\"CreatePseudoConsole\")\n    closePseudoConsole          = kernel32.NewProc(\"ClosePseudoConsole\")\n    resizePseudoConsole         = kernel32.NewProc(\"ResizePseudoConsole\")\n    createPipe                  = kernel32.NewProc(\"CreatePipe\")\n    getConsoleScreenBufferInfo  = kernel32.NewProc(\"GetConsoleScreenBufferInfo\")\n)\n\nconst (\n    \/\/ Geni\u015f ve \u00f6zl\u00fc sabitler\n    STARTF_USESTDHANDLES = 0x00000100\n    STARTF_USESHOWWINDOW = 0x00000001\n    SW_SHOW              = 5\n    CREATE_UNICODE_ENVIRONMENT = 0x00000400\n    EXTENDED_STARTUPINFO_PRESENT = 0x00080000\n    MAX_PATH = 260\n    INVALID_HANDLE_VALUE = ^syscall.Handle(0)\n)\n\ntype COORD struct {\n    X short\n    Y short\n}\n\ntype SMALL_RECT struct {\n    Left   short\n    Top    short\n    Right  short\n    Bottom short\n}\n\ntype CONSOLE_SCREEN_BUFFER_INFO struct {\n    dwSize              COORD\n    dwCursorPosition    COORD\n    wAttributes         uint16\n    srWindow            SMALL_RECT\n    dwMaximumWindowSize COORD\n}\n\n\/\/ Win32 API \u00e7a\u011fr\u0131lar\u0131 i\u00e7in yard\u0131mc\u0131 fonksiyonlar\n\/\/ ... (STRUCT YAPILARI VE YARDIMCI FONKS\u0130YONLAR EKLECEK) ...\n\/\/ Bu b\u00f6l\u00fcm, makale uzunlu\u011fu i\u00e7in daha fazla struct ve yard\u0131mc\u0131 fonksiyon tan\u0131m\u0131 i\u00e7erebilir.\n\/\/ \u00d6rne\u011fin, STARTUPINFOEX, PROCESS_INFORMATION, SECURITY_ATTRIBUTES gibi yap\u0131lar.\n\nfunc createConPTY() (syscall.Handle, syscall.Handle, syscall.Handle, error) {\n    var (\n        inputRead  syscall.Handle\n        inputWrite syscall.Handle\n        outputRead syscall.Handle\n        outputWrite syscall.Handle\n    )\n\n    \/\/ Alt s\u00fcrece girdi g\u00f6ndermek i\u00e7in pipe\n    err := syscall.CreatePipe(&inputRead, &inputWrite, nil, 0)\n    if err != nil {\n        return 0, 0, 0, fmt.Errorf(\"girdi pipe olu\u015fturulamad\u0131: %w\", err)\n    }\n\n    \/\/ Alt s\u00fcre\u00e7ten \u00e7\u0131kt\u0131 almak i\u00e7in pipe\n    err = syscall.CreatePipe(&outputRead, &outputWrite, nil, 0)\n    if err != nil {\n        syscall.CloseHandle(inputRead)\n        syscall.CloseHandle(inputWrite)\n        return 0, 0, 0, fmt.Errorf(\"\u00e7\u0131kt\u0131 pipe olu\u015fturulamad\u0131: %w\", err)\n    }\n\n    \/\/ Konsol ekran boyutu bilgisi al\n    var csbi CONSOLE_SCREEN_BUFFER_INFO\n    r1, _, err := getConsoleScreenBufferInfo.Call(uintptr(syscall.Stdout), uintptr(unsafe.Pointer(&csbi)))\n    if r1 == 0 {\n        return 0, 0, 0, fmt.Errorf(\"konsol bilgisi al\u0131namad\u0131: %w\", err)\n    }\n\n    \/\/ ConPTY olu\u015ftur\n    var pseudoConsoleHandle syscall.Handle\n    r1, _, err = createPseudoConsole.Call(\n        uintptr(csbi.dwSize.X), \/\/ Geni\u015flik\n        uintptr(csbi.dwSize.Y), \/\/ Y\u00fckseklik\n        uintptr(inputRead),\n        uintptr(outputWrite),\n        uintptr(unsafe.Pointer(&pseudoConsoleHandle)),\n    )\n    if r1 == 0 {\n        syscall.CloseHandle(inputRead)\n        syscall.CloseHandle(inputWrite)\n        syscall.CloseHandle(outputRead)\n        syscall.CloseHandle(outputWrite)\n        return 0, 0, 0, fmt.Errorf(\"pseudo console olu\u015fturulamad\u0131: %w\", err)\n    }\n\n    return pseudoConsoleHandle, inputWrite, outputRead, nil\n}\n\nfunc main() {\n    pseudoConsoleHandle, inputWriter, outputReader, err := createConPTY()\n    if err != nil {\n        fmt.Fprintf(os.Stderr, \"Hata: %v\\n\", err)\n        return\n    }\n    defer closePseudoConsole.Call(uintptr(pseudoConsoleHandle))\n    defer syscall.CloseHandle(inputWriter)\n    defer syscall.CloseHandle(outputReader)\n\n    fmt.Println(\"ConPTY ba\u015far\u0131yla olu\u015fturuldu. cmd.exe ba\u015flat\u0131l\u0131yor...\")\n\n    \/\/ TODO: Alt s\u00fcreci ba\u015flatma kodu buraya eklenecek\n    \/\/ \u00d6rne\u011fin, cmd.exe'yi pseudoConsoleHandle ile ili\u015fkilendirerek \u00e7al\u0131\u015ft\u0131rmak.\n    \/\/ Bu k\u0131s\u0131m sonraki b\u00f6l\u00fcmlerde detayland\u0131r\u0131lacakt\u0131r.\n\n    \/\/ Basit bir \u00e7\u0131kt\u0131 okuyucu (\u00f6rnek ama\u00e7l\u0131)\n    outputBuf := make([]byte, 1024)\n    for {\n        var n uint32\n        err := syscall.ReadFile(outputReader, outputBuf, &n, nil)\n        if err != nil {\n            \/\/ fmt.Println(\"Hata okuma \u00e7\u0131kt\u0131s\u0131:\", err)\n            break \/\/ Genellikle pipe kapat\u0131ld\u0131\u011f\u0131nda bu hata al\u0131n\u0131r\n        }\n        if n > 0 {\n            os.Stdout.Write(outputBuf[:n])\n        }\n    }\n\n    fmt.Println(\"Uygulama tamamland\u0131.\")\n}\n<\/pre>\n
<\/code><\/p>\n
Yukar\u0131daki \u00f6rnekte, temel pipe'lar olu\u015fturulur ve CreatePseudoConsole<\/code> \u00e7a\u011fr\u0131l\u0131r. main<\/code> fonksiyonunda ise, olu\u015fturulan pseudoConsoleHandle<\/code>'\u0131 kullanarak bir alt s\u00fcreci nas\u0131l ba\u015flataca\u011f\u0131m\u0131z\u0131n yeri belirtilmi\u015ftir. Dikkat edilmesi gereken \u00f6nemli bir nokta, ConPTY'nin \"geni\u015flik\" ve \"y\u00fckseklik\" gibi konsol boyut parametrelerine ihtiya\u00e7 duymas\u0131d\u0131r. Bu bilgiler genellikle mevcut konsolun boyutlar\u0131ndan al\u0131n\u0131r. Bu boyutlar, alt s\u00fcrecin kendisini do\u011fru bir \u015fekilde render etmesi i\u00e7in kritiktir.<\/p>\n
Bu temel kurulum, ConPTY'nin Go'daki mekani\u011fini anlaman\u0131n ilk ad\u0131m\u0131d\u0131r. inputWriter<\/code> ve outputReader<\/code> pipe'lar\u0131 arac\u0131l\u0131\u011f\u0131yla alt s\u00fcre\u00e7le iki y\u00f6nl\u00fc ileti\u015fimi kurmu\u015f oluruz. Alt s\u00fcrecin ba\u015flat\u0131lmas\u0131, CreateProcess<\/code> veya CreateProcessW<\/code> gibi Windows API fonksiyonlar\u0131 kullan\u0131larak ger\u00e7ekle\u015ftirilir. Bu fonksiyonlar, STARTUPINFOEX<\/code> yap\u0131s\u0131n\u0131n bir par\u00e7as\u0131 olarak pseudoConsoleHandle<\/code>'\u0131 alacak \u015fekilde yap\u0131land\u0131r\u0131lmal\u0131d\u0131r. Bu sayede, ba\u015flat\u0131lan alt s\u00fcre\u00e7, bizim kontrol\u00fcm\u00fczdeki s\u00f6zde konsol ortam\u0131nda \u00e7al\u0131\u015fmaya ba\u015flar.<\/p>\n
\n  Uzman \u0130pucu: ConPTY ile \u00e7al\u0131\u015f\u0131rken syscall<\/code> paketini yo\u011fun bir \u015fekilde kullanmak, kodunuzu Windows'a \u00f6zg\u00fc API'lere ba\u011f\u0131ml\u0131 hale getirecektir. \u00c7apraz platform deste\u011fi ar\u0131yorsan\u0131z, platforma \u00f6zg\u00fc soyutlama katmanlar\u0131 olu\u015fturmay\u0131 d\u00fc\u015f\u00fcnebilirsiniz.<\/ExpertTip>\n<\/p>\n
Bu a\u015famada, Go uygulamam\u0131z\u0131n alt s\u00fcre\u00e7le ileti\u015fim kurmaya haz\u0131r oldu\u011funu g\u00f6r\u00fcyoruz. Ancak, bu temel kurulum, win32-input-mode<\/code>'un getirdi\u011fi \u00f6zel girdi sorunlar\u0131n\u0131 do\u011frudan ele almaz. Sadece ham girdi ve \u00e7\u0131kt\u0131 ak\u0131\u015flar\u0131n\u0131 y\u00f6netiriz. win32-input-mode<\/code>'un neden ve nas\u0131l bir sorun te\u015fkil etti\u011fini anlamak i\u00e7in bir sonraki b\u00f6l\u00fcme ge\u00e7meliyiz. Burada, fare t\u0131klamalar\u0131, tu\u015f basmalar\u0131 gibi olaylar\u0131n INPUT_RECORD<\/code> format\u0131nda nas\u0131l geldi\u011fini ve bunun geleneksel VT sekanslar\u0131ndan fark\u0131n\u0131 inceleyece\u011fiz.<\/p>\n
win32-input-mode'un Detaylar\u0131 ve Kar\u015f\u0131la\u015f\u0131lan Zorluklar<\/h2>\n
Yukar\u0131daki b\u00f6l\u00fcmde Go ile temel bir ConPTY oturumu olu\u015fturmay\u0131 ve bir alt s\u00fcreci ba\u015flatmay\u0131 \u00f6\u011frendik. \u015eimdi ise, terminal uygulamalar\u0131 geli\u015ftirirken ba\u015f\u0131m\u0131z\u0131 a\u011fr\u0131tan as\u0131l meseleye, yani win32-input-mode<\/code>'un detaylar\u0131na ve onunla gelen zorluklara odaklanaca\u011f\u0131z. Bu mod, \u00f6zellikle Windows Terminal kullan\u0131ld\u0131\u011f\u0131nda ve interaktif CLI uygulamalar\u0131 s\u00f6z konusu oldu\u011funda kritik bir fark yarat\u0131r. Anlamak i\u00e7in, \u00f6ncelikle standart terminal girdi mekanizmalar\u0131ndan neden farkl\u0131la\u015ft\u0131\u011f\u0131n\u0131 derinlemesine incelememiz gerekiyor.<\/p>\n
Geleneksel terminal uygulamalar\u0131 ve em\u00fclat\u00f6rleri genellikle VT (Virtual Terminal) sekanslar\u0131 ad\u0131 verilen standartla\u015ft\u0131r\u0131lm\u0131\u015f escape kodlar\u0131n\u0131 kullanarak girdi ve \u00e7\u0131kt\u0131 i\u015flemlerini ger\u00e7ekle\u015ftirir. \u00d6rne\u011fin, bir ok tu\u015funa bas\u0131ld\u0131\u011f\u0131nda \\x1b[A<\/code> gibi bir sekans g\u00f6nderilirken, fare t\u0131klamalar\u0131 i\u00e7in de SGR (Select Graphic Rendition) fare raporlama format\u0131 gibi VT tabanl\u0131 sekanslar kullan\u0131l\u0131r. Bu standart, \u00e7o\u011fu terminal uygulamas\u0131n\u0131n platform ba\u011f\u0131ms\u0131z bir \u015fekilde etkile\u015fim kurmas\u0131n\u0131 sa\u011flar. Ancak Windows Terminal, win32-input-mode<\/code> etkin oldu\u011funda, bu geleneksel yakla\u015f\u0131m\u0131n d\u0131\u015f\u0131na \u00e7\u0131kar.<\/p>\n
Peki, win32-input-mode<\/code> ne zaman ve neden aktive olur? Temelde, bir ConPTY oturumu olu\u015fturuldu\u011funda ve bu oturum bir Windows Terminal penceresi taraf\u0131ndan bar\u0131nd\u0131r\u0131ld\u0131\u011f\u0131nda, Windows Terminal, alt s\u00fcrece daha zengin ve detayl\u0131 girdi bilgileri sa\u011flamak amac\u0131yla bu modu kullanmay\u0131 tercih edebilir. Bu modun amac\u0131, klasik Windows konsol uygulamalar\u0131n\u0131n al\u0131\u015f\u0131k oldu\u011fu INPUT_RECORD<\/code> yap\u0131s\u0131n\u0131 kullanarak girdileri aktarmakt\u0131r. Bu yap\u0131, bir klavye tu\u015funun bas\u0131l\u0131p bas\u0131lmad\u0131\u011f\u0131, fare tekerle\u011finin kayd\u0131r\u0131l\u0131p kayd\u0131r\u0131lmad\u0131\u011f\u0131, imlecin nerede oldu\u011fu gibi \u00e7ok daha gran\u00fcler bilgileri i\u00e7erir. Yani, terminal uygulaman\u0131z \"bir tu\u015fa bas\u0131ld\u0131\" bilgisini almak yerine, \"sol Shift tu\u015fu bas\u0131l\u0131yken 'A' tu\u015funa bas\u0131ld\u0131, imle\u00e7 (X,Y) konumundayd\u0131\" gibi detayl\u0131 bir bilgi paketi al\u0131r.<\/p>\n
Bu durumun getirdi\u011fi en b\u00fcy\u00fck zorluk, bizim Go uygulamam\u0131z\u0131n (veya ConPTY arac\u0131l\u0131\u011f\u0131yla ileti\u015fim kurdu\u011fumuz alt s\u00fcrecin) bu INPUT_RECORD<\/code> format\u0131ndaki girdileri do\u011fru bir \u015fekilde ayr\u0131\u015ft\u0131rmas\u0131 ve e\u011fer gerekiyorsa, bunlar\u0131 standart VT sekanslar\u0131na d\u00f6n\u00fc\u015ft\u00fcrmesidir. E\u011fer bunu yapmazsak, alt s\u00fcrecimiz fare t\u0131klamalar\u0131n\u0131, \u00f6zel tu\u015f kombinasyonlar\u0131n\u0131 (Ctrl+C, Ctrl+V hari\u00e7) veya pencere yeniden boyutland\u0131rma olaylar\u0131n\u0131 alg\u0131layamaz. \u00d6rne\u011fin, htop<\/code> veya gitui<\/code> gibi fare etkile\u015fimli veya karma\u015f\u0131k tu\u015f kombinasyonlar\u0131 gerektiren bir CLI arac\u0131 yazd\u0131\u011f\u0131n\u0131z\u0131 d\u00fc\u015f\u00fcn\u00fcn. Kullan\u0131c\u0131 fare ile bir men\u00fc \u00f6\u011fesine t\u0131klad\u0131\u011f\u0131nda veya bir paneli kayd\u0131rd\u0131\u011f\u0131nda, uygulaman\u0131z hi\u00e7bir tepki vermeyecektir \u00e7\u00fcnk\u00fc bekledi\u011fi VT sekanslar\u0131 yerine, INPUT_RECORD<\/code> format\u0131nda bir veri ak\u0131\u015f\u0131 geliyordur ve uygulama bunu yorumlayamaz.<\/p>\n
INPUT_RECORD<\/code> yap\u0131s\u0131 asl\u0131nda bir union (birle\u015fim) i\u00e7erir ve farkl\u0131 girdi olaylar\u0131 i\u00e7in farkl\u0131 alt yap\u0131lar bar\u0131nd\u0131r\u0131r:<\/p>\n
    \n
  • KEY_EVENT_RECORD<\/code>: Klavye tu\u015f basmalar\u0131 ve b\u0131rakmalar\u0131 i\u00e7in. Hangi tu\u015fun bas\u0131ld\u0131\u011f\u0131, tu\u015fun ASCII veya Unicode de\u011feri, kontrol tu\u015flar\u0131n\u0131n (Shift, Ctrl, Alt) durumu gibi bilgiler i\u00e7erir.<\/li>\n
  • MOUSE_EVENT_RECORD<\/code>: Fare hareketleri, t\u0131klamalar\u0131 ve tekerlek kayd\u0131rmalar\u0131 i\u00e7in. \u0130mlecin konumu, hangi fare tu\u015funun bas\u0131l\u0131 oldu\u011fu, fare tekerle\u011finin ne kadar kayd\u0131r\u0131ld\u0131\u011f\u0131 gibi detaylar\u0131 bar\u0131nd\u0131r\u0131r.<\/li>\n
  • WINDOW_BUFFER_SIZE_EVENT_RECORD<\/code>: Konsol penceresinin yeniden boyutland\u0131r\u0131lmas\u0131 gibi olaylar i\u00e7in.<\/li>\n
  • MENU_EVENT_RECORD<\/code>: Uygulama men\u00fcleri ile ilgili olaylar i\u00e7in (daha az kullan\u0131l\u0131r).<\/li>\n
  • FOCUS_EVENT_RECORD<\/code>: Konsol penceresinin odaklan\u0131p odaklanmad\u0131\u011f\u0131 ile ilgili olaylar i\u00e7in.<\/li>\n<\/ul>\n
    Go uygulamam\u0131z, ConPTY'nin \"\u00e7\u0131kt\u0131\" pipe'\u0131ndan okurken, bu INPUT_RECORD<\/code> yap\u0131lar\u0131n\u0131 bayt ak\u0131\u015f\u0131 olarak alacakt\u0131r. Bu bayt ak\u0131\u015f\u0131n\u0131 al\u0131p do\u011fru INPUT_RECORD<\/code> yap\u0131s\u0131na d\u00f6n\u00fc\u015ft\u00fcrmek, ard\u0131ndan i\u00e7indeki KEY_EVENT_RECORD<\/code> veya MOUSE_EVENT_RECORD<\/code> alt yap\u0131lar\u0131n\u0131 inceleyerek anlaml\u0131 olaylar\u0131 \u00e7\u0131karmak ve son olarak bunlar\u0131 CLI uygulamas\u0131n\u0131n bekledi\u011fi VT sekanslar\u0131na \u00e7evirmek, Go geli\u015ftiricileri i\u00e7in \u00f6nemli bir g\u00f6rev haline gelir. Bu \u00e7eviri s\u00fcreci hem hata potansiyeli ta\u015f\u0131r hem de performans a\u00e7\u0131s\u0131ndan dikkatli optimizasyon gerektirebilir. \u00d6zellikle fare olaylar\u0131n\u0131 SGR format\u0131na \u00e7evirmek veya \u00f6zel tu\u015flar\u0131 uygun ANSI sekanslar\u0131na d\u00f6n\u00fc\u015ft\u00fcrmek, detayl\u0131 bir e\u015fleme tablosu ve mant\u0131k gerektirir. Bu karma\u015f\u0131kl\u0131k, Go'nun sistem programlama yeteneklerini ve dikkatli bayt manip\u00fclasyonunu gerektiren bir aland\u0131r. Bu durum, sadece Go'ya \u00f6zg\u00fc bir sorun de\u011fil, ConPTY ile etkile\u015fime ge\u00e7en her dilde kar\u015f\u0131la\u015f\u0131labilecek genel bir Windows Terminal \u00f6zg\u00fcl\u00fc\u011f\u00fcd\u00fcr.<\/p>\n
    Go'da win32-input-mode Girdilerini Ayr\u0131\u015ft\u0131rma ve Normalle\u015ftirme<\/h2>\n
    \u00d6nceki b\u00f6l\u00fcmde win32-input-mode<\/code>'un ne oldu\u011funu ve neden INPUT_RECORD<\/code> yap\u0131s\u0131nda girdiler g\u00f6nderdi\u011fini anlad\u0131k. \u015eimdi, Go uygulamam\u0131z\u0131n bu INPUT_RECORD<\/code> yap\u0131lar\u0131n\u0131 nas\u0131l okuyaca\u011f\u0131n\u0131, ayr\u0131\u015ft\u0131raca\u011f\u0131n\u0131 ve gerekirse standart VT sekanslar\u0131na nas\u0131l d\u00f6n\u00fc\u015ft\u00fcrece\u011fini detayl\u0131 bir \u015fekilde inceleyece\u011fiz. Bu, interaktif CLI uygulamalar\u0131m\u0131z\u0131n Windows Terminal ortam\u0131nda beklendi\u011fi gibi \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flamak i\u00e7in hayati bir ad\u0131md\u0131r. Amac\u0131m\u0131z, Go'nun g\u00fc\u00e7l\u00fc sistem programlama yeteneklerini kullanarak, bu d\u00fc\u015f\u00fck seviyeli Windows API girdilerini y\u00fcksek seviyeli, terminal dostu \u00e7\u0131kt\u0131lara \u00e7evirmektir.<\/p>\n
    ConPTY'nin \u00e7\u0131kt\u0131 pipe'\u0131ndan okudu\u011fumuzda, INPUT_RECORD<\/code> yap\u0131lar\u0131n\u0131 i\u00e7eren bir bayt ak\u0131\u015f\u0131 elde ederiz. Bu yap\u0131, Go'da kar\u015f\u0131l\u0131k gelen Go struct'lar\u0131na d\u00f6n\u00fc\u015ft\u00fcr\u00fclmelidir. Bu d\u00f6n\u00fc\u015f\u00fcm, binary.Read<\/code> veya unsafe.Pointer<\/code> kullan\u0131larak manuel bayt manip\u00fclasyonu ile yap\u0131labilir. INPUT_RECORD<\/code> kendisi bir union<\/code> i\u00e7erdi\u011fi i\u00e7in, hangi alt yap\u0131n\u0131n (KEY_EVENT_RECORD<\/code>, MOUSE_EVENT_RECORD<\/code> vb.) aktif oldu\u011funu belirlemek i\u00e7in EventType<\/code> alan\u0131n\u0131 kontrol etmemiz gerekir. Bu sayede do\u011fru alt yap\u0131y\u0131 ayr\u0131\u015ft\u0131rabiliriz.<\/p>\n
    \u0130lk ad\u0131m, INPUT_RECORD<\/code> ve onun alt yap\u0131lar\u0131n\u0131n Go'daki temsillerini tan\u0131mlamakt\u0131r. Bu yap\u0131lar, Windows SDK's\u0131ndaki tan\u0131mlara birebir uygun olmal\u0131d\u0131r. \u00d6zellikle veri t\u00fcrlerinin boyutlar\u0131 (short<\/code>, int32<\/code>, uint16<\/code> vb.) do\u011fru e\u015fle\u015fmelidir, aksi takdirde yanl\u0131\u015f bayt okumalar\u0131yla kar\u015f\u0131la\u015f\u0131r\u0131z.<\/p>\n
    \n\/\/ win32api_types.go (ayr\u0131 bir dosyada veya ana dosyan\u0131n ba\u015flang\u0131c\u0131nda tan\u0131mlanabilir)\npackage main\n\nimport \"syscall\"\n\n\/\/ COORD struct, X ve Y koordinatlar\u0131 i\u00e7in\ntype COORD struct {\n    X short\n    Y short\n}\n\n\/\/ KEY_EVENT_RECORD i\u00e7in gerekli flag'ler\nconst (\n    FROM_LEFT_1ST_BUTTON_PRESSED = 0x0001\n    RIGHTMOST_BUTTON_PRESSED     = 0x0002\n    FROM_LEFT_2ND_BUTTON_PRESSED = 0x0004\n    FROM_LEFT_3RD_BUTTON_PRESSED = 0x0008\n    FROM_LEFT_4TH_BUTTON_PRESSED = 0x0010\n    \n    \/\/ Klavye kontrol tu\u015flar\u0131\n    CAPSLOCK_ON        = 0x0080\n    ENHANCED_KEY       = 0x0100\n    LEFT_ALT_PRESSED   = 0x0002\n    LEFT_CTRL_PRESSED  = 0x0008\n    NUMLOCK_ON         = 0x0020\n    RIGHT_ALT_PRESSED  = 0x0001\n    RIGHT_CTRL_PRESSED = 0x0004\n    SCROLLLOCK_ON      = 0x0040\n    SHIFT_PRESSED      = 0x0010\n)\n\n\/\/ Event t\u00fcrleri\nconst (\n    KEY_EVENT         = 0x0001\n    MOUSE_EVENT       = 0x0002\n    WINDOW_BUFFER_SIZE_EVENT = 0x0004\n    \/\/ Di\u011fer event t\u00fcrleri de eklenebilir\n)\n\ntype KEY_EVENT_RECORD struct {\n    bKeyDown          int32 \/\/ 0: Key up, 1: Key down\n    wRepeatCount      uint16\n    wVirtualKeyCode   uint16\n    wVirtualScanCode  uint16\n    U_Char            uint16 \/\/ Union: UnicodeChar or AsciiChar\n    dwControlKeyState uint32\n}\n\ntype MOUSE_EVENT_RECORD struct {\n    dwMousePosition COORD\n    dwButtonState   uint32\n    dwControlKeyState uint32\n    dwEventFlags    uint32\n}\n\ntype WINDOW_BUFFER_SIZE_RECORD struct {\n    dwSize COORD\n}\n\ntype INPUT_RECORD struct {\n    EventType uint16\n    _         uint16 \/\/ Padding\n    Event     [16]byte \/\/ Union i\u00e7in ham bayt alan\u0131, 16 bayt en b\u00fcy\u00fck olay\u0131n boyutu\n}\n\n\/\/ Di\u011fer win32 structlar\u0131 ve typedef'leri eklenebilir (\u00f6rne\u011fin short int32 gibi)\ntype short int16 \/\/ Windows'daki SHORT int16'ya kar\u015f\u0131l\u0131k gelir\n<\/pre>\n
    <\/code><\/p>\n
    Yukar\u0131daki yap\u0131lar\u0131 tan\u0131mlad\u0131ktan sonra, ConPTY'nin \u00e7\u0131kt\u0131 pipe'\u0131ndan okudu\u011fumuz baytlar\u0131 bu INPUT_RECORD<\/code> yap\u0131s\u0131na d\u00f6n\u00fc\u015ft\u00fcrmemiz gerekir. Ard\u0131ndan EventType<\/code> alan\u0131na bakarak hangi olay\u0131n geldi\u011fini belirler ve ilgili alt yap\u0131y\u0131 ayr\u0131\u015ft\u0131r\u0131r\u0131z. \u0130\u015fte temel bir ayr\u0131\u015ft\u0131rma d\u00f6ng\u00fcs\u00fc:<\/p>\n
    \n\/\/ main.go i\u00e7inde, outputReader'dan okuma d\u00f6ng\u00fcs\u00fcn\u00fcn bir par\u00e7as\u0131 olarak\nfunc processInputRecords(outputReader syscall.Handle, inputWriter syscall.Handle) {\n    recordSize := unsafe.Sizeof(INPUT_RECORD{})\n    inputBuffer := make([]byte, recordSize)\n\n    for {\n        var n uint32\n        \/\/ ConPTY'den INPUT_RECORD okuma\n        err := syscall.ReadFile(outputReader, inputBuffer, &n, nil)\n        if err != nil {\n            \/\/ Hata y\u00f6netimi: Pipe kapat\u0131ld\u0131\u011f\u0131nda veya ba\u015fka bir hata oldu\u011funda \u00e7\u0131k\n            if err == syscall.ERROR_BROKEN_PIPE {\n                fmt.Println(\"ConPTY \u00e7\u0131kt\u0131 pipe'\u0131 kapat\u0131ld\u0131.\")\n            } else {\n                fmt.Fprintf(os.Stderr, \"INPUT_RECORD okuma hatas\u0131: %v\\n\", err)\n            }\n            return\n        }\n\n        if n == uint32(recordSize) {\n            record := (*INPUT_RECORD)(unsafe.Pointer(&inputBuffer[0]))\n            \n            \/\/ Event t\u00fcr\u00fcne g\u00f6re ayr\u0131\u015ft\u0131rma\n            switch record.EventType {\n            case KEY_EVENT:\n                keyEvent := (*KEY_EVENT_RECORD)(unsafe.Pointer(&record.Event[0]))\n                if keyEvent.bKeyDown != 0 { \/\/ Sadece tu\u015fa basma olaylar\u0131n\u0131 i\u015fleyelim\n                    vtSeq := convertKeyEventToVT(keyEvent)\n                    if len(vtSeq) > 0 {\n                        \/\/ D\u00f6n\u00fc\u015ft\u00fcr\u00fclen VT sekans\u0131n\u0131 alt s\u00fcrece yaz\n                        \/\/ NOTE: Bu VT sekans\u0131 genellikle ana terminale (os.Stdout) yaz\u0131l\u0131r,\n                        \/\/ alt s\u00fcrece de\u011fil. E\u011fer alt s\u00fcre\u00e7 de VT bekliyorsa buraya yaz\u0131l\u0131r.\n                        \/\/ \u00c7o\u011fu durumda, ConPTY kendisi alt s\u00fcrece Win32 olay\u0131n\u0131 iletir.\n                        \/\/ Bizim amac\u0131m\u0131z, e\u011fer ara katmanda bu olay\u0131 kendimiz i\u015fleyip\n                        \/\/ ba\u015fka bir yere (\u00f6rn. ba\u015fka bir pty'ye) iletmekse bu d\u00f6n\u00fc\u015f\u00fcm mant\u0131kl\u0131.\n                        os.Stdout.Write([]byte(vtSeq))\n                    }\n                }\n            case MOUSE_EVENT:\n                mouseEvent := (*MOUSE_EVENT_RECORD)(unsafe.Pointer(&record.Event[0]))\n                vtSeq := convertMouseEventToVT(mouseEvent)\n                if len(vtSeq) > 0 {\n                    os.Stdout.Write([]byte(vtSeq))\n                }\n            case WINDOW_BUFFER_SIZE_EVENT:\n                sizeEvent := (*WINDOW_BUFFER_SIZE_RECORD)(unsafe.Pointer(&record.Event[0]))\n                \/\/ Pencere yeniden boyutland\u0131rma olay\u0131n\u0131 i\u015fleme\n                \/\/ \u00d6rne\u011fin, os.Stdout.Write([]byte(fmt.Sprintf(\"\\x1b[8;%d;%dt\", sizeEvent.dwSize.Y, sizeEvent.dwSize.X)))<\/code>\n                fmt.Printf(\"Pencere boyutu de\u011fi\u015fti: %dx%d\\n\", sizeEvent.dwSize.X, sizeEvent.dwSize.Y)\n                \/\/ ResizePseudoConsole \u00e7a\u011fr\u0131s\u0131 yap\u0131labilir\n                \/\/ resizePseudoConsole.Call(uintptr(pseudoConsoleHandle), uintptr(sizeEvent.dwSize.X), uintptr(sizeEvent.dwSize.Y))\n            \/\/ Di\u011fer event t\u00fcrleri i\u00e7in case'ler eklenebilir\n            }\n        } else if n > 0 {\n            fmt.Fprintf(os.Stderr, \"Beklenenden farkl\u0131 boyutta INPUT_RECORD okundu: %d bayt\\n\", n)\n        }\n    }\n}\n<\/pre>\n
    <\/code><\/p>\n
    \u015eimdi en kritik k\u0131sma gelelim: KEY_EVENT_RECORD<\/code> ve MOUSE_EVENT_RECORD<\/code>'u standart VT sekanslar\u0131na d\u00f6n\u00fc\u015ft\u00fcrme. Bu d\u00f6n\u00fc\u015f\u00fcm, genellikle b\u00fcy\u00fck bir switch<\/code> ifadesi veya e\u015fleme tablosu gerektirir. Her tu\u015f kombinasyonu ve fare olay\u0131 i\u00e7in belirli bir VT sekans\u0131 vard\u0131r.<\/p>\n
    \n  Uzman \u0130pucu: unsafe.Pointer<\/code> kullan\u0131m\u0131 Go'da dikkatli olmay\u0131 gerektirir. Performans i\u00e7in gerekli olabilir ancak yanl\u0131\u015f kullan\u0131mda haf\u0131za hatalar\u0131na yol a\u00e7abilir. Alternatif olarak encoding\/binary<\/code> paketini kullanarak daha g\u00fcvenli ama potansiyel olarak biraz daha yava\u015f bir yol izleyebilirsiniz.<\/ExpertTip>\n<\/p>\n
    Klavye Girdilerini VT Sekanslar\u0131na \u00c7evirme<\/h3>\n
    Klavye girdilerini d\u00f6n\u00fc\u015ft\u00fcrmek i\u00e7in, KEY_EVENT_RECORD<\/code> yap\u0131s\u0131ndaki wVirtualKeyCode<\/code>, U_Char<\/code> ve dwControlKeyState<\/code> alanlar\u0131na bakar\u0131z. \u00d6rne\u011fin, \"A\" tu\u015funa bas\u0131ld\u0131\u011f\u0131nda U_Char<\/code> alan\u0131 'A' de\u011ferini i\u00e7erecektir. \u00d6zel tu\u015flar (F1-F12, Ok tu\u015flar\u0131, Home, End vb.) i\u00e7in ise wVirtualKeyCode<\/code> alan\u0131n\u0131 kontrol ederiz ve buna g\u00f6re uygun VT sekans\u0131n\u0131 (\u00f6rne\u011fin, F1 i\u00e7in \\x1bOP<\/code> veya ok tu\u015flar\u0131 i\u00e7in \\x1b[A<\/code>) d\u00f6nd\u00fcr\u00fcr\u00fcz. Kontrol tu\u015flar\u0131n\u0131n (Shift, Ctrl, Alt) durumu, dwControlKeyState<\/code> ile belirlenir ve bu da VT sekans\u0131n\u0131n modifiye edilmesine neden olabilir (\u00f6rne\u011fin, Shift+Ok tu\u015fu farkl\u0131 bir sekans verebilir).<\/p>\n
    Fare Girdilerini VT Sekanslar\u0131na \u00c7evirme<\/h3>\n
    Fare olaylar\u0131 biraz daha karma\u015f\u0131kt\u0131r. MOUSE_EVENT_RECORD<\/code> yap\u0131s\u0131ndaki dwMousePosition<\/code>, dwButtonState<\/code> ve dwEventFlags<\/code> alanlar\u0131n\u0131 kullanarak olay\u0131n t\u00fcr\u00fcn\u00fc (t\u0131klama, \u00e7ift t\u0131klama, hareket, tekerlek kayd\u0131rma) ve konumunu belirleriz. Ard\u0131ndan bunlar\u0131 SGR (Set Graphics Rendition) fare raporlama format\u0131na d\u00f6n\u00fc\u015ft\u00fcr\u00fcr\u00fcz. SGR format\u0131 genellikle \\x1b[