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

Use kitty as the main terminal emulator #21

Open
rdbo opened this issue Jul 13, 2024 · 5 comments
Open

Use kitty as the main terminal emulator #21

rdbo opened this issue Jul 13, 2024 · 5 comments

Comments

@rdbo
Copy link
Owner

rdbo commented Jul 13, 2024

kitty is fast, has ligatures, is actively developed, and is lightweight
The only problem I could think of is someone said it sends web requests when it starts to check for updates. I checked myself and I couldn't replicate that behavior, but I should double check before adding

@rdbo
Copy link
Owner Author

rdbo commented Jul 13, 2024

image
Looks like it can be easily disabled, so probably no big deal

@rdbo
Copy link
Owner Author

rdbo commented Jul 13, 2024

Another big problem, the startup is unbearably slow unfortunately
It takes me ~ 0.5s per instance, and I have a pretty good processor. Maybe this is not the terminal I've been looking for

@kovidgoyal
Copy link

kitty --single-instance will reduce that startup time for all subsequent instances to ~10 ms

@rdbo
Copy link
Owner Author

rdbo commented Jul 14, 2024

@kovidgoyal Thanks for replying! The --single-instance did improve the startup time
I think there is some sort of overhead though (maybe the way kitty is packaged on my distribution?), because running kitty --version takes basically the same time as running a normal instance
I also noticed that kitty is outdated on the Alpine Linux packages (0.31), could be that as well

~ $ time kitty -e sh -c exit
[196 08:11:45.750857] [glfw error 65544]: process_desktop_settings: failed with error: [org.freedesktop.DBus.Error.ServiceUnknown] The name org.freedesktop.portal.Desktop was not provided by any .service files

real  0m0.561s
user  0m0.454s
sys   0m0.108s
~ $ time kitty --single-instance -e sh -c exit

real  0m0.389s
user  0m0.314s
sys   0m0.073s
~ $ time kitty --version
kitty 0.31.0 created by Kovid Goyal

real  0m0.374s
user  0m0.317s
sys   0m0.056s

I'm gonna try upgrading it myself and see if I have issues on the latest version as well

@kovidgoyal
Copy link

The overhead comes from starting python, which is very slow on your
system for some reason, probably to do with bytecode invalidation.
In any case if you run the kitty nightly both
-version and --single-instance dont use python anymore.

time kitty --version                                                                                                            master 
kitty 0.35.2 created by Kovid Goyal

real	0.003
user	0.000
sys	0.002
maxmem	12 MB
faults	0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants