mrob95 on texmaker
Add basic TeXMaker support (compare)
mrob95 on master
Create requirements.txt (compare)
mrob95 on master
Create install.bat (compare)
mrob95 on master
change to \(\) for inline math,… add equation* and align* update docs and 2 more (compare)
mrob95 on master
mrob95 on breathe
Transition sublime and template Update dependencies Add install script and 2 more (compare)
mrob95 on master
Create LICENSE (compare)
mrob95 on master
Add core context (compare)
mrob95 on master
Add install script (compare)
mrob95 on master
Update dependencies (compare)
mrob95 on languages
Improve formatting (compare)
mrob95 on languages
Initial multilanguage support load to edit Further improvement and 1 more (compare)
mrob95 on master
Transition sublime and template (compare)
CCR is complicated, as you probably know, and I am more or less just hacking on top of caster's implementation.
There are some details on the mathfly site, but the the way it is all done is to merge everything that can be recognised in the current context into one rule, and then allow repetitions of that rule. The structure is something like
Rule(
Repetition(
Alternative(
Compound("command one"->action)
Compound("command two"->action)
Compound("command three"->action)
)
)
)
language
setting is equal to nld
. English will always be used as a fallback
Major architectural change. Before updating you will need to run
pip install dfly-breathe
I have entirely replaced the old caster-based CCR backend with Breathe, a library I've been working on. Should make it much easier to add support for new apps etc, and I have fully fleshed out the NestedRule
concept which was originally prototyped here. Please let me know if there are any issues.
Well basically I wanted rules that were like:
Integral from <stuff1> to <stuff2>
Where stuff was a sequence of any other ccr commands. Nested rules were the first implementation based on Caster, breathe allows this by allowing the user to add custom top-level rules. The mathfly examples are in e.g. lyx.py
at the bottom but may be slightly difficult to understand at a glance, there are clearer examples on the breathe readme which show greedy dictation and optional repeat values using the same feature.
CommandsRef
extra which references a sequence of commands and then include an Exec
action to execute the sequence
say <text>
command, which should allow you to input text without using Dragon dictation