VSCodeVim / VSCodeVim/Vim

Filename autocomplete

Open
#8,096 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

Hello,

I would like to be able to use the vim autocomplete Ctrl+x Ctrl+f which is able to autocomplete paths.
It is an important feature to me when making scripts.

Example: for a path (dir1/dir2/dir3/myfile.extension)
When writing path my_function_opens("./dir1/dir2/")
Ctrl+x Ctrl+f shows the content of dir2.

I have seen your codebase and am having trouble trying to run tests and/or docker (am not a ts dev but more of a C++ one).
I am ok with developping the feature and creating a PR afterwards.

Can you just help me get a docker container up and running up to the point where I can change a test of the file lineCompletionProvider.ts to make it pass or fail ?

Basically, I try to docker build and docker run but I get an error of type "ENOENT: npm /app/package.json not found, no such file or directory".
I don't really know much about making a docker container, after that I have some experience with many programming languages and JS so should be ok.

Thanks for your consideration,
Hope I can contribute.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with lineCompletionProvider.ts and resolve the reported Docker setup problem involving npm and /app/package.json so the tests can run. Use the issue's Vim Ctrl+x Ctrl+f example as the behavior to investigate; done means path completion shows the contents of the requested directory in the described context.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.