requesting screen size in pixels (esc[14t) doesn't work immediately after node script start on mac when stdin is in raw mode and focus events are enabled

[monsterkodi]

hello,

when i send the csi sequence esc[14t to stdout, the terminal reports the screen size in pixels on stdin as esc[4;h;wt
this doesn't work directly after the process started (at least on my mac).
if i delay the request for a few milliseconds it works as expected.
it would be nice if this would work immediately, like it does in kitty.

and btw: thanks for ghostty! it's awesome!

[00-kat]

How would one check this? I'm assuming adding a program which checks to one's shell configuration, but I'm not sure.

[monsterkodi]

i wrote a minimal test script. while doing it, i recognized that the terminal must be in raw mode and the focus events must be enabled for the problem to occur:

// these two are prerequisites for the problem to occur:

process.stdin.setRawMode(true)
process.stdout.write('\x1b[?1004h') // enable focus events  

process.stdout.write('\x1b[14t') // request screen size in pixels immediately, doesn't work in ghostty

//    setTimeout((function () // workaround: doing it after a delay does work
//    {
//        process.stdout.write('\x1b[14t')
//    }),10)

process.stdin.on('data',function (data)
{
    var csi = data.slice(1).toString('utf8')
    
    console.log('csi', csi) // this should print something like 'csi [4;2050;2222t'
    
    if (data.length === 1 && (data[0] === 0x1b || data[0] === 0x03)) // exit on esc or ctrl+c
    {
        process.exit()
    }
})

definitely a minor problem, but still would be nice to have consistent behaviour.

[00-kat]

When you say "process start" do you mean "Ghostty process start" or "terminal application process start"? If the latter, I can reproduce this, and if the former, your script is broken.

[monsterkodi]

i mean application (node or bun script) start.
and yes, the script is only done for reproducing that case :)

[mitchellh]

This is a known issue and is currently considered a "wontfix." I'm not sure the best way forward, but the reason this happens is because Ghostty initializes the pty concurrently to the GUI views, so initially we don't know our final size (an immediate resize happens usually).

The easiest solution would be to not initialize the pty until the view is fully laid out, but this would slow down our startup times and I'm not sure how I feel about that.

For now, registering for resize notifications and then requesting the size is the best option.