Replies: 2 comments
-
I think it has to do with the order of entries in In theory, Eglot is doing nothing wrong. |
Beta Was this translation helpful? Give feedback.
-
OK, I found that by shuffling the order of the entries in I guess I was surprised by the assumption that because a mode X derives implementation from another mode Y, any language server for mode Y should be usable with mode X, when the server program list contains an entry that is a more specific match to the mode. For now I'll change my groovy declaration to append the entry to the end of |
Beta Was this translation helpful? Give feedback.
-
I'm not sure how I am supposed to configure
eglot-server-programs
to avoid this problem.I can add support for
groovy-mode
via:But now I want to try out the language server for
nextflow-mode
, (which is derived fromgroovy-mode
), using a similar construct:However, when I start eglot in a buffer that is in
nextflow-mode
, it starts the groovy language server instead.Beta Was this translation helpful? Give feedback.
All reactions