Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The design
See original GitHub issue-
Not depends on denite.nvim
-
Vim8/neovim compatible(nvim-yarp is needed for Vim8)
-
Implemented by Python3
-
No double filer feature
-
Column feature
-
Source feature
-
Options
-
Highlight is defined by column
-
Few commands (
:Defxcommand only?) -
Extended rename
-
Mark
-
Windows supporters are needed
-
The original trashbox feature
-
No minimal features
-
Subtree feature like vimfiler
-
No default mappings
-
No global variables
-
No explorer feature(like
g:vimfiler_as_default_explorer)
Release date: In 2018 someday
Issue Analytics
- State:
- Created 6 years ago
- Reactions:30
- Comments:60 (35 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have started the vaporware development.
https://github.com/Shougo/defx.nvim/commit/4b4dfae45c44933cc9c5e092e6c7e728e18d6fa9
It would be nice if it does not rely on filesystem.
For example, I would like to make a plugin which cooperate with this one to show a directory tree on a particular commit. In that case, probably the INPUT for this plugin would be a tree dictionary with custom kind, actions, etc.