kitty
No description set
- Developed at X11:terminals
- Sources inherited from project openSUSE:Factory
-
4
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/kitty && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
fix-librsync-leap.patch | 0000001261 1.23 KB | |
kitty-0.26.2.tar.gz | 0006048093 5.77 MB | |
kitty.changes | 0000100853 98.5 KB | |
kitty.spec | 0000004179 4.08 KB | |
optional-disable-docs.patch | 0000002160 2.11 KB |
Revision 11 (latest revision is 40)
Dominique Leuenberger (dimstar_suse)
accepted
request 1001194
from
Michael Vetter (jubalh)
(revision 11)
- Update to 0.26.2: * Allow creating overlay-main windows, which are treated as the active window unlike normal overlays (#5392) * hints kitten: Allow using The launch command as the program to run, to open the result in a new kitty tab/window/etc. (#5462) * hyperlinked_grep kitten: Allow control over which parts of rg output are hyperlinked (#5428) * Fix regression in 0.26.0 that caused launching kitty without working STDIO handles to result in high CPU usage and prewarming failing (#5444) * The launch command: Allow setting the margin and padding for newly created windows (#5463) * hints kitten: hyperlink matching: Fix hints occasionally matching text on subsequent line as part of hyperlink (#5450) * Fix a regression in 0.26.0 that broke mapping of native keys whose key codes did not fit in 21 bits (#5452) * Wayland: Fix remembering window size not accurate when client side decorations are present * Fix an issue where notification identifiers were not sanitized leading to code execution if the user clicked on a notification popup from a malicious source.
Comments 2
Not sure how or why, but after the rebuild with gcc 12 kitty does something weird for me. Almost randomly freezes or forces to hang my keyboard, and it stops working until I unplug and plug it back. Tried 4 different cables with the same keyboard, and another 2. Got a pretty large (~8GB) debug log from it, not sure if I should open a bug report or bring it upstream so I will just a post a link to it here: https://drive.google.com/file/d/124tmeTheFMebT5ZUk-gGSOAKmT6pYu7n/view?usp=sharing.
Setting
sync_to_monitor no
seem to solve the issue. Weird, but I'm also ~~lazy~~ too busy to debug it further ^-^