Skip to content
This repository
branch: master
README.markdown

fuzzy-find-in-project.el - Emacs binding to the fuzzy_file_finder rubygem.

License:

Copyright (c) 2008 Justin Weiss

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

http://www.avvo.com

Commentary

Requires ruby, rubygems, and the fuzzy_file_finder rubygem.

The fuzzy_file_finder rubygem can be installed with the following command:

sudo gem install --source http://gems.github.com jamis-fuzzy_file_finder

Usage

The primary interface into the functionality provided by this file is through the fuzzy-find-in-project function. Calling this function will match the query to the files under fuzzy-find-project-root and open up a completion buffer with the first matched file selected (with a >.) The selection can be changed using C-n and C-p, and the currently selected file can be opened using <RET>.

Configuration:

In your .emacs or init.el:

(add-to-list 'load-path "~/.emacs.d/path/to/fuzzy-find-in-project")
(require 'fuzzy-find-in-project)
(fuzzy-find-project-root "~/path/to/project")
Something went wrong with that request. Please try again.