castles_made_of_sand wrote:You might get a cheap improvement by using the on_modified event instead.
Thanks for the input.
Using the on_modified event is what I originally was planning to use and the code that facelessuser provided. I switched to on_selection_modified because that was closer to the behavior I wanted. I knew that mouse-selection would be a disaster, but it doesn't bother me; I love scrolling with the keys with on_selection_modified. I have thought that it might be possible to put together a function (or series of functions) that centers the cursor on_modified, as well as every command that potentially moves the cursor up or down. But maybe that would be rewriting the on_selection_modified function
castles_made_of_sand wrote:`if view.match_selector(0, 'text.plain'): ...` can restrict to only text files.
Restricting it to text files or related syntaxes (markdown, textile etc.) is in the TODO, but it's a little more complicated than that. For this plugin to "work" properly, it needs a specific theme as well. And, as far as I can, tell plugins can't override a user's theme settings. (I derive this information from the fact that the "org mode" plugin doesn't do this, either.)
I'll take a look at 'Idle Watcher', but I think a second is maybe half-a-second too slow for this purpose.
phillip.koebbe wrote:I quickly noticed the issues with selection. That alone would be enough to keep me from using it while trying to work. It would drive me bonkers and be a major distraction.
Writing code with this plugin drives me
bonkers. But writing prose is a whole different beast.
To put it another way: what I call a line
when I write code, I call a paragraph
when I write prose. The semantic units are utterly different.