TheBloke
2018-08-27 23:38:38 UTC
Hi all
I'm running latest iTerm 2, version 3.2.0, on Mac OS 10.13.6.
I use a PC-style keyboard, with UK layout. My # key is therefore in a
different place to a Mac keyboard, and US style. I use an app called
Karabiner-Elements to remap the keys such that I can get # on the correct
keyboard key. This remapping works by sending Alt+3 when I press that key
- pressing Alt+3 being another way to get # in Mac OS.
This works in all apps except iTerm 2 shells. In my iTerm2 shells,
pressing my # key, or just hitting Alt+3, does nothing. So I have no way
to type a #, which is a rather important symbol in a shell. It does work
elsewhere in iTerm2, eg I can type # in a search box in the Preferences
pane.
I've been using iTerm2 with this keyboard for a couple of years, and this
only became a problem quite recently. I don't know exactly when it stopped
working, but I did a couple of iTerm2 upgrades in the last month or two, so
I assume it started then (I wasn't using iTerm2 daily at the time I did the
upgrades, so only spotted it a little later.)
Is there any way I can fix this? The only normal setting related to the
Alt key I could find is changing it to Meta or Esc+ - I did try changing
that, to no avail. I also looked through Advanced, and tried changing
settings such as "On keyboards that require a modifier to press a digit.."
and "When you press an arrow key .. that transmits the modifiers, should
Alt be translated to Meta", but again with no success.
I guess the basic issue is probably that iTerm2 is always sending the Alt
to the remote terminal, whereas I need it to process itself in order to
create the #?
Thanks in advance for any help. Let me know if I should raise a bug/issue
instead.
TB.
I'm running latest iTerm 2, version 3.2.0, on Mac OS 10.13.6.
I use a PC-style keyboard, with UK layout. My # key is therefore in a
different place to a Mac keyboard, and US style. I use an app called
Karabiner-Elements to remap the keys such that I can get # on the correct
keyboard key. This remapping works by sending Alt+3 when I press that key
- pressing Alt+3 being another way to get # in Mac OS.
This works in all apps except iTerm 2 shells. In my iTerm2 shells,
pressing my # key, or just hitting Alt+3, does nothing. So I have no way
to type a #, which is a rather important symbol in a shell. It does work
elsewhere in iTerm2, eg I can type # in a search box in the Preferences
pane.
I've been using iTerm2 with this keyboard for a couple of years, and this
only became a problem quite recently. I don't know exactly when it stopped
working, but I did a couple of iTerm2 upgrades in the last month or two, so
I assume it started then (I wasn't using iTerm2 daily at the time I did the
upgrades, so only spotted it a little later.)
Is there any way I can fix this? The only normal setting related to the
Alt key I could find is changing it to Meta or Esc+ - I did try changing
that, to no avail. I also looked through Advanced, and tried changing
settings such as "On keyboards that require a modifier to press a digit.."
and "When you press an arrow key .. that transmits the modifiers, should
Alt be translated to Meta", but again with no success.
I guess the basic issue is probably that iTerm2 is always sending the Alt
to the remote terminal, whereas I need it to process itself in order to
create the #?
Thanks in advance for any help. Let me know if I should raise a bug/issue
instead.
TB.
--
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-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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-discuss+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.