iterm2 issueshttps://gitlab.com/gnachman/iterm2/-/issues2016-05-19T04:12:50Zhttps://gitlab.com/gnachman/iterm2/-/issues/2620Hotkey window doesn't open on Cmd+Tab2016-05-19T04:12:50ZGeorge NachmanHotkey window doesn't open on Cmd+Tab*By sbo\.\.\. on September 12, 2013 12:11 (imported from Google Code)*
---
*What steps will reproduce the problem?*
1. In preferences, enable hotkey window
2. Open hotkey window using the chosen KB shortcut
3. Cmd+Tab to another ...*By sbo\.\.\. on September 12, 2013 12:11 (imported from Google Code)*
---
*What steps will reproduce the problem?*
1. In preferences, enable hotkey window
2. Open hotkey window using the chosen KB shortcut
3. Cmd+Tab to another application
4. Cmd+Tab back to iTerm
*What is the expected output? What do you see instead?*
Expected: iTerm hotkey window opens
Actual: iTerm application activates (menubar shows active application is iTerm) but no window opens
*What version of the product are you using? On what operating system?*
iTerm 2 build 1.0.0.20130624 on MacOS 10.9 Mavericks DP7 (same issue present using MacOS 10.8.4 Mountain Lion).
*Please provide any additional information below.*
Clicking the dock icon doesn't open the existing hotkey window either.
Preference "closing hotkey window may switch spaces" doesn't changes this behavior
---
[com.googlecode.iterm2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-2620/comment-0/com.googlecode.iterm2.plist)Feature Complete 3.1https://gitlab.com/gnachman/iterm2/-/issues/1570Drop-down visor switches desktop in full screen mode under Lion2018-03-08T06:07:29ZGeorge NachmanDrop-down visor switches desktop in full screen mode under Lion*By hosheng.hs\.\.\. on November 01, 2011 21:39 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. Anchor iterm2 to Desktop 1
2. Enter full screen mode for a window
2. At the full-screen desktop,...*By hosheng.hs\.\.\. on November 01, 2011 21:39 (imported from Google Code)*
---
<b>What steps will reproduce the problem?</b>
1. Anchor iterm2 to Desktop 1
2. Enter full screen mode for a window
2. At the full-screen desktop, hit the hotkey for the visor window
3. Lion will animate the desktop switch and the visor dropdown
<b>What is the expected output? What do you see instead?</b>
GIVEN iterm2 in full screen mode
AND iterm2 anchored to desktop 1
AND Visor configured properly
AND I am on the full-screen iterm2 desktop
WHEN I hit the Visor hotkey
THEN the Visor should drop down without switching out of full screen mode
AND I should see my full screen terminal through a transparent visor background
<b>What version of the product are you using? On what operating system?</b>
iterm2 1.0.0.20111020
Lion 10.7.2
<b>Please provide any additional information below.</b>
This was sort of working in the previous version. I could drop down the visor window, move over to the full screen window, (with the dropped-down visor dragging over desktops) and the visor would pop in and out properly without switching desktops. This no longer happens in this current update (since I am exploiting a bug to make it do what I want). Having visor switch desktop completely breaks the purpose of having the visor overlay on top of the existing full-screen terminal.
Some other to note: I've anchored iterm2 to the first desktop. I would much prefer using it under fullscreen mode, but I'll either downgrade to an older version or try something else until this issue gets fixed.
---
[com.googlecode.iterm2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-1570/comment-0/com.googlecode.iterm2.plist)Feature Complete 3.1George NachmanGeorge Nachmanhttps://gitlab.com/gnachman/iterm2/-/issues/1516Show/hide hotkey uses raw keyboard keys, ignores keyboard layout2016-10-06T05:33:23ZGeorge NachmanShow/hide hotkey uses raw keyboard keys, ignores keyboard layout*By w\.\.\.@wisq.net on October 15, 2011 16:10 (imported from Google Code)*
---
The iTerm show/hide key does not respect keyboard layouts. When set, it attaches to a raw keyboard key — even though it appears to attach to a translated ...*By w\.\.\.@wisq.net on October 15, 2011 16:10 (imported from Google Code)*
---
The iTerm show/hide key does not respect keyboard layouts. When set, it attaches to a raw keyboard key — even though it appears to attach to a translated (mapped) key in the current layout. This causes problems when switching between keyboard layouts, or if using a device that remaps keyboards at the hardware level (even if I'm pressing the same logical key).
Steps to reproduce:
1. In System Preferences, select a keyboard layout — let's say Dvorak.
2. Set your iTerm show/hide key to some key — let's use command-(key next to tab).
3. iTerm will display the key you chose in the current keyboard layout. Using the above examples, it would now show "⌘'" (command-apostrophe).
4. Change keyboard layouts — let's go back to Qwerty.
5. Bring up the iTerm preferences. Notice that it still displays the key you chose.
6. Attempt to bring up iTerm using the displayed (logical) key. With the above examples, that would be command-apostrophe (key next to enter) in Qwerty. (Nothing happens.)
7. Attempt to bring up iTerm using the same keyboard (physical) key you set it up with. With the above examples, that would be command-(key next to tab), i.e. command-Q. (It works.)
8. Set your iTerm show/hide key to the same physical key. Notice how the displayed logical key changes, even though you're not actually changing the physical show/hide key. With the above examples, it would now display "⌘Q" instead of "⌘'", but nothing has really changed.
(FYI: "a" and "m" are the same in Dvorak and Qwerty, so if you want to test with different keys, don't use those two.)
Given that the iTerm preferences say that my key is set to <X>, I would expect that pressing the logical key <X>, in any layout, would be the trigger key. Instead, it really means "the physical key that maps to logical key <X> when your keyboard layout is set to the same layout as when you set this setting". Not entirely intuitive. :)
Running iTerm2 1.0.0.20110909 on OSX 10.6.8 Snow Leopard.
The full, long story:
I use Dvorak as my main keyboard layout. Usually, I run with a normal keyboard (e.g. the built-in Macbook keyboard) with Dvorak as my software keyboard layout (in System Preferences) — let's call this "software remapped".
Sometimes, I use a hardware device that remaps Qwerty to Dvorak at the hardware level. I type in Dvorak, but the computer sees me typing the same letters in Qwerty instead, and I set my software keyboard layout to Qwerty — call this "hardware remapped".
(This is useful for games, which often also bind to raw keyboard keys. Or for pair programming, where we want two USB keyboards, one in each layout. Or for attaching to a KVM switch that includes a hardware remapper. All of which are common scenarios for me.)
In software remapped mode, my global iTerm show/hide key is command-apostrophe (⌘'), where apostrophe is the key next to "tab". This works fine so long as I continue to use software-remapped mode.
If I switch to Qwerty (with no remapping), the keyboard layout changes, but the iTerm activation key remains the same. It's now command-Q (key next to tab), which shadows the existing Mac "quit" key. However, iTerm still shows it as "⌘'", ignoring the fact that it's really "⌘Q" now.
If I then enable hardware remapping, the raw keyboard keys change, meaning that I now have to actually enter command-Q in Dvorak rather than command-apostrophe. (That's like pressing command-X on Qwerty.)
Obviously, this makes it rather difficult to switch between the two remapping methods as needed, even though I'm essentially pressing the same key (command-apostrophe) at all times.
(You can probably imagine the looks I get when I tell my pair programmer that they should bring up the terminal using command-Q.)
I don't know if binding to a raw keyboard key is a fundamental limitation of being able to have a global show/hide key, but it's certainly confusing behaviour. Also, I'm guessing some users may prefer that the key not change based on keyboard layout, so if this is "fixed", it should probably be a toggle option.
---
[com.googlecode.iterm2.plist](https://storage.googleapis.com/google-code-attachments/iterm2/issue-1516/comment-0/com.googlecode.iterm2.plist)Feature Complete 3.1