:new not working when in kak-shell
basbebe opened this issue · comments
:new command works fine normally.
But when I'm in kak-shell and :attach, then :new does nothing and I get this in debug buffer:
shell stderr: <<<
Traceback (most recent call last):
File "lib/python3.8/runpy.py", line 282, in run_path
File "lib/python3.8/runpy.py", line 87, in _run_code
File "__main__.py", line 127, in <module>
File "__main__.py", line 123, in main
File "__main__.py", line 23, in remote_control
File "kitty/remote_control.py", line 188, in main
File "kitty/remote_control.py", line 132, in do_io
File "kitty/utils.py", line 429, in __enter__
OSError: Failed to open controlling terminal: /dev/tty (identified with ctermid()) with error: Device not configured
>>>I would have thought that this might be a kitty problem but since it works when not in kak-shell…
update:
this is only true if I open the client from kak-shell:
❯ kak-shell
Kakoune sessions:
+ create new session
Kakoune session: kanto
~ 🐈 client0@kanto
❯ then:
*debug*
accepting connection failed: socket read failed: Bad file descriptor
remote client connected: 7
remote client disconnected: 7:o README.mddoes nothing.:attachand then:newdoes nothing (also:>)- both give the kitty error from above
If I open a new session (without being in kak-shell), I can open new clients, new terminals etc. without problem.
not checked yet if related to 0966198
update: not related to 0966198
tried around a bit more:
I cannot open new kak instances whan in kak-shell. I can only attach.
If the instance was being created by setsid, I get the error above (#53 (comment)).
If I create the session by e.g. sh -c 'kak -s test -d < /dev/null > /dev/null 2>&1 &' and then connect via kak-shell, the terminal window becomes unresponsive whenever I try to create a new client.
I have the impression connect.kak is broken.
Try in other terminals / OSes to see.
it does work in iterm2 w/ tmux.
So it might be a kitty thing (kitty itself / kakoune / connect ?)
(kakrc: https://github.com/basbebe/.dotfiles/blob/master/.config/kak/kakrc – might look familiar to you 😬)
funny thing:
If I open kitty from iterm w/tmux and open kak-shell in kitty, :new spawns new windows in iterm2 (tmux).
If I open kitty from apple terminal or iterm2 without tmux and do the same, I get the error.
If I switch terminal-mode to iterm, windows open in iterm again.
It may be due to the aliasing.
Type in Kakoune :terminal, you will see the terminal command that is used in the info box.
it's kitty-terminal in all cases
not quite: when opened through iterm/tmux, it shows tmux-terminal-horizontal, and if I change it manually with terminal-mode, it shows the corresponding setting, of course.