<p dir="auto">Both danish and faroese keyboard layouts uses Alt Gr-´ to print the pipe character "|" but the key binding resolver registers Alt Gr-´ as "ctrl-alt-["</p>
<p dir="auto">I tried adding the following rule to keymap.cson:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="'.workspace .editor:not(.mini)':
  'ctrl-alt-[': 'native!'"><pre class="notranslate"><code class="notranslate">'.workspace .editor:not(.mini)':
  'ctrl-alt-[': 'native!'
</code></pre></div>
<p dir="auto">But this causes atom to both fold the current line and print |. I tried changing it to</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="'.workspace .editor:not(.mini)':
  'ctrl-alt-[': 'notset!'"><pre class="notranslate"><code class="notranslate">'.workspace .editor:not(.mini)':
  'ctrl-alt-[': 'notset!'
</code></pre></div>
<p dir="auto">but that caused atom to neither fold or print the pipe.</p>
<p dir="auto">I've tried adding rules to ".workspace .editor", ".workspace" and "body" but no matter how much I fiddle around with the keymap.cson file I cannot get atom to consistently print | and not fold the current line.</p>
<p dir="auto">If I bind ctrl-alt-[ to something other than native! or notset! then atom consistently calls that command, but I cannot find any documentation about binding a keystroke pattern to print a specific character.</p>
<p dir="auto">I'm using Atom 0.136.0 on Windows 7 64bit</p>
<p dir="auto">Original issue: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="28529842" data-permission-text="Title is private" data-url="https://github.com/atom/atom/issues/1625" data-hovercard-type="issue" data-hovercard-url="/atom/atom/issues/1625/hovercard" href="https://github.com/atom/atom/issues/1625">atom/atom#1625</a></p>
<hr>
<p dir="auto">Use <a href="https://atom.io/packages/keyboard-localization" rel="nofollow">https://atom.io/packages/keyboard-localization</a> until this issue gets fixed (should be in the Blink upstream).</p>