Closed basbebe closed 3 years ago
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.md
does nothing.:attach
and then :new
does nothing (also :>
)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 https://github.com/alexherbo2/connect.kak/commit/09661989333b07f31c74b8cd3a0ec8db55a28718
update: not related to https://github.com/alexherbo2/connect.kak/commit/09661989333b07f31c74b8cd3a0ec8db55a28718
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 (https://github.com/alexherbo2/connect.kak/issues/53#issue-800619181).
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.
: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:I would have thought that this might be a kitty problem but since it works when not in
kak-shell
…