ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Better​Find​Next

by notbaab ST2/ST3

Sublime plugin for a better find next

Details

Installs

  • Total 316
  • Win 182
  • OS X 84
  • Linux 50
Dec 14 Dec 13 Dec 12 Dec 11 Dec 10 Dec 9 Dec 8 Dec 7 Dec 6 Dec 5 Dec 4 Dec 3 Dec 2 Dec 1 Nov 30 Nov 29 Nov 28 Nov 27 Nov 26 Nov 25 Nov 24 Nov 23 Nov 22 Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30
Windows 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 1 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1
OS X 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 1
Linux 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1

Readme

Source
raw.​githubusercontent.​com

BetterFindNext

A find next plugin that (attempts to) understand code.

Not found

BetterFindNext is aims to be a smarter version of the built in find_next (super+d) command. It achieves this by allowing the user to customize what scope gets ignored.

Default Key bindings and Behavior

By default, the shortcut maps to alt+i and ignores adding strings or comments.

Ignore Options

The key binding accepts a list of scopes as it's excluded_scopes args. For Example, if you want to not include constant scope, you would define a mapping like so

[
    {"keys": ["ctrl+i"], "command": "better_find_next", "args": {"excluded_scopes": ["constant"]}},
]

In a very contrived example, this would produce behavior like this.

Not found

TODO

Requests can be submitted in the issues. Current plans are - Limit find to current function - Limit find to current indentation - Allow included_scopes option (inverse of the current implementation)

Install

Search for BetterFindNext on Package Control