Moesasji

> This was unfortunately broken by an emacs update, and I have not gotten to fix it yet. Thanks for the report! In trying to figure out what goes wrong...

> I'm aware of this issue and thought about it briefly. It's not technically possible to have few home-environments, because each of them would define the same env variables, run...

> To summarize, the goal is still the same: have a simple, flexible highlighting scheme with the least amount of (long term) work for myself. If this can be accomplished...

Thanks for the clarification as this now makes sense to me; first step in this appears to be to make vis understand the new lexer format as just swapping out...

> First step in this appears to be to make vis understand the new lexer format as just swapping out a lexer looses the highlighting. Looking through the code I...

> I rebased our changes on top of the most recent upstream `lexer.lua` and pushed the result to the [scintillua branch](https://github.com/martanne/vis/tree/scintillua). It isn't really tested, but at least in theory...

> I am not really familiar with either environment, but don't they typically use the C++ lexers? Both would be editors that are popular in the gnome/xfce community, but a...

I think that the way this is done by [vis-seapeak](https://gitlab.com/SZanko/vis-peaksea) might be what you are looking for?

This patch works for me and makes vis behave the same as vim on this example for these two motions.

How is what you are asking for different from what the [vis-cursor](https://github.com/erf/vis-cursors) plugin as listed on the wiki already offers?