`gf` should expand environment variables in filepaths.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST
What happened:
Nothing :)
What did you expect to happen:
I expected to go to a file that includes environment variable names.
How to reproduce it (as minimally and precisely as possible):
Create a text file with the following lines:
$HOME/.bashrc
${HOME}/.bashrc
Put cursor on one of those files and press gf.
If cursor is on the first line, vscode does not do anything.
If cursor is on HOME inside ${HOME}, vscode would create a new file called HOME.
Environment:
RHEL 7.2
- Extension (VsCodeVim) version:
- VSCode version: 1.23.1
- OS version: 0.12.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in VSCodeVim with paths containing $HOME and ${HOME}, using the versions and environment described in the report. Trace the gf file-navigation entry point and identify where the path is parsed; done means both forms resolve to the expanded file rather than doing nothing or opening HOME, with coverage for the reported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100