Replies: 3 comments 4 replies
-
You will probably need to issue |
Beta Was this translation helpful? Give feedback.
-
Now that I think of it, modifying existing notification arguments makes no sense, as change of window index will very likely cause change in other windows' indices as well. Which means window move would trigger number of TBD notifications (e.g. It is however unfortunate that some window moves wouldn't trigger any notifications whatsoever, e.g. |
Beta Was this translation helpful? Give feedback.
-
@nicm trying to add a new notification for window reorder/index change event; would you be so kind and point me to roughly right place where to look at? Naively thought it's at session_renumber_windows(), but this part is not even called by say cmd_swap_window_exec(). In fact I can't comprehend currently where the swap flow causes indices to be updated. As for the new notification, I'm thinking there are 2 somewhat reasonable options:
Am I on a reasonable path here? |
Beta Was this translation helpful? Give feedback.
-
I'm working on a script that keeps state of some very basic tmux data, such as attached clients, their sessions & windows. To update this state it's consuming various notifications via the control mode.
However when re-ordering windows within a given session, the only notification received is
%session-window-changed
, which contains no index data. Same notification is also fired whenever viewed/active windows are changed in the session.Or am I approaching it in too high detail and should just request
list-windows
with a format containing all the needed data with each and every notification, effectively refreshing the whole state snapshot as opposed to trying to keep it up-to-date incrementally?Unrelated to window index notification, but there are other notifications that feel like should be there. One that comes to mind is when a new client is started/attached, only notification fired is
%client-session-changed
Beta Was this translation helpful? Give feedback.
All reactions