We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime - command-line tools
cspell
8.2.3
Not sure
Macos
Sonoma 14.2.1
cspell does not automatically read a configuration file if it is a symlink.
somenewword
cspell.yaml
cspell trace somenewword
mv cspell.yaml actual.yaml
ln -s actual.yaml cspell.yaml
cspell trace somenewword --config cspell.yaml
cspell finds and reads cspell.yaml no matter whether it is a symlink or an actual file.
No response
words: - somenewword
The text was updated successfully, but these errors were encountered:
fix: handle symbolic links to config files
7bfa5b8
fixes #5120
Confirmed v8.2.4 works as expected. Thank you very much for the prompt response!
Sorry, something went wrong.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Successfully merging a pull request may close this issue.
Kind of Issue
Runtime - command-line tools
Tool or Library
cspell
Version
8.2.3
Supporting Library
Not sure
OS
Macos
OS Version
Sonoma 14.2.1
Description
cspell does not automatically read a configuration file if it is a symlink.
Steps to Reproduce
somenewword
in a simple config file:cspell.yaml
cspell trace somenewword
mv cspell.yaml actual.yaml
ln -s actual.yaml cspell.yaml
cspell trace somenewword
. The config is not loaded.cspell trace somenewword --config cspell.yaml
. The config is loaded.Expected Behavior
cspell finds and reads
cspell.yaml
no matter whether it is a symlink or an actual file.Additional Information
No response
cspell.json
No response
cspell.config.yaml
Example Repository
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: