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

Better​Find​Next

by notbaab ALL

Sublime plugin for a better find next

Details

Installs

  • Total 577
  • Win 329
  • Mac 152
  • Linux 96
May 13 May 12 May 11 May 10 May 9 May 8 May 7 May 6 May 5 May 4 May 3 May 2 May 1 Apr 30 Apr 29 Apr 28 Apr 27 Apr 26 Apr 25 Apr 24 Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1 Mar 31 Mar 30
Windows 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 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 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 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 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 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0

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