MacOS kitty.conf listen_on and allow_remote_control only works on command line

[Chuanhuan]

Describe the bug
I use jukit vim and it need to set listen_on new kitty window.
The issue and screenshots also in here

To Reproduce
Steps to reproduce the behavior:

1. in kitty.conf

listen_on unix:$TMPDIR/kitty
allow_remote_control yes

2. open nvim in new kitty and split jukit window

E474: Unidentified byte: Error: open /dev/tty: device not configured^@
E474: Failed to parse Error: open /dev/tty: device not configured^@
E474: Failed to parse Error: open /dev/tty: device not configured^@

3. use command line in other terminal to call kitty
   kitty --listen-on=unix:$TMPDIR/kitty -o allow_remote_control=yes
4. In new kitty terminal, it's working

Issue
Why I must use command line manually instead of configure in kitty.conf ?

[kovidgoyal]

If you read the help of the listen_on configuration directive it will
tell you that when specified in the conf file the actual socket name
will be modified to include process pid since the configuration applies
to all kitty instances while the command line flag applies to a single
instance.

[Chuanhuan]

thx, I checked and don't know how to use actual socket name. Hopefully someone can post solution.