Kitty: Default session interfering with panel kitten

[giftig]

I have a default session file which looks like this:

layout grid
cd ~/Code
title kitty
launch bash
launch bash
launch bash
launch bash

and I'm trying to run your simple panel kitten example:

kitty +kitten panel --lines 10 sh -c 'printf "\n\n\nHello, world."; sleep 5s'

but I've found it's invoking my session and assembling multiple gridded windows for me instead, with working prompts etc.

I tried to work around it like this:

kitty +kitten --session /dev/null panel --lines 10 sh -c 'printf "\n\n\nHello, world."; sleep 5s'

but adding --session seems to make it ignore the '+kitten' directive and just start a new terminal. I also tried -o startup_session=none, which gave me a "no such file or directory" error. Removing my session from my config file fixes the issue.

Incidentally I added --lines 10 to the example in your docs because if I leave it with a height of 1 row, my message seems to actually be printed off the top of the screen.

[kovidgoyal]

I cannot replicate this. Using the following command-line:

kitty +kitten panel -o startup_session=none --lines=10 sh -c "echo moooo; read"

shows me a panel with moooo
in it, even when adding startup_session to kitty.conf.

[giftig]

Guess it's not an issue if it works on your machine then.

[kovidgoyal]

Guess I have zero interest in hearing from you, ever again.

[Luflosi]

@giftig: @kovidgoyal could not replicate your issue, so he closed it. If he closes bug reports, that doesn't mean, that they are invalid or that he won't ever fix them. If they are or he won't fix them, he usually leaves a comment explaining that. He usually opens issues again or fixes them after the author of the bug report provided some more information or some steps that allow @kovidgoyal to reproduce the issue. If you think this is still an issue, you should be the one to come forward again and work together with him to fix your issue. But I can also kind of understand your (@giftig's) point of view. A closed bug report could signal that this won't be fixed. But instead of writing an unfriendly comment, you could have asked nicely why it was closed since it's still an issue for you.