VSCodeVim / VSCodeVim/Vim

vimrc EISDIR error

Open
#9,663 0 comments 0 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

Describe the bug
Trying to enable a .vimrc file, I get the following error:

vimrc file "[director]" is broken, err=Error: EISDIR: illegal operation on a directory, read

If I change the file to som

To Reproduce

  • Create .vimrc in any folder
  • change vimrc path to [folder]
  • When vscode reloads setting, gives the EISDIR error
  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
This should load vimrc without issue

Screenshots
If applicable, add screenshots to help explain your problem.
If remapping-related, please attach log output: https://github.com/VSCodeVim/Vim#debugging-remappings.

Image
Image

Environment (please complete the following information):

  • Extension (VsCodeVim) version: [v1.30.1]
  • VSCode version: 1.85.2
  • OS: Win10 22H2 19045.5854

Additional context
Can't update to latest VSCode (version locked by company IT)

WORKAROUND
I was able to get a different format of vimrc to load. I created file as vscode.vimrc and it does not through the error. Location does not seem to matter, seems like error has to do with treating the file as a folder instead of a file and creating name.vimrc this fixes the issue. Posting in case someone runs into same problem

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 by reproducing the EISDIR error with VSCodeVim v1.30.1 on VSCode 1.85.2 and the reported Windows environment, using a .vimrc path that points to a folder. Trace how the extension handles that path and compare it with the working vscode.vimrc case; done means a valid .vimrc loads without the directory-read error.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vim, vscode
Domain
devtools, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.