Claire: The Fuzzy File Finding Light Table plugin with Style.

Claire is a fuzzy file finder heavily inspired by Emacs' ido-mode. It implements a subset of the features ido-mode provides, with a few extra touches.

claire is specifically the LightTable plugin for the claire-files backend, which is being developed synchronously with this plugin. The backend can be found in the claire-files repository.

Usage

1. Clone the claire package into your LT plugins directory.

       $ cd /path/to/config/LightTable/plugins && git clone https://github.com/joshuafcole/claire.git

2. Download the plugin dependencies via npm.

       $ cd claire/ && npm install

You're all set! Restart Light Table. If using the default keybindings, you can activate claire with C-x C-f. Interact by typing. delete is bound to smart-delete by default, tab is bound to smart-complete, and enter opens the current search term.

Changelog

• 0.1.8 Bug fixes.
  • #7 - Editor not focused after match opened - @seancorfield
  • #10 - :claire-iterate did not respect direction parameter - @dubiousdavid
• 0.1.7 Fixes bug when reattaching to bottom bar after console has been opened.
• 0.1.6 Fixes implicit relative include path and claire being eaten by toggling the console.
• 0.1.5 Bumps LTrap version to fix claire when no tab / non-file-backed tab is selected.
• 0.1.4 Serious refactoring to make claire more easily maintainable.
• 0.1.3 Fixes sticky path separator, removes File: label, and allows enter to finalize directory choices when iterating instead of (failing) to write a directory as a file.
• 0.1.2 Fixes focus issues, typo in default keymap, and compatibility with 6.0 binary release of LT.
• 0.1.1 Properly supports active directory when used with multiple tabsets.
• 0.0.7 Removes dependency on jQuery.
• 0.0.6 Initial release for plugin manager.
• 0.0.5 Fixes weird behavior when iterating to directories.
• 0.0.4 Initial public release.

Legal Stuff

Claire and its constituent parts are free as in liberty to use as you please to the greatest extent possible. The code is clean, concise and thoroughly documented with comments. External API should stay consistent, but internal aspects may change in the future to improve clarity and reusability.