mcrmck 606aa1543e Fix multi-OS-window drag bugs and KeyError crash on tab drag
Two fixes:

1. boss.py: scope window drag is_dest to the receiving OS window only.
   Previously all tab managers got is_dest=True with the same window-local
   coordinates. Since every OS window's viewport starts at (0,0), a drag at
   (x,y) in Window 1 also matched windows in Window 2 at the same coords,
   causing spurious highlights and incorrect drop-target state in the second
   window.

2. tabs.py: filter synthetic tab IDs (< 0) from all_tabs in on_tab_drop_move.
   The '+' new-tab indicator uses tab_id=-1. If a tab drag started while
   window_drag_active or tab_bar_show_new_tab_button was set, the -1 ended
   up in tab_being_dropped.tab_ids, then tab_bar_data crashed with KeyError
   when it tried tmap[-1].
2026-03-23 21:44:48 -04:00
2026-03-07 09:33:39 +05:30
2026-03-17 20:14:02 +05:30
2026-03-16 17:38:14 +05:30
...
2026-03-12 13:48:20 +05:30
2026-02-24 07:47:22 +05:30
...
2026-03-17 08:22:45 +05:30
2026-01-20 17:09:01 +01:00

= kitty - the fast, feature-rich, cross-platform, GPU based terminal

If you live in the terminal, *kitty* is made for **you**!

See https://sw.kovidgoyal.net/kitty/[the kitty website].

image:https://github.com/kovidgoyal/kitty/workflows/CI/badge.svg["Build status", link="https://github.com/kovidgoyal/kitty/actions?query=workflow%3ACI"]

https://sw.kovidgoyal.net/kitty/faq/[Frequently Asked Questions]

To ask other questions about kitty usage, use either the https://github.com/kovidgoyal/kitty/discussions/[discussions on GitHub] or the
https://www.reddit.com/r/KittyTerminal[Reddit community]

Packaging status in various repositories:

image:https://repology.org/badge/vertical-allrepos/kitty-terminal.svg?columns=3&header=kitty["Packaging status", link="https://repology.org/project/kitty-terminal/versions"]
Description
No description provided
Readme GPL-3.0 157 MiB
Languages
Python 38.5%
C 28%
Go 26.4%
Objective-C 5.5%
Shell 1%
Other 0.5%