Change behaviour with VS Code

[david.ste...@gmail.com]

I tend to load files into VS Code via the command-line, My starting point is to go into  a dec directory and type "code ."

This starts up VS Code, and loads the current directory into the file browser.

As of the latest iTerm2, it correctly starts up VS Code (or creates a new window if already open), but VS Code does not come to the front! This is new behaviour, and it's a right royal pain.  

$EDITOR is set to "/usr/local/bin/code -w", so when I need to add a git commit msg, I used to just do "git commit ..." and start typing. But now the typing isn't going to VS Code as it's no longer brought to the front.

In contrast, the Apple Terminal.app still behaves correctly, it opens VS Code and brings it to the front. Like iTerm2 used to.

An intentional change?  I hope not :)

Thanks for all your efforts on this fantastic tool.

[David Stevenson]

Typos, subject should be “Changed…” and “dec” should be “dev”…

--
You received this message because you are subscribed to the Google Groups "iterm2-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iterm2-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/iterm2-discuss/0e1b0a00-ec74-487a-aa39-7d414cb82c62n%40googlegroups.com.

[David Stevenson]

It seems like it's probably not a VS Code (or 'open') problem due to working ok with Apple's Terminal.app

Anyone else able to reproduce this, latest official releases of VS Code, macOS, and iTerm2?

[David Stevenson]

Same behaviour with TextMate 2 and latest iTerm2

[Richard Mitchell]

From reading the iTerm2 gitlab issues, several people are reporting similar issues - if they open another app with iTerm2 in the foreground, the other app is displayed underneath.  It also, if I have understood correctly, seems to be new to Monterey but specific to iTerm2 and not Terminal.  This suggests Apple has changed something in their API that requires a change in programs using it.

[George Nachman]

If you’re running the command at the command line, it’s unlikely that iTerm2 is responsible. Does Terminal.app exhibit the same behavior? Would it be any different if you did EDITOR=`open /usr/local/bin/code -w`?

To view this discussion on the web visit https://groups.google.com/d/msgid/iterm2-discuss/9af9fd9e-6779-4a80-a301-0da8fc6408f3n%40googlegroups.com.

[David Stevenson]

As I stated, it’s fine in Terminal.app

To view this discussion on the web visit https://groups.google.com/d/msgid/iterm2-discuss/CAB5Rqona%3DqPHK-RndOTnY-pGYj2PbFRj0Gy54f9_eV9kPx-2ZA%40mail.gmail.com.

[George Nachman]

The reason for this is that secure keyboard entry is turned on. It’s a menu item under iTerm2. This seems to be a change in Monterey, presumably for security purposes.

To view this discussion on the web visit https://groups.google.com/d/msgid/iterm2-discuss/CABU4iDVAxQ7PpYgo2TfrwOKb6wMBub%3DrADiehz1KM7Emu4d5Yw%40mail.gmail.com.