TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Show HN: Voil – Oil.nvim for VSCode

5 pointsby hexomancer4 months ago
I wrote a vscode extension which allows you to create&#x2F;rename&#x2F;move&#x2F;delete files by editing a text buffer. If you are familiar with oil.nvim, this is similar. In my opinion this is vastly superior to the built-in file manager because it allows you to utilize your existing text-editing muscle memory into file manipulation skills, as opposed to the built-in file explorer which requires mouse or at least memorizing new keyboard shortcuts. There is a video demo on the github page here: <a href="https:&#x2F;&#x2F;github.com&#x2F;ahrm&#x2F;voil">https:&#x2F;&#x2F;github.com&#x2F;ahrm&#x2F;voil</a>.

1 comment

berkes4 months ago
Wow, nice achievement! It&#x27;s funny to see the amount of community effort around vscode to make it behave like vim.<p>I&#x27;ve never got to like oil.vim. Tried, but it doesn&#x27;t stick.<p>I guess, partly because it doesn&#x27;t solve a real problem for me: commandline (bash, zsh) with gnutools is good enough.<p>But mostly because doing stuff to files, for me, is more about the actions (commands, events) and less about the end result. With oil, it feels a bit like I describe the state I want in a text file (in a DSL) but my head keeps translating that from the actions I&#x27;d need to take. Probably just 30+ years of commandline thinking worn into my brain too deep.