Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

A plugin which supports fuzzy search in gedit. (forked from snapopen)

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 fuzzyopen
Octocat-spinner-32 CHANGELOG
Octocat-spinner-32 INSTALL
Octocat-spinner-32 README
Octocat-spinner-32 TODO
Octocat-spinner-32 VERSION
Octocat-spinner-32 fuzzyopen.gedit-plugin
README
Fuzzy Open (Gedit Plugin)
Andrew Liu <andrewliu33 (at) gmail com>
Mads Buus Jensen <online@buus.net> (SnapOpen)

Github location: http://github.com/eggegg/fuzzyopen

This plugin is base on SnapOpen plugin.
(http://github.com/MadsBuus/gedit-snapopen-plugin)
It use a totally different algorithm to find and rank the search result.
It depends on File Browser Plugin to get the root of searching.

FEATURES:

 - Enable partial matching search, search with path
 - Metedatas showed when searching: modified time, git status, file extention
 - Ignore the hidden files and the file cannot be opened by gedit
 - Options for case ignored or space ignored search

USAGE:

Shortcut: Ctrl + Shift + O

When you type the query in the new query window, the box under the query line
will simultaneously update the search result.  The search space start from the
root of the file show in the file browser plugin.

The search result contains the files which matches the query along with some
metadata, including the extension name, the time of modification displayed in
relative form, and the git diff status if a folder .git is detected under the
root of the file browser.

SEARCH ALGORITHM:

The algorithm is intended to solve the problem that sometimes there are many
files having the same name (ie. index.erb), so search with path is a solution
to the problem.  However, I'm too lazy to enter the whole path name.  So this
is how the fuzzy search algorithm comes out.

 - there is point for each single match
 - the points increase for continue match, 1 point at first, 2 points at second,
   3 points at third, ... and so on

Eventually, the algorithm will match something like this:
amus         =>   app/models/user.rb
a/v/tclub    =>   app/view/theme/plain/club.erb

If you have any suggestion about the algorithm, please contact me and help me
improve it.

Something went wrong with that request. Please try again.