diff options
| author | Josh Rahm <joshuarahm@gmail.com> | 2022-04-20 00:56:29 -0600 |
|---|---|---|
| committer | Josh Rahm <joshuarahm@gmail.com> | 2022-10-09 12:19:46 -0600 |
| commit | 4319bde78b32d42d20b43c1ebd79095409db399e (patch) | |
| tree | c129e13ba41e497de67f87cc2fc27358d9cce5ae /src/Rahm/Desktop/XMobarLog.hs | |
| parent | c2d0c6b0b699513ede65ecef40d7afaccff53ee4 (diff) | |
| download | rde-4319bde78b32d42d20b43c1ebd79095409db399e.tar.gz rde-4319bde78b32d42d20b43c1ebd79095409db399e.tar.bz2 rde-4319bde78b32d42d20b43c1ebd79095409db399e.zip | |
Add macro support to WML.
Macros may be defined by using <M-d>
<M-d>w begins defining a windowset macro
<M-d>t begins defining a workspace macro
The next character typed is the key chord to save the macro to. The next
sequence of keys read up until the Return key is the macro value. This
macro may then be used as WML objects.
Macros are pretty primitive right now. I need to think about if it would
be worthwhile to make these macros either take arguments or add some
kind of state to WML a la sed to take a step to make the language Turing
complete, and if such a development would actually be desirable. If
anything it would be an academic exercise.
Diffstat (limited to 'src/Rahm/Desktop/XMobarLog.hs')
0 files changed, 0 insertions, 0 deletions