Keyboard shortcuts don't seem to work when panel is active. about fuzzyfilenav HOT 4 CLOSED

I am on Mac with 10.8+ and I do not have this issue.

I need more details ST2 or ST3. Check for shortcut conflicts as well with other plugins. FuzzyFileNav should restrict its shortcuts to the panel only, but other plugins aren't always so careful to avoid panels and can cause conflicts. So, if other plugins have shortcuts defined as super+n and super+b, and they do not avoid widget elements, FuzzyFileNav shortcuts might get overridden.

Do you see any errors in Sublime Text console? If so, please post them here.

Also remember, some shortcuts that act on a file require the whole name of the file since I can't access the highlighted index. In these cases you should auto-complete names first.

Also try restarting ST. I don't know if you tried this after you installed the plugin. Sometimes things like that can help.

from fuzzyfilenav.

ST2. Restarted it several times.
Console is not throwing any errors related to Fuzzy plugin (although it's showing errors related to other plugins).

When I said that none of the shortcuts are working for me I ment that they are doing they native ST2 function. So fer example when I have a folder open and press super+n I'm getting a new tab created (default ST2 function). Same goes for super+shift+n (new window opened). It's like the default Fuzzy key bindings were not respected.

I don't know it that might be a factor but I'm using Vintage mode and VintageEx plugins.

from fuzzyfilenav.

One easy way to verify is to change the shortcut for one of the actions in FuzzyFileNav to something you are sure no one is using and see if it starts working. If this is the case, you know it isn't FuzzyFileNav that is directly broken.

There is a plugin that will also show you key conflicts. It is called FindKeyConflicts. FuzzyFileNav will show up as having conflicts with default, but that is okay. FuzzyFileNav only overrides them when the cursor is in the quick panel. If another plugin is also conflicting, that might be the issue. A number of plugin developers don't remember to exclude widgets views, so if their keymaps are imported after FuzzyFileNav and they don't exclude widgets, they will override FuzzyFileNav. So running FindKeyConflicts on my Windows system, I only see conflicts with default which is expected:

example

 [ctrl+b]
   build                                    Default               
   fuzzy_bookmarks_load                     FuzzyFileNav          [{"key": "fuzzy_bookmarks_load"}]

from fuzzyfilenav.

Ok. I think I have to go for a walk or something.... I don't really know how I missed it before but everything works as it's supposed to. What I was doing was using the shortcuts without any file name written and that's exactly why it was not catching the correct file binding. Seriously I'm going for a walk, can't believe I didn't catch that earlier 😄

Sorry to bother you. Plugin works fine (and is a much better implementation then what I wrote for my self earlier - Sublime File Navigator). Thanks for your help.

from fuzzyfilenav.