lexxish

I was considering assuming the user spends most the time in command mode which means Caster commands would have to be overridden. Also, after doing some testing it looks like...

I have basic vim mode tracking and commands here https://gist.github.com/lexxish/1a9582f175119f36a508282a81761d2a I haven't had a chance to merge them into caster yet. You'd want the files vim_helper, vim_mode, vim_rule and you'd...

> Either way this will be a long-term goal as there's a lot of other pressing implementations such as Python three, cross-platform, reloading grammars and so on. This is something...

Yes it won't effect either of those. I will decouple it from Caster and build it just on top of dragonfly. Filter rules will still be in Caster's control.

I could see this being part of dragonfly or being its own module. However I would lean towards its own module that depends on dragonfly so that it can be...

Generally sounds like the right idea but one concern I have is if they are text files how can we represent extras? If they are kept as python files we...

My preference is still to use Python. This gives us syntax checking, highlighting and IDE tooling. It also allows for extras to be easily added into grammar standards [like they...

> You mean externalizing strings like it is in browser.py and symbolspecs py? Yes, to make commands consistent when they are used in more than rule, something like this may...

> I would prefer a mechanism for generating translations from existing grammars as seen with the dragonfly config implementation. Does mean we have to use it but a similar concept....

> From a code clarity perspective it is less clear if the grammar is defined as one string and replaced as another string elsewhere. Sorry I posted this by accident....