I don’t personally use the official Dyalog IME for Microsoft Windows as my daily APL input method. My only complaints are that it forces me to use the Ctrl<\/kbd> key for APL input, which conflicts with conventional shortcuts for most applications, and for some reason it puts an additional item in my input method list because I have a Japanese input enabled, even though that is not a supported layout for the IME!<\/p>\n I am a fan of Ad\u00e1m’s AltGr keyboard for Windows<\/a> for a couple of reasons. It is based on the Microsoft Keyboard Layout Creator (MSKLC)<\/a>, and appears to work in newer Universal Windows Platform (UWP) apps and with the default On-Screen Keyboard on Windows. It also has accents and box-drawing characters<\/a>. However, support might be unreliable, because Microsoft do not officially support MSKLC on Windows 11, and there are rumoured issues with using it on ARM machines. Its main drawback is the limited choice of shifting keys, which can make it difficult to use with certain keyboard layouts or in certain applications. Personally, I am fond of using Caps Lock<\/kbd> as my primary APL shifting key, because it is rare these days that I need to TYPE A BUNCH OF THINGS IN ALL CAPITALS \u2013 it feels like shouting.<\/p>\n I used to do this by mapping Caps Lock<\/kbd> to Alt Gr<\/kbd> through some registry trickery. However, Kanata<\/a> allows me to use almost any keys I like. I now have Caps Lock<\/kbd> and Right Ctrl<\/kbd> as APL shifting keys. In addition, I can double-tap Caps Lock<\/kbd> to toggle it, so I can SHOUT OVER TEXT if I really need to. It’s cross-platform, so my single APL Kanata configuration gives me a consistent experience even when using my Linux virtual machine. There are still many features on my wish list for a comprehensive input method editor, but this is quite good for now (I wonder if anybody is able to adapt mozc<\/a> for APL?).<\/p>\n Whichever keyboard input method<\/a> you use, once you are not using Ctrl<\/kbd> for APL input you will be very glad to get back your beloved, conventional keyboard shortcuts for use in the Dyalog editor.<\/p>\n In the Dyalog IDE for Microsoft Windows, you can set keyboard shortcuts by selecting Options<\/strong>\u00a0>\u00a0Configure<\/strong> in the Session’s menu bar, then selecting the\u00a0Keyboard Shortcuts<\/strong> tab. From here, you can click on a code that corresponds to an action for which you want to set a shortcut.<\/p>\n These are keyboard shortcuts recognised by the Dyalog development environment.<\/p>\n I set:<\/p>\n To help find these in the list, click on the Code<\/strong> column title to put them in alphabetical order.<\/p>\n In Ride, only <FX> needs to be set, as the other shortcuts should default to this behaviour.<\/p>\n Having said all that, the official Dyalog IME still has features that would be invaluable especially if I were a brand new user. You can read about these in the Dyalog for Microsoft Windows UI guide<\/em><\/a>\u00a0and configure them using the IDE by going to Options<\/strong>\u00a0>\u00a0Configure<\/strong>\u00a0>\u00a0Unicode Input<\/strong>\u00a0>\u00a0Configure Layout<\/strong>. A little-known tip is that its backtick (also known as introducer<\/em> or prefix<\/em>) input method offers a searchable keyword menu, so that you can find glyphs by name or by the name of the function or operator it represents.<\/p>\n After setting the prefix introducer key to #<\/kbd> (octothorpe \/ hash), pressing twice and typing “rot” shows suggestions for the glyphs There’s also the wonderful overstrike feature. Once upon a time, APL was executed on remote machines accessed using the IBM Selectric Teletype typewriter; you can see this in this demonstration from 1975<\/a>. Certain characters would be composed by typing one symbol over another, such as printing a vertical bar ( Its basic usage is a feature of the IDE for Microsoft Windows; the IME isn’t required at all. If you press the Ins<\/kbd> key on your keyboard, it usually toggles “insert” or “overtype” mode. This is typically indicated by the vertical bar text cursor changing into an underbar. Typing will then replace existing text indicated by the cursor. With overstrikes enabled, APL glyphs can be created using other glyphs!<\/p>\n Insert<\/kbd>, Slash ( The IME allows you to use this in applications other than Dyalog by ticking Enable Overstrikes<\/strong> from the IME settings. You can read the documentation<\/a> to learn more, but the basic mechanism is to use the Overstrike Introducer Key<\/em> (default Ctrl<\/kbd>+Backspace<\/kbd>) followed by entering the two symbols to overstrike.<\/p>\n Settings menu for the Dyalog Input Method Editor<\/p><\/div>\n For this post I just wanted to highlight aspects of APL input beyond the simple defaults. For more about using your keyboard with Dyalog, see Ad\u00e1m’s blog post about enhanced debugging keys<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" In this blog post post I describe: how to use standard Ctrl keyboard shortcuts when using Dyalog on all platforms. little-known APL input features for Microsoft Windows. alternative input methods that do not use the Ctrl key for APL input. … Continue reading ![\"Dyalog](\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2025\/12\/shortcuts-win-ide-1.png\")
<\/p>\n\n
![\"\"](\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2025\/10\/ime-search.png\")
\u233d<\/code> and \u2296<\/code> with the keywords “rotate” and “rotatefirst”.<\/p><\/div>\n|<\/code>) over a circle (\u25cb<\/code>) to produce the circle-bar glyph for rotate\/reverse (\u233d<\/code>).<\/p>\n![\"APL](\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2025\/10\/overstrike.gif\")
\/<\/code>), LeftArrow<\/kbd>, Dash (-<\/code>), Circle (\u25cb<\/code>), LeftArrow<\/kbd>, Stile (|<\/code>)<\/p><\/div>\n![\"\"](\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2025\/12\/ime-config.png\")