advanced-open-file
advanced-open-file copied to clipboard
Add as a project folder does not work
I have read in the docs, that I can add a hightlighted path as a project folder using ctrl + alt + o on linux. In my machine it does not work. The advanced open file palette closes and nothing happens. What kind of information do you need from my side?
Thanks for the report!
- Are you trying on a directory with a plus symbol on the side, or one without?
- Are you highlighting the entry with the keyboard, or with the mouse?
- If you open the DevTools (View -> Developer -> Toggle Developer Tools) and view the console, is anything logged when you try to add a project folder?
- Can you open the keybinding resolver (should be ctrl+. on Linux) and try to add a file with the shortcut? And then check what the resolver says after you hit the shortcut? It should show the advanced-open-file binding, but if it shows another binding, that one might be overriding ours.
Thanks for your time!
- With a plus symbol.
- With the keyboard, since I am trying to gain a similar workflow as in vim with
:e file. - No, the console does not log anything.
- It shoes the advanced file open
togglecommand.
It is a bit strange. The palette closes and nothing happens. When I click the plus symbol with the mouse it works as inteded.
I must've missed the notification that you replied, sorry for the late response!
Also I realize I'm a fool now. There's no default shortcut defined at all! https://github.com/Osmose/advanced-open-file/commit/047401c7d3b6d1c0abd8b7af4740c510474be419 is the commit that added the command, but it doesn't add a keybinding, even though it says it does in the README. Whoops!
This should be a quick fix. What would be your preferred shortcut? Maybe ctrl + shift + a?
What is the status of this issue? I also found it surprising that Ctrl-Alt-O does not work as specified in the README. Is this issue blocked by the need to decide on a default shortcut? If so, how can I define a custom shortcut for the command in my keymap.cson until a default shortcut is implemented? In any case, any references to a keyboard shortcut for this feature (e.g. those added in 047401c7d3b6d1c0abd8b7af4740c510474be419) should be removed until an actual keyboard shortcut is implemented.