120
edits
Typing glyphs on Linux: Difference between revisions
Jump to navigation
Jump to search
→APL Keyboard Remains After Dyalog is Closed
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 174: | Line 174: | ||
=== Dyalog Overrides Current Keyboard Settings === | === Dyalog Overrides Current Keyboard Settings === | ||
Prior to version 18.2, Dyalog APL would override the current [https://www.x.org/wiki/XKB/ XKB] configuration to use the Meta ("Windows") key as the modifier for entering APL symbols. If the user manages their keyboard configuration manually using the techniques described on this page, this behavior can be quite troublesome. | |||
To run Dyalog in the terminal without overriding ("hijacking") the user keyboard configuration, run <code>dyalog</code> with the <code>-nokbd</code> option: | To run Dyalog in the terminal without overriding ("hijacking") the user keyboard configuration, run <code>dyalog</code> with the <code>-nokbd</code> option: | ||
| Line 194: | Line 194: | ||
=== APL Keyboard Remains After Dyalog is Closed === | === APL Keyboard Remains After Dyalog is Closed === | ||
Dyalog | Previous versions of Dyalog override the current keyboard configuration, as described in [[#Dyalog_Overrides_Current_Keyboard_Settings|this section]], but even using the default keyboard configuration by starting Dyalog 18.2 or later with | ||
<source lang=bash> | |||
dyalog --keyboard | |||
</source> | |||
fails to return the user to their previous keyboard configuration on exit. To solve this, create a custom [[wikipedia:Bash_(Unix_shell)|Bash]] script to save and revert keyboard settings upon exiting Dyalog APL:<ref>Adám Brudzewsky. [https://stackoverflow.com/questions/63431922/dyalog-apl-hijack-windows-key-and-do-not-give-it-back-fedora-32-gnome-free-lic/63433845#63433845 Stack Overflow answer]. 17 Aug, 2020</ref> | |||
<source lang=bash> | <source lang=bash> | ||