@facelessuser Is there any chance that you will need to extend FuzzyNav so that it can be used as a dialog for saving files?
Yeah, it is still on my list. I have a habit of taking on too much, but I will get to it.
Doesn't it already, to an extent via the "Fuzzy Make File" and "Fuzzy Make Folder" commands?
Kind of, and you can use the "Fuzzy Copy" and "Fuzzy Paste" command to effectively "Save As", but I know what he means. He would like to take an unsaved buffer with content and turn it into a file, but pass it through ST2's save function to save it in a consistent way. Also the same with save as with unsaved content.
Great idea implementing (and the original idea from biermeester and matthjes) os/host specific settings. I hope you don't mind if I apply it to another plugin.
I don't mind at all. That is what it is there for. As long as you include the license, it is fine. I plan to integrate it into a couple more of my plugins to abstract some settings that make sense to be abstracted.
skuroda wrote: One more thing (feel free to ignore this as it isn't plugin related if you would like). I have written a plugin to help identify key conflicts. Though to me you fall into the category of "If it doesn't exists and I want it, I'll build it", I was wondering if there was anything you could think of as a Sublime Text user or developer, that you feel would be helpful to know with regards to key bindings. Anyways, obviously not related to your plugin, so feel free to ignore.
Off the top of my head, the only things I can think of that I miss in regards to key bindings I have solved in two scripts:
1. Shorcut profiles (ShortcutPlus): https://gist.github.com/4029726
2. Find and open any keymap file or other package files (PackageFileSearch): https://gist.github.com/4072884
Neither plugins above are formal Package Control releases. Sometimes I post scripts and see if people actually care about them to see if it is a waste of time creating a formal Package Control repo. Sometimes I don't release them at all because of laziness, or they just aren't polished enough, or I don't think anyone will care.
The ability to fairly quickly pull up a plugins keymap file (without having it in a project) to disable something is nice. I don't recall releasing PackageFileSearch which can pop up a menu to show a list of all files of X type found in packages on your computer, but I find it very useful, and it applies to key map files as well.
What might be nice from your plugin, is when you show the key maps you create invisible regions with keys ("keyconflict=filepath" or something) around each keymap. When you click or maybe double click (heck even a shortcut), your plugin would look at the region and determine which key map file to open. Just an idea.