aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Albinus2016-10-20 14:57:17 +0200
committerMichael Albinus2016-10-20 14:57:17 +0200
commit38091c90005932017cbac54f2f5b82b3a003b9fa (patch)
tree8425544d683670f6c8961d9a95b57c15d9716c72
parent027c350e0cde1876f811b845cb10d3faa8f45665 (diff)
downloademacs-38091c90005932017cbac54f2f5b82b3a003b9fa.tar.gz
emacs-38091c90005932017cbac54f2f5b82b3a003b9fa.zip
Document, how to suppress iTerm2 shell integration in Tramp
* doc/misc/tramp.texi (Frequently Asked Questions): Suppress iTerm2 shell integration.
-rw-r--r--doc/misc/tramp.texi17
1 files changed, 15 insertions, 2 deletions
diff --git a/doc/misc/tramp.texi b/doc/misc/tramp.texi
index c3b54c612f0..d8a2beac405 100644
--- a/doc/misc/tramp.texi
+++ b/doc/misc/tramp.texi
@@ -2886,8 +2886,21 @@ end
2886@end group 2886@end group
2887@end example 2887@end example
2888 2888
2889When using WinSSHD on remote hosts, @value{tramp} do not recognize the 2889When using WinSSHD on remote hosts, @value{tramp} does not recognize
2890strange prompt settings. 2890the strange prompt settings.
2891
2892A similar problem exist with the iTerm2 shell integration, which sends
2893proprietary escape codes when starting a shell. This can be
2894suppressed by changing the respective integration snippet in your
2895@file{~/.profile} like this:
2896
2897@example
2898@group
2899[ $TERM = "dumb" ] || \
2900test -e "$@{HOME@}/.iterm2_shell_integration.bash" && \
2901source "$@{HOME@}/.iterm2_shell_integration.bash"
2902@end group
2903@end example
2891 2904
2892@item 2905@item
2893Echoed characters after login 2906Echoed characters after login