Differences between launch kitten and clone-in-kitty, clone-in-kitty confirmation, global user variables #8243
-
Hello!
|
Beta Was this translation helpful? Give feedback.
Answered by
kovidgoyal
Jan 21, 2025
Replies: 2 comments 2 replies
-
These are all answered in the docs. 1. neither sources .bashrc 2. allow_cloning 3. There are standard terminal escape codes you can use in any terminal to query information about colors, use them. Or use kitty remote control which has a get-colors command |
Beta Was this translation helpful? Give feedback.
2 replies
Answer selected by
kovidgoyal
-
On Tue, Jan 21, 2025 at 09:04:08AM -0800, Georgios Vlassis wrote:
1) In my .bashrc file I have a print statement which is run when I do kitten @ launch/clone-in-kitty (I can see the output of print, which is different for every invocation). How does this statement run if neither sources .bashrc? And if they do not run .bashrc what are they doing behind the scenes?
bash sources bashrc
3) The escape codes/get-colors are about getting colors (with predefined names, like background etc.). I want to retrieve arbitrary strings (e.g. var='test123'). Essentially, I am looking for something like "global" user vars (user vars for all the tabs). Alternatively, how would you go about setting a specific user var in every tab launched in kitty.conf?
Set an env var
4) Wait, this contradicts the docs. The launch action cannot copy live env vars, the launch kitten can (according to the docs+my experiments).
Yes, that's what I said. --copy-env does not access live env vars clone-in-kitty does.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These are all answered in the docs. 1. neither sources .bashrc 2. allow_cloning 3. There are standard terminal escape codes you can use in any terminal to query information about colors, use them. Or use kitty remote control which has a get-colors command