Skip to content
New issue

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

[Bug]: Symlink to configuration file is ignored unless specified explicitly #5120

Closed
1 task done
heavywatal opened this issue Dec 27, 2023 · 2 comments · Fixed by #5122
Closed
1 task done

[Bug]: Symlink to configuration file is ignored unless specified explicitly #5120

heavywatal opened this issue Dec 27, 2023 · 2 comments · Fixed by #5122

Comments

@heavywatal
Copy link

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

  1. Define somenewword in a simple config file: cspell.yaml
  2. Confirm it works: cspell trace somenewword
  3. Rename it: mv cspell.yaml actual.yaml
  4. Create a symlink to it: ln -s actual.yaml cspell.yaml
  5. Try using it implicitly: cspell trace somenewword. The config is not loaded.
  6. Use it explicitly: 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

words:
  - somenewword

Example Repository

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@heavywatal
Copy link
Author

Confirmed v8.2.4 works as expected. Thank you very much for the prompt response!

Copy link
Contributor

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants