<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>Keybindings - 标签 - William</title>
    <link>https://williamlfang.github.io/tags/keybindings/</link>
    <description>Keybindings - 标签 | William</description>
    <generator>Hugo -- gohugo.io</generator><language>zh-CN</language><lastBuildDate>Sat, 14 Nov 2026 18:49:28 &#43;0800</lastBuildDate><atom:link href="https://williamlfang.github.io/tags/keybindings/" rel="self" type="application/rss+xml" /><item>
  <title>Nested tmux over SSH: automatically route Ctrl-k to the remote</title>
  <link>https://williamlfang.github.io/2026-11-14-tmux-ssh-auto-prefix/</link>
  <pubDate>Sat, 14 Nov 2026 18:49:28 &#43;0800</pubDate>
  <author>william</author>
  <guid>https://williamlfang.github.io/2026-11-14-tmux-ssh-auto-prefix/</guid>
  <description><![CDATA[<div class="featured-image"><img loading="eager" src="https://williamlfang.github.io/2026-11-14-tmux-ssh-auto-prefix/featured-image.png" alt="Nested tmux over SSH: automatically route Ctrl-k to the remote" title="Keep Ctrl-k local by default, forward it to a matching remote tmux over SSH, and reserve Ctrl-b for local control." referrerpolicy="no-referrer"/></div><p>My local tmux and one remote tmux both used <code>Ctrl-k</code> as their prefix. After connecting over SSH, <code>Ctrl-k c</code> still created a <strong>local</strong> window. The local tmux consumed the prefix before SSH could send it to the server.</p>
<p>I wanted <code>Ctrl-k</code> to control the remote when its tmux also accepted <code>Ctrl-k</code>, but stay local for other servers. The working solution uses a pane-local flag and one SSH probe per login. <code>Ctrl-b</code> remains an always-local escape hatch.</p>]]></description>
</item>
</channel>
</rss>
