v1.7.0-next-25e23ae
You should put a valid kanata configuration within the configuration text box. You can see the kanata guide to learn about the configuration syntax.
To insert a Tab ('\t') character in the configuration text box, you can press Shift+Space.
'\t'
Some kanata configurations make use of files when using the real program. For example, in (include file.txt...) or for (defzippy-experimental zippycfg.txt ...). You can simulate files in the simulator. Start a line with: === file:... The text composing ... will be the filename. All text after the line — up until the end of the configuration or the next file definition — will be the content of the simulated file.
(include file.txt...)
(defzippy-experimental zippycfg.txt ...)
=== file:...
...
Example: (defsrc) (deflayermap (base) d @d) (include config-d.txt) (defzippy-experimental zippycfg.txt) === file:config-d.txt (defalias d (tap-hold 200 200 d lsft)) === file:zippycfg.txt abc alphabet
(defsrc) (deflayermap (base) d @d) (include config-d.txt) (defzippy-experimental zippycfg.txt) === file:config-d.txt (defalias d (tap-hold 200 200 d lsft)) === file:zippycfg.txt abc alphabet
You can use the recording functionality to automatically generate inputs. The recording will end on demand or after running for 30s. The input format is action:item. Valid actions are:
action:item
d | down
r | repeat
u | up
t | tick
The items for key up/down actions are a single key name like what you would use in defsrc. The items for tick actions are a single number representing the number of milliseconds to advance time by. Example: d:a t:50 u:a t:50 d:b t:50 u:b t:50 NOTE: The simulator behaves as if process-unmapped-keys is always set to yes. This cannot be turned off. This is unlike the real Kanata program where this configuration is off by default.
defsrc
d:a t:50 u:a t:50 d:b t:50 u:b t:50
process-unmapped-keys
yes