Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kitty integration #627

Closed
tj57 opened this issue Mar 21, 2024 · 5 comments
Closed

Kitty integration #627

tj57 opened this issue Mar 21, 2024 · 5 comments
Assignees
Labels

Comments

@tj57
Copy link

tj57 commented Mar 21, 2024

What do you think about direct integration of kitty, so as to add another tab and run the kitty window inside the 1Remote window ?

Kitty has a lot of configuration options, ssh tunnels, X11 forwarding etc.

Like on this screeen ?
image

image

Another option is to autoimport files directly from Sessions with Kitty, only then you won't be able to edit them in 1Remote.
Create config file directly in kitty, autoimport to 1Remote and call it

@tj57 tj57 added the meta-feature New feature label Mar 21, 2024
@VShawn
Copy link
Member

VShawn commented Mar 21, 2024

Kitty has a lot of configuration options, ssh tunnels, X11 forwarding etc.
Like on this screeen ?

Because Kitty's configuration window and terminal window are two different windows, their HWNDs are different. Currently, 1Remote can only capture one HWND when integrating third-party programs, so itis difficult to achieve. At least I think the effort does not match the return. If that's the case, I would rather use KITTY's UI directly instead of the integrated one. Telemetry data also supports this view, with only a very small number of people using the 1Remote import kitty session feature.

Create config file directly in kitty, autoimport to 1Remote and call it

We can now import the kitty session but lack for auto import.

The reason we lack the ability to auto import session is that we do not know where to auto import the session files from. Users may use both the portable and non-portable versions of kitty, and the storage path of the session cannot be anticipated.

@tj57
Copy link
Author

tj57 commented Mar 27, 2024

Kitty has a lot of configuration options, ssh tunnels, X11 forwarding etc.
Like on this screeen ?

Because Kitty's configuration window and terminal window are two different windows, their HWNDs are different. Currently, 1Remote can only capture one HWND when integrating third-party programs, so itis difficult to achieve. At least I think the effort does not match the return. If that's the case, I would rather use KITTY's UI directly instead of the integrated one. Telemetry data also supports this view, with only a very small number of people using the 1Remote import kitty session feature.

If you're interested, I have an older version of PRemotem converted by a friend with added Kitty portable support and capture of both windows. I don't know much about C#, but I can make it available.

Create config file directly in kitty, autoimport to 1Remote and call it

We can now import the kitty session but lack for auto import.

The reason we lack the ability to auto import session is that we do not know where to auto import the session files from. Users may use both the portable and non-portable versions of kitty, and the storage path of the session cannot be anticipated.

Set retriction, if only one mode of import is available?
Import is avaliable only from selected directory and Sessions portable mode.

@VShawn
Copy link
Member

VShawn commented Apr 4, 2024

If you're interested, I have an older version of PRemotem converted by a friend with added Kitty portable support and capture of both windows. I don't know much about C#, but I can make it available.

Of course, I am happy to refer to any third-party implementations.

Oh, by the way, due to my scenario, I have never used SSH tunnels, X11 forwarding functions. so I am not familiar with their principles, which is also a barrier to me adding new SSH features.

Copy link

github-actions bot commented May 5, 2024

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label May 5, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants