-
Notifications
You must be signed in to change notification settings - Fork 2
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
How to teach typos about project specific terms? #4
Comments
For now you can create a [default.extend-words]
ODF = "ODF" Then you need to reload the editor. I might add a command to automatically do this in the future but for the time being this will fix your issue. Note that the configuration will only apply to your project directory. Any other file opened outside of the repository in Zed will not see the |
Thanks, adding a shortcut to add a word to the list would be nice. But per project word may not be enough. Many projects have multiple repos so you will not update multiple project typos.toml files. There should be also a per machine configuration (like ~/.gitconfig and .git/config). Per machine config should be the most useful way, hopefully it can be synced between machines like other zed settings. |
For reference, the relevant docs: |
Hello again, I dug a bit on how to solve this issue and the code action to add new words should be done in the LSP itself, not this zed-plugin which purpose is to add the "glue" to use the LSP. There is already a WIP PR to implement this feature tekumara/typos-lsp#12, which should be automatically downloaded when the new version is released (if not, then that's a bug I should fix here). I will ask on the PR if it's also possible to add an action into a global config, which would ultimately fix your problem, you're not the only one having it :D |
Thanks for typos, this is a wonderful extension!
One issue, it complains about terms like ODF (OpenShift Data Foundation):
How can I teach it about ODF?
In vim I would add ODF to my local dictionary (zg) - quick an easy and works for many projects related to ODF on single machine.
The text was updated successfully, but these errors were encountered: