Comments (7)
Thanks for the report! I had assumed that the LSP server library I was using would silently drop the window/showMessageRequest
if the client doesn't support it (it does that with some other operations, such as workspace/configuration
, but it seems I need to explicitly check for support.
Should be a fairly quick fix!
Thanks also for the info about configuring helix - I'll borrow that for the Contextive readme documentation if that's ok?
from contextive.
Thanks also for the info about configuring helix - I'll borrow that for the Contextive readme documentation if that's ok?
Sure! I can report back once the LSP setup works if anything else was needed to set it up
from contextive.
Hi @ssiltanen v1.10.4 should resolve this issue - let me know how you go! As part of reproducing/testing, I've also added some documentation to the readme - let me know if this makes sense and works for you: https://github.com/dev-cycles/contextive#helix (note, it's basically yours, but you don't need the --stdio
arg, and I've included what to do if the definitions file is not in the default location.
As a helix user, you might also be interested in this discussion: helix-editor/helix#8850 - about using an LSP on all files. If they describe how to do that, or decide to update helix to support it, I'll update the documentation.
It also seems that I could open a PR against https://github.com/helix-editor/helix/blob/master/languages.toml to make the language-server configuration 'baked into' helix - it would then just require the user to nominate which languages to enable it for. I'll wait until the discussion above is resolved before doing that, though, to ensure I understand the intended approach for an lsp like this.
Feel free to raise another issue if any problems!
from contextive.
Hold on that, seems to be an issue with 1.10.4. Will be getting a fix out shortly.
from contextive.
OK 1.10.5 should work.
from contextive.
OK 1.10.5 should work.
Yes, it resolves the issue (v.1.10.5)! Thank you for work 💯
I've also added some documentation to the readme
Documentation looks correct to me and I can verify the --stdio
was not needed after all like you mentioned. Although, in my configuration I did not specify the definitions.yml path but instead created it under .contextive in the repo root and let the LSP find it on its own.
discussion about using an LSP on all files
Thank you, I was not aware of that discussion taking place yet, but that would be indeed cool to have, especially with this LSP. I agree before creating the helix PR, it is wise to follow the discussion you mentioned.
Also, this might be just a user error on my behalf but I noticed a behaviour with Helix and multi LSPs that the onHover shows docs only of one LSP, which affects Contextive as well. I started a discussion about it here helix-editor/helix#8872
from contextive.
Great, thanks for confirming! And thanks for opening that discussion - I'll keep an eye on that as well, as it is almost always the case that Contextive is used alongside another language server.
from contextive.
Related Issues (20)
- Support for shared definitions HOT 3
- Support sharing definitions between repos with different languages/package managers HOT 3
- Support VSCode multi-root HOT 5
- Support multi-root workspaces in vscode with different definitions files in each root
- Context information is not shown when using LF Line endings, only with CRLF HOT 5
- Multiple context definition files HOT 5
- Support multiple definition files in a single repository
- Support sharing definitions from multiple sources into the current work environment
- Language Server process doesn't exit when LanguageClient or vscode stops.
- Support JetBrains Fleet
- Omnisharp error after installing Contextive HOT 4
- Multi-line yaml can result in additional underscores HOT 6
- Problem running contextive HOT 2
- Release Language Server as independent Component
- Move `contextive.path` default to `Contextive.LanguageServer` for vscode extension HOT 7
- Add a `LICENSE` file HOT 2
- Editor agnostic configuration HOT 6
- Neovim setup not working HOT 4
- Exception starting 1.10.4 due to dotnet trimming HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from contextive.