MacOS – iTerm2 shell integration isn’t working

applicationsitermmacos

I am using iTerm2 3.0.15 beta on Sierra. I have had shell integration installed since many months ago. At some point, shell integration stopped working. (I'm not very observant; I just noticed it at some point. I'd been away for a while, too.) What I mean when I say it stopped working is that command history, recent directories, etc. sections of the Toolbelt are empty. Also, there are no mark indicators before the bash prompt.

I've been looking for a solution off and on for some weeks. I've tried manually sourcing $HOME/.iterm2_shell_integration.bash to make sure it was sourced and that it wasn't getting clobbered by something else in my setup. Just today, I upgraded to 3.1.6 beta 2, but shell integration is still not working.

Nothing has worked and I'm at a loss for where else to look for problems.

Best Answer

Had the same problem. Running this command fixed the problem to me:

curl -L https://iterm2.com/misc/install_shell_integration.sh | bash

It will re-install shell integration. You can found more details on the following link.

Related Solutions

MacOS – Clean Lion install, keeping Time Machine history

I think you'd be better off doing a clean install and using Setup Assistant to copy over just the users and settings. (Setup Assistant, like Migration Assistant, can use a Time Machine backup as the source. The are basically the same application, but Setup Assistant configures your Mac for the first time and Migration Assistant helps you copy stuff over to a Mac you've already set up. You can only use Setup Assistant immediately after a clean install of the OS, which of course includes the first time you boot up a new Mac.) That way for sure your new users will have the same UID and UUID as your current users, meaning your backup and all your other drives ownership and read/write permissions will still work as before, and there's a chance that the Time Machine interface will work to fetch old files. I wouldn't bet on the latter, but I've had permissions problems before when not migrating users. Of course, this might be different if all your machines only have one user; my machines have 3.

I'm pretty sure, also, that if Time Machine doesn't work straight off the bat, you can trick it into working by replacing the com.apple.TimeMachine.MachineID.plist file in the Time Capsule's sparsebundle disk image for the backup for the machine in question. But that's a bit advanced and certainly unsupported, so I'd leave that for "when all else fails".

Vim not working under iTerm2

Apparently, removing set lines=40 does the trick. The manual says:

    Number of lines of the Vim window.
    Normally you don't need to set this.  It is done automatically by the
    terminal initialization code

so be careful when you copy-paste ready configs, as I did :)

Best Answer

Related Solutions

MacOS – Clean Lion install, keeping Time Machine history

Vim not working under iTerm2

Related Question