LexiconCode

> > > I have basic vim mode tracking and commands here [gist.github.com/lexxish/1a9582f175119f36a508282a81761d2a](https://gist.github.com/lexxish/1a9582f175119f36a508282a81761d2a) > > I haven't had a chance to merge them into caster yet. You'd want the files...

All right @lexxish FuncContext is now supported in Caster. FuncContext a dragonfly class that evaluates a given function with optional parameters for window title/executable, whose return value is interpreted as...

https://www.vim.org/ I'm willing to do this in collaboration with help. Someone could create the individual grammars consisting of one mode per file. Then I would be willing to do the...

Yes, function context gives us that functionality. What function context does is evaluate a function to true or false every utterance. If true, then the context and therefore rule becomes...

In a couple of days here, I'll come up with a minimum implementation that you guys can use to expand.

@Talos878 @lubyrex Here you go [vim_rules.zip](https://github.com/dictation-toolbox/Caster/files/7923822/vim_rules.zip). a minimum implementation that you guys can use to expand. Test from Run_Caster_Test_Engine.bat ``` enable vim ex # mode name eg. "normal mode, visual...

Temporarily addressed through conditional imports https://github.com/dictation-toolbox/Caster/commit/205b39a3b143081e2ff5bc11955b6a30219ffcf8 until a more elegant solution is devised. Does not cover edge cases as mentioned above like "eclipse2.py" with `alphabet_support.py`

Note: this also affects from `castervoice.rules.ccr.standard import SymbolSpecs` in `ccr`

That might be away without leveraging casters current system to override grammars. I'm actually hoping to tack on `get_support` to the current system.

I agree we could create a quick cheat sheet for dragonfly grammars similar to how it's already set up. Explain dragonfly first then caster additions.