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

Ltex do not pick a file as dictionary #157

Closed
cinghiopinghio opened this issue Feb 23, 2022 · 4 comments
Closed

Ltex do not pick a file as dictionary #157

cinghiopinghio opened this issue Feb 23, 2022 · 4 comments
Labels
1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label) 3-not-a-bug Issue resolution: LTeX behaves as expected, or bug cannot be reproduced

Comments

@cinghiopinghio
Copy link

Describe the bug
When defining dictionary.en-US = ":path/to/file", the words in the text file are not added to the word list.

Steps to reproduce

test config test.json:

{
    "dictionary": {
        "en-US": [
            "pluto",
            ":/path/to/test.txt"
        ]
    }
}

test dictionary test.txt:

pippo

run the code:

echo "This is pippo and pluto." | ltex-cli --client-configuration=test.json -

I get the output:

-:1:9: info: 'pippo': Possible spelling mistake found. [MORFOLOGIK_RULE_EN_US]
This is *pippo* and pluto.
        Use 'hippo'

Expected behavior
One would expect that the words listed in test.txt are not found as errors.

LTeX configuration
see above

LTeX LS log
see above

Version information

Linux (Archlinux).

{
  "ltex-ls": "15.2.0",
  "java": "11.0.12"
}
@cinghiopinghio cinghiopinghio added 1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label) labels Feb 23, 2022
@valentjn
Copy link
Owner

External files are not supported by ltex-ls, only by vscode-ltex/coc-ltex (“Setting Scopes & Files” is under “vscode-ltex / coc-ltex”, not “LTEX LS”).

@valentjn valentjn added the 3-not-a-bug Issue resolution: LTeX behaves as expected, or bug cannot be reproduced label Feb 23, 2022
@cinghiopinghio
Copy link
Author

Thanks for the quick reply.

Indeed you are right. I get confused by the fact that this configuration appears also in the global configuration.
There is no mention to the fact that it may not work in ltex-ls.

@valentjn
Copy link
Owner

There is a striped bar to the left of the text—when you hover it, it says that it's client-specific.

I guess it's a good idea to state this more prominently somewhere at the top.

@cinghiopinghio
Copy link
Author

I see, thanks anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label) 3-not-a-bug Issue resolution: LTeX behaves as expected, or bug cannot be reproduced
Projects
None yet
Development

No branches or pull requests

2 participants