I cannot speculate on what fraction of iTerm2 users enable this optional feature. Is it "many or most"? No idea.
I note that the article nowhere mentions the fact that the feature is optional. That would be a huge improvement.
We can disagree over whether the article is horribly written or not. My firm opinion is that it is.
> The rough model is:
> 1. iTerm2 launches SSH integration, usually through it2ssh.
> 2. iTerm2 sends a remote bootstrap script, the conductor, over the existing SSH session.
> 3. That remote script becomes the protocol peer for iTerm2.
How can I tell whether this "conductor" is running on the remote host or not?
I tried to reproduce this problem, following their instructions, but was unable to. I think but am not sure that's because my environment is pretty much nothing like one that would allow this to work.
For example, whether it's the default or not, my iTerm2 just doesn't have shell integration enabled. With my profile "Command:" set to "Login Shell," it doesn't look like I could enable it if I wanted to: "Load shell integration automatically" is disabled, apparently because "Automatic loading doesn't work with ksh."
This is explained in the article in the "The core bug" section.
