[Feature request] Relative path completion

[kristijanhusak]

Hi,

would you consider adding a relative file path completion as an optional source?
Something like this.

I tried adding it myself, but since i don't know lua, everything turned out to be calls to vimscript.

[haorenW1025]

I'd loved to implement new sources! May I ask a small question though, how is this different from the filename completion of ins-complete?

[kristijanhusak]

ins-complete file autocompletes only absolute paths and paths relative to the CWD. Path completion allow autocompleting paths relative to the current file.

[haorenW1025]

Understand. That's actually pretty helpful. I'm pretty busy recently though... Hopefully I'll be able to make some progress in the weekends.

[haorenW1025]

Sorry for pending this so long...The first step of path completion should be done in the latest commit. It should still have lots of issues and it doesn't support definite path for now. You can enable it by specified path in complete_items, the given example allow path completion only in string. Feel free to report any issue after trying it!

let g:completion_chain_complete_list = {
            \ 'default' : {
            \   'default': [
            \       {'complete_items': ['lsp', 'snippet']},
            \       {'mode': '<c-p>'},
            \       {'mode': '<c-n>'}],
            \   'comment': [],
            \   'string' : [
            \       {'complete_items': ['path']}]
            \   }

[kristijanhusak]

Sorry for late response. I tested it, looks good to me for now.

[kristijanhusak]

Few minor issues that I found:

• If I try to autocomplete with slash after file, I get the full thing in the autocomplete menu. for example, having this /usr/local/bin/nvim/ shows /usr/local/bin/nvim Path

• Hidden folders are not autocompleted, for example, ~/.conf doesn't autcomplete ~/.config. Note that once i write the full folder name and continue completing, it works, so ~/.config/nv properly completes to ~/.config/nvim

• Root is not autocompleted, but this may be due to permission issue, i'm not sure. So for example /ho doesn't show anything (should be /home), but same as for hidden folders, works after the first part.

[haorenW1025]

Okay, the first and the third issue should be fixed. The second one is a little tricky and I might need some time...

[kristijanhusak]

Yeah it's fixed, thanks!

[kristijanhusak]

I think i found some new issues unfortunately.

looks like relative completion is now broken.

path automatically completes without anything: So if I do this:

let g:test_path = '

It automatically starts autocompleting this file directory items, which is I guess fine. The problem is that doing ./ is broken.

So doing this:

let g:test_path = './

should basically do the same thing, but it starts listing files and folders from cwd.

If i try to go one parent up, it goes up from cwd instead of current directory of the file

let g:test_path = '../

[haorenW1025]

Should be fixed now, please check if it works.

[kristijanhusak]

Works great! Even hidden folders are shown.

I just ran into one minor issue when testing. When I tried to autocomplete from root with /, i properly got the root folders (etc, home, usr), but when I type any of them, it doesn't continue autocompleting.

For example typing /ho properly shows /home. Then when I add slash, i should get kristijan as a single option, but I don't get anything. Once I type out kristijan it properly shows all the files from home folder.

Another one that doesn't go deeper is for example /etc I assume this has something to do with user permissions.

I'm not sure how the implementation is done, but maybe you could just use the native file autocompletion source if autocompletion starts with /. Native one properly returns any level.