Pokey Rule
Pokey Rule
@wolfmanstout looks like this one is back on the table now that DFA improvements have shipped to public. Is it ready for review or were there other tweaks you wanted...
@wolfmanstout yeah I'd be inclined to add fields `excludeAnchor` and `excludeActive` to `lineNumber` target, pass through proper anchor and active rather than having them always equal, and handle things extension...
I view "and" as a nice-to-have, so I'm not sure we should block the PR on adding this, but cc @AndreasArvidsson who actually uses line numbers
Fair enough. @wolfmanstout if you do decide to take a crack at "and" in this PR, I think your proposal sounds reasonable. I'd make it so that `lineNumber` marks always...
I like your uncommented approach. I don't like the idea of keeping both old and new version of `lineNumber`, though. I'd argue for a migration, and only supporting the new...
Updated description to be more general
I think this PR is still a win, esp if the docs immediately tell you how to use the cheatsheet for those who were expecting old "cursorless help" behaviour
this one is waiting on #884
@paul-schaaf Cool colours! Feel free to add them to [the wiki](https://github.com/cursorless-dev/cursorless/wiki/Color-schemes). Prob worth mentioning what VSCode colour scheme you're using them with Also worth reporting back after you've been using...
We should probably add two newlines for "section", and one newline for "item" while we're here. Ideally we'd do #855, but let's get these 3 fixed as it should be...