1

a newbie here.

I just installed kitty on wsl kali-linux, I am using win-kex to use a GUI. When I launch kitty opens on another window "outside" the winkex instance: like a Windows app. So, how can I make kitty work "inside" the winkex session?

Right, the winkex session. Left, the kitty window on windows.

The message after call kitty is:

ignoreboth or ignorespace present in bash HISTCONTROL setting, showing running command in window title will not be robust

Improve this question
3
  • It's not clear what you're trying to do here, or even what's happening. I know Kitty as a terminal emulator, so I'm guessing your trying to open a terminal between the host and the emulated Windows environment. I can't tell which direction you're trying to connect, or the nature of your problem. You need to clarify what you expect to happen here. Ideally, if you know what they mean, you should also use more specific terms to explain what's actually happening now, such as those here: kali.org/docs/wsl/win-kex. Commented Aug 21, 2023 at 4:32
  • 1
    Oh, @BryKKan, I'm so sorry. I was trying to use kali on wsl and trying to make it work like a native system (Cant' install kali as native system becasue need windows for engineering tools and have a little storage space). So the "issue " here was that kitty was oppening in other window and not "inside" the win-kex instance. I totaly forgot about the other win-kex modes . Launch a winkex instance on enhanced session mode solved the "issue". Thank you so much. I'll make an edit and add the answer that you gave me. Commented Aug 21, 2023 at 5:46
  • Great! You did great with the answer too! Just don't forget to edit a bit of the details from your comment back into the original question. Makes it a little more useful to others coming by later if they don't have to read the comments first to understand whether they're having the same problem. Commented Aug 21, 2023 at 6:50

1 Answer 1

Reset to default
1

On win-kex docummentation here (thanks to @BryKKan on comments) the "problem" is solved launching win-kex enhanced session mode (--esm):

kex --esm --sound

After that Kitty and all tools open inside the instance alike the native system.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.