4 Commits

Include renames

Author	SHA1	Message	Date
ZacharyZhang-NY	3b5bf46093	T32: on Windows herdr's client is sought among the herdr.exe processes at or under the session's shell, none under another herdr, whose server and panes are its own; they are read when that list changes, and a server or a command beside the client is passed by, where round 1 found the server taken for the client	2026-10-16 16:38:45 -04:00
ZacharyZhang-NY	d7dc1af6b9	T32: on Windows the right column follows herdr's focused pane: the herdr.exe nearest under the session's shell, its arguments and variables read through sysinfo, its folder found as herdr finds it there, herdr's named pipe asked as herdr names it; on every system a herdr answer that lands after the shell reported a folder is dropped	2026-10-16 12:37:09 -04:00
ZacharyZhang-NY	2af45cbfb9	T29: the foreground is its group and the executable its leader runs, so exec herdr from a shell is followed and a program that did not read is tried again; a relative herdr socket lies in the client's folder; on Linux an executable an update replaced still names itself herdr	2026-10-16 03:19:13 -04:00
ZacharyZhang-NY	3e30f95543	T29: inside herdr the right column follows herdr's focused pane: herdr keeps its panes' OSC 7, so on macOS and Linux a session that finds herdr's client leading its pty's foreground reads the focused pane's folder from herdr's socket, found as herdr 0.9 finds it	2026-10-16 02:58:38 -04:00