In an effort to get this project revitalized, I am setting things up for publishing to the marketplace before I start trying to merge in any fixes or features. I want the published extension to be clearly labeled as a fork of Jake's work but I also want to be set up so that, if we end up being viable long term, we don't have code and settings littered with fork for example. Here is what I propose.

1. We use elixir-lsp (display name Elixir Language Server Protocol) as the publisher. Sticking with this as our org name and publisher name feels like consistent branding that should help users understand where it came from. Alternatively we switch to just ElixirLS (I grabbed the elixir-ls org if needed) since this is the language server not the protocol, but that's not super important.
2. We use elixir-ls for the package name, making the full package id be elixir-lsp.elixir-ls or elixir-ls.elixir-ls if we dropped the P.
3. We use something like "ElixirLS Fork: ..." as the display name of the extension, so that anyone who finds us in the marketplace knows right away that this is a fork and isn't misled if they were trying to find Jake's extension.
4. We ensure that the README as displayed on the extension's entry in the marketplace clearly calls out Jake's great work and the reason for the fork, and points people to Jake's extension if that is what they were looking for.
5. We use ElixirLS for the langId as opposed to Jake's elixirLS. This is very similar I know, but it is different enough to not squash config people are using from his extension and doesn't require that fork or similar be left in settings for users of this fork.
6. We use "ElixirLS" and not "ElixirLS Fork" in the UI labels. It seems unlikely that someone will have both extensions installed at the same time so it doesn't feel necessary to call out fork in those labels.

@JakeBecker I'd love to hear your opinion on this if you can spare the time. I don't want to do anything disrespectful to your work and hope to help this thrive for the sake of the community.

Anyone else have an opinion? @axelson? @msaraiva?

Did anyone get basic autocomplete of CSS class names and other HTML attributes to work with this plugin? I'm only getting emmet to work by adding

  "emmet.includeLanguages": {
    "HTML (EEx)": "html"
  },

but autocompletes like

are not working (tried both master versions of bradlc.vscode-tailwindcss and ecmel.vscode-html-css)

Environment

Most of this can be filled out by running the VSCode command (by default bound to Ctrl+Shift+P) "ElixirLS Fork: Copy Debug Info"

  * Elixir & Erlang versions (elixir --version): Erlang/OTP 22 [erts-10.6.4] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [hipe] [dtrace]

Elixir 1.10.2 (compiled with Erlang/OTP 22)

  * VSCode ElixirLS Fork version: 0.3.2
  * Operating System Version: darwin 19.4.0

Troubleshooting

• Restart your editor (which will restart ElixirLS) sometimes fixes issues
• Stop your editor, remove the entire .elixir_ls directory, then restart your editor
  • NOTE: This will cause you to have to re-run the entire dialyzer build

Starting with a new phoenix repo my formatter file consists of:

[
  import_deps: [:ecto, :phoenix],
  inputs: ["*.{ex,exs}", "priv/*/seeds.exs", "{config,lib,test}/**/*.{ex,exs}"],
  subdirectories: ["priv/*/migrations"]
]

and a sample ecto schema file the fields are without parenthesis because of https://github.com/elixir-ecto/ecto/blob/master/.formatter.exs

So this code snippet when formatting via VSCode and via CLI stays the same

  schema "users" do
    field :name, :string

    timestamps()
  end

So far everything is correct.

In the case where I have multiple projects (e.g. I usually open both the frontend and backend) and the elixir project is not first (backend first then frontend), the formatter doesn't seem to respect the .formatter.exs file.
After moving the project in the 2nd+ position it adds the parenthesis:

  schema "users" do
    field(:name, :string)

    timestamps()
  end

i tried a PR..but it won't.
So i put:
JakeBecker/vscode-elixir-ls#162 (comment)

Hello,

I'm using VS Code 1.43.2 and ElixirLS Fork 0.3.2.

Somehow, I can't get EEx tags to highlight correctly inside HTML attributes, as the entire quoted attribute highlights as a single string.

Example:
<div id="user_<%= @id %>">

In the above example, "user_<%= @id %>" highlights as a string. Ideally, <%= @id %> would highlight in the usual EEx tag format inside the string highlighting.

The issue is illustrated nicely with two pictures in this pull request for the original ElixirLS: https://github.com/JakeBecker/vscode-elixir-ls/pull/121). Not sure why it's not working for me, maybe it didn't make it into the published extension (I don't know much about how VS Code extensions work)?

Thank you for any help on this and all the work on this really useful extension!

This comment has some instructions that should be a good starting point:
JakeBecker/elixir-ls#163 (comment)

But if you don't want to wait for the package to be published, you can build the package yourself:

git clone --recursive https://github.com/leandrocp/vscode-elixir-ls
cd vscode-elixir-ls
git checkout support-phoenix-live-view
npm install
npm install -g vsce
vsce package

A file elixir-ls-0.2.24.vsix will be generated in the current path. On vscode, go to Extensions > ... > Install from VSIX... to install the package.

Hi! I was wondering if you have plans to improve the current elixir grammar.

I'm asking because I was recently extending some elixir color schemes and noticed that some tokens are missing or don't have a distinction from others. For instance, both key: (parameter) and :key (atom) are defined as source.elixir > constant.other.symbol.elixir which prevents me from highlighting only atoms.

I was looking for solutions and saw that the ruby extension has a little bit more definitions:
https://github.com/rubyide/vscode-ruby/blob/master/packages/vscode-ruby/syntaxes/ruby.cson.json (if you search the page for "hashkey" you'll see some good examples).

I get this everytime I try to save an Elixir file:

Running Save Participants for 'test/users/notifications/mailer/some_mailer_test.exs': Formatting

It doesn't even save the file until i Cancel the message above. Once I cancelled it, it also formats the file. However, it's a really annoying behaviour.

It works fine if you downgrade VSCode to 1.41 or less.

Am I the only one with this problem on VSCode 1.42.0 ?

I've seen there are other Extensions with this problem, here's a PR from another project that explains and fixes it: zxh0/vscode-proto3#73

Environment

• VSCode ElixirLS Fork version: master@93da0f9203be0efdbc486e38a9c02a99cbb95939

Troubleshooting

It seems that recent repo changes broke something. This is the output from Developer Tools console

Warning: jakebecker.elixir-ls is not compatible with ElixirLS Fork, please uninstall jakebecker.elixir-ls
Activating extension 'JakeBecker.elixir-ls' failed: command 'extension.copyDebugInfo' already exists.
ERR No application in the Launch Services database matches the input criteria.: Error: No application in the Launch Services database matches the input criteria.

If VSCode had direct support for universally embedding languages that would be ideal, but it's currently on the backlog:

• microsoft/vscode#1751
• This comment on the above issue has an example of embedding that is possible today

You can embed syntax highlighting, this might be the lowest hanging fruit:
https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide#embedded-languages

You can also embed support for another language server:
https://code.visualstudio.com/api/language-extensions/embedded-languages

If you use tailwind css, this extension has support for eex (and leex?) files, and might be a good source of inspiration:
https://github.com/bradlc/vscode-tailwindcss

Currently the Language server is built from git on activation of the plugin, if and only if there has not yet been a checkout/clone.

This happens from master and a the hardcoded URL of the new LSPs home.

This need to be configurable.

My system config,

Ubuntu - 18.04
VS Code - 1.43.0
Elixir 1.9.2

I've the docker elixir project and I'm using "bitwalker/alpine-elixir:1.9.2" image.

When I click F12. It's only showing "No definition found". It's not working. When I try Ctrl + Shift + F, I can able to find the function.

Any other project, git shows changes normally.

This same project, with all extensions disabled git changes shown properly.

This same project, with ElixirLS Fork causes git changes to not be shown and also presents itself as if git wasn't even initialized in the repo.

Tried restarting my mac, deleting _build and deps, and restarting the extension itself, but no changes.

Any ideas?

I've been using this extension on Mac for a year (well, first the original and then the fork) and it works very well. However I've switched to a Windows machine recently and I've tried to make it work with no success.

Having Elixir and erlang with a compatible OTP (1.9.1-otp22 and otp 22), I open up an elixir project and:

• On both platforms I always get the message saying that the build is stopped because the cwd has changed (just removing the trailing .)
• In windows I get everything working except the @SPEC feature
• In WSL I cannot even get the code problems to be processed, so I only get the code documentation when hoovered. Taking a look on the Output window I can see that CodeLens gives an error.

WSL uses asdf, by the way

Is there anything I must do to make it work?

Let the user choose where the LS sources and binaries should be stored and whether or not they should be managed by this plugin or something else (which would deactivate auto update as described in #2).

Currently the debugger appears to launch with an unstable CWD, and since the asdf environment is loaded based on the CWD the asdf environment loaded may not match the project.

Looking at the VSCode docs: https://code.visualstudio.com/api/extension-guides/debugger-extension
I don't see a way to control what the CWD of the debugger.sh script or a way to pass the projectDir to the script. So I'm not sure what an easy fix to this issue is.

Elixir Version:
Erlang/OTP 22 [erts-10.6.2] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [hipe]
Elixir 1.9.4 (compiled with Erlang/OTP 20)

Extension version: 0.2.28 (I've also tried downgrading)
Had same issue with Elixir 1.10.0 also.

VSCode(Stable latest release) has stopped showing compile error (underline highlights and error message) and @SPEC suggestions. They used work fine but I don't remember exactly when, for user it was with Elixir 1.9.4.

What all I have tried:

• I was running Elixir 1.10.0 on ubunut, installed asdf to downgrade to 1.9.4
• I have tried removing and regenerating the .elixirls, deps, and build folders
• PLTs were generated again
• Vim coc-elixir is working fine without any customization

Here is my mix file:

defmodule MyProject.MixProject do
  @moduledoc """
   Example:
  """
  use Mix.Project

  def project do
    [
      app: :my_project,
      version: "0.1.0",
      elixir: "~> 1.8",
      start_permanent: Mix.env() == :prod,
      deps: deps()
    ]
  end

  # Run "mix help compile.app" to learn about applications.
  def application do
    [
      extra_applications: [:logger]
    ]
  end

  # Run "mix help deps" to learn about dependencies.
  defp deps do
    [
      # {:dep_from_hexpm, "~> 0.3.0"},
      # {:dep_from_git, git: "https://github.com/elixir-lang/my_dep.git", tag: "0.1.0"}
      {:earmark, "~> 1.4", only: :dev},
      {:ex_doc, "~> 0.19", only: :dev},
      {:dialyxir, "~> 1.0.0-rc.7", only: [:dev, :test], runtime: false},
      {:credo, "~> 1.1.0", only: [:dev, :test], runtime: false}
    ]
  end
end

Here is the fresh ElixirLS log on cold start with the project in VSCode stable version.

Compiling with Mix env test
[Info - 12:30:54 PM] Compile took 61 milliseconds
[Info - 12:30:54 PM] [ElixirLS Dialyzer] Checking for stale beam files
[Info - 12:30:55 PM] [ElixirLS Dialyzer] Analyzing 0 modules: []
[Info - 12:30:55 PM] [ElixirLS Dialyzer] Analysis finished in 12 milliseconds
[Info - 12:30:55 PM] Dialyzer analysis is up to date
[Info - 12:30:56 PM] [ElixirLS Dialyzer] Writing manifest...
[Info - 12:31:00 PM] [ElixirLS Dialyzer] Done writing manifest.
[Error - 12:31:13 PM] Request textDocument/documentSymbol failed.
Message: an exception was raised:
** (SyntaxError) nofile:14: unexpected token: end
(language_server) lib/language_server/providers/document_symbols.ex:41: ElixirLS.LanguageServer.Providers.DocumentSymbols.list_symbols/1
(language_server) lib/language_server/providers/document_symbols.ex:35: ElixirLS.LanguageServer.Providers.DocumentSymbols.symbols/2
(language_server) lib/language_server/server.ex:442: anonymous fn/3 in ElixirLS.LanguageServer.Server.handle_request_async/2
Code: -32000

12:31:13.192 [error] Process #PID<0.1356.0> raised an exception
** (SyntaxError) nofile:14: unexpected token: end
(language_server) lib/language_server/providers/document_symbols.ex:41: ElixirLS.LanguageServer.Providers.DocumentSymbols.list_symbols/1
(language_server) lib/language_server/providers/document_symbols.ex:35: ElixirLS.LanguageServer.Providers.DocumentSymbols.symbols/2
(language_server) lib/language_server/server.ex:442: anonymous fn/3 in ElixirLS.LanguageServer.Server.handle_request_async/2

From the original: JakeBecker/vscode-elixir-ls#90

Is this considered after forked?
Personally I'm looking forward to the feature, so let me raise an issue for tracking.
(I may try working on the feature but need to grasp project structure first)

With the release of Phoenix 1.5 it's much easier to include LiveView

https://www.phoenixframework.org/blog/build-a-real-time-twitter-clone-in-15-minutes-with-live-view-and-phoenix-1-5

#83 adds the .html.leex filetype for syntax highlighting and filewatching

As a follow up on #22: This new issue is meant to track progress on expanding the entity.name.function-call.elixir scope added on #40 to function calls without parenthesis.
As exemplified here, while we can't disambiguate calls for niladic functions, we probably could do it for functions that have at least one parameter.

Example: The current behavior for greet/1 is that greet("Hello") will be scoped to entity.name.function-call.elixir while greet "Hello" will be scoped to source.elixir.

The language identifier guidelines state that language ids should be lowercase and contain no spaces.
https://code.visualstudio.com/docs/languages/identifiers#_new-identifier-guidelines

This causes issues with displaying icons for .html.eex files as noted here:
vscode-icons/vscode-icons#1414 (comment)

This was requested and implemented in a Pull Request on the vscode-elixir project.
timmhirsens/vscode-elixir#114 corrects the issue but was never merged.

The largest impact of this change is that other extensions that rely on the current identifier would have to be changed for support to continue.

Was there a larger reason this change hasn't occurred? The icon issue definitely persists.

Now that https://github.com/elixir-lsp/elixir-ls/ is the canonical repo we should remove the references to being a fork. Copy of elixir-lsp/elixir-ls#212

As a follow up on #22: This new issue is meant to track progress on adding a specific scope for "namespaces" to the Elixir grammar.

As previously discussed in the original issue, Elixir does not have namespaces as a builtin language construct, even though part of the module name it acts like it conceptually by convention. So, the objective is to provide an optional configuration to support further customization while keeping the current behavior as a fallback (if the configuration is not specified).

As @axelson suggested here, a better name could be "module prefixes", which captures the essence of the scope without compromising semantics about the language specification.

Notice that this should work for both module definitions and calls. It should also work for aliases, imports and requires.

Command+T allows to search for modules but it seems to be the default VSC functionnality. Using prefixes like f or t does not find anything.

Otherwise the outline panel shows all symbols without problem.

• Elixir & Erlang versions (elixir --version): Erlang/OTP 22 [erts-10.6.4] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [hipe] [dtrace]
• Elixir 1.10.2 (compiled with Erlang/OTP 22)
• VSCode ElixirLS Fork version: 0.3.2
• Operating System Version: darwin 18.7.0
• Visual studio:
  Version: 1.44.2
  Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
  Date: 2020-04-16T17:07:18.473Z (2 wks ago)
  Electron: 7.1.11
  Chrome: 78.0.3904.130
  Node.js: 12.8.1
  V8: 7.8.279.23-electron.0
  OS: Darwin x64 18.7.0

Hello, I use ASDF for elixir version management, and it seems this plugin is trying to use my global elixir version rather than the local version set by the .tool-versions and ASDF.

As described in issue here JakeBecker/vscode-elixir-ls#97 one would like to debug erlang/elixir node that is part of some cluster. I suggested to respect ERL OPTIONS env variable so it can be injected on application start.

Here is launch config I suggested

{
      "type": "mix_task",
      "name": "mix phx.server",
      "request": "launch",
      "projectDir": "${workspaceRoot}",
      "task": "phx.server",
      "startApps": true,
      "env":{
        "ELIXIR_ERL_OPTIONS": "-name [email protected]"
      }
}

At the moment, LS will never connect to node since this VS Code plugin will generate node name anyways and pass it to LS, and above would only make confusion. Probably it is the best way to be explicit in launch confing with dedicated attribute for sname or name flag for instance

{
     "type": "mix_task",
     "name": "mix phx.server",
     "request": "launch",
     "projectDir": "${workspaceRoot}",
     "task": "phx.server",
     "startApps": true,
     "nodeName": "[email protected]"
}

EDIT:

For the sake of the safety if node should connect to prod cluster, there can be also flag for "hidden" and nodeCookie, in case one would like to run hidden node in the cluster with all code up but don't want that node to participate in cluster workload.

{
     "type": "mix_task",
     "name": "mix phx.server",
     "request": "launch",
     "projectDir": "${workspaceRoot}",
     "task": "phx.server",
     "startApps": true,
     "erlOpts": {
           "name": "[email protected]",
           "cookie": "dskajhd98asd9ohasdh98hsad9",
           "hidden": true
     }
}

the list could go on :) for any erl flag

So user's no longer need the following setting:

"[elixir]": {
  "editor.acceptSuggestionOnEnter": "on"
}

Discussion in #51

Hey all,

Thanks for this awesome vs code plugin. Everything is working great, but I can't seem to be able to get it to accept suggestions on enter. I'm probably missing something simple, but I can't get it working.

Here is my vs code settings.json
{ "workbench.colorTheme": "dark+(elixir)", "editor.formatOnSave": true, "editor.acceptSuggestionOnEnter": "on" }

From reading the readme, it seems like that's all that should be required. Completeing with tab is working fine btw.

Edit: Enter is working to accept suggestions in .html.eex files, but not .ex files. Not sure if that helps

Hello. Are you planning add support iex -S mix debugging?

Environment

Erlang/OTP 22 [erts-10.4.1] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [hipe]
Elixir 1.10.0-dev (495148e) (compiled with Erlang/OTP 20)

VSCode ElixirLS Fork version: 0.3.3

Operating System Version:
Microsoft Windows [Version 10.0.18362.720]
WSL:
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"

Problem

No syntax highlighting for *.LEEX files (But changelog says it does.)

Highlight works fine on *.EEX files.

I read https://thinkingelixir.com/vs-code-broken-for-elixir/ but nothing there works, either.

Ideas?

Thanks.

The default was changed in ElixirLS but the default in this extension overrides that default.

I'm fairly new to VSCode, so maybe I'm using it wrong. I have a single project containing multiple microservices in different languages, several in Elixir. I'd eventually like to manage the whole thing in VSCode--launch Skaffold and deploy everything into Minikube, switch between Kotlin and Elixir services in different editor groups, etc.

Unfortunately, I can't see the Mix project directory setting in my workspace configurations.

Again, I'm new to VSCode. Maybe I should be opening each microservice in its own window, and should give up on trying to wrangle the whole thing in a single project. But it did work fine until we added another Elixir project, so I'm wondering how painful it'd be to run several separate language server instances and let me configure the Mix project directory per workspace. May take up more RAM, but that's wy I have 32 GB. :)

Or maybe workspaces are the wrong fix? Can I add .vscode/ directories in each subdirectory containing an Elixir project, then opening a file in one of those directories will automatically run the language server with the correct context, even if my project is still in a single tabbed window?

Thanks.

Hi! I'm getting what I believe is a false-positive warning:

I have a schema called "regions" that defines many "zones":

# region.ex
schema "regions" do
    field :name, :string
    has_many :zones, Zone
    timestamps()
end

# zone.ex
schema "zones" do
    field :name, :string
    belongs_to :region, Region
    timestamps()
end

I'm receiving the warning:

invalid association `zones` in schema Region: associated schema Zone does not have field `region_id`

Since the field region_id in the "zones" schema is inferred from the belongs_to association, I don't understand why this warning is necessary. Is this a problem!?

Setup Azure pipelines as specified in https://code.visualstudio.com/api/working-with-extensions/continuous-integration

The VS Code extension repeatedly loops, failing to build the core PLT file. It's attempting to write it to /.mix, rather than ~/.mix.

Environment

Version: 1.44.2
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T17:50:03.709Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.3.0-46-generic

• Elixir & Erlang versions (elixir --version): Erlang/OTP 22 [erts-10.7.1] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1]

Elixir 1.10.2 (compiled with Erlang/OTP 21)

• VSCode ElixirLS version: 0.3.3
• Operating System Version: linux 5.3.0-46-generic

Diagnosis

I cloned the vscode-elixir-ls project and added some tracing in elixir_plt_path():

JsonRpc.show_message(:info,
    "XDG_DATA_HOME is #{System.get_env("XDG_DATA_HOME")}, MIX_HOME is #{System.get_env("MIX_HOME")}, ~/.mix is #{Path.expand("~/.mix")}, Mix home is #{Mix.Utils.mix_home()}")

XDG_DATA_HOME is , MIX_HOME is /.mix, ~/.mix is /home/roger/.mix, Mix home is /.mix

This evaluates the environment variables used by Mix.Utils.mix_home/0. Now, it's fairly obvious that MIX_HOME is getting set somehow. But I'm not setting it:

$ env | grep MIX
$ 

If I explicitly set it:

$ MIX_HOME=$HOME/.mix code .

...then everything's fine. How can I debug/fix this problem?

The extension works fine on VS Code on my Mac, incidentally.

I have the following launch configuration setup:

        {
            "type": "mix_task",
            "name": "mix test current file",
            "request": "launch",
            "task": "test",
            "taskArgs": [
                "--trace",
                "${relativeFile}"
            ],
            "startApps": true,
            "projectDir": "${workspaceRoot}",
            "requireFiles": [
                "test/**/test_helper.exs",
                "test/**/*_test.exs"
            ]
        }

However when I run this, it runs all of my tests, not just the one in the currently open file.

Since this is missing from this package, and I think that this is the only package that you need to work with Elixir, will you be interested in adding a support for syntax highlighting in markdown code blocks?

There is an existing addon that this, but I think it might be good if it is integrated into this one, as I personally expected this to work, instead of looking for an additional package.

If you think that this is a good idea, I can create a PR

Thank you

The two extensions are not compatible so detect if vscode-elixir is installed and show a warning to the user.

Environment

• Elixir & Erlang versions (elixir --version): Erlang/OTP 22 [erts-10.7.1] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [hipe]

Elixir 1.10.3 (compiled with Erlang/OTP 21)

• VSCode ElixirLS Fork version: 0.3.2
• Operating System Version: linux 5.4.0-7626-generic

Troubleshooting

• Restart your editor (which will restart ElixirLS) sometimes fixes issues
• Stop your editor, remove the entire .elixir_ls directory, then restart your editor
  • NOTE: This will cause you to have to re-run the entire dialyzer build

If you have the following code:

IO.puts "🎧"

On save this gets formatted to:

IO.puts("🎧)"

But running mix format path/to/file.ex gives you:

IO.puts("🎧")

Currently the LS is built only once from master.

We need to check for updates and update/rebuild the LS when updates are available.

As the LS needs to be compiled with the appropriate version of erlang, try to pick and precompile proper LS version depending on the erlang configured in .tool-versions or whatever asdf tells us its using.

Hello,

I'm not sure if it's the right repo (vs elixir-lsp/elixir-ls) but since it's related to VS Code (with its Remote Dev Container features) I'm asking here.

Simply put, nothing happen with this extension when it's installed on the Remote Dev Container (and that the container is up and running etc.)

To contrast, if I disable (or uninstall) this extension on the container and use back the original one from jakebecker/elixir-ls), everything work out of the box.

Does this extension need something particular to set up and that I'm missing?

For example, the default installation folder when installed on a Dev Container is
~/.vscode-server/extensions rather than ~/.vscode/extensions. Could it be a problem with an harcoded path?

I have VS Code 1.43.2, Elixir 1.10, and this extension as 0.3.2

Thank you very much for the efforts! This tool improves my life greatly.

One thing I am wondering is whether it would be a good idea to start redirecting people who post on https://github.com/JakeBecker/vscode-elixir-ls over here. The current install count for VS Code is just under 73k whereas this most excellent fork is still under 4k.

Would it be valuable to you if I keep an eye on said repo and respond to new messages with a note directing them over here? I am thinking of something like the below:

Hello!

I am not a maintainer of this project but would like to let you know that this repository has been inactive since May 2019. There is a fork that is being actively developed by community members, and I recommend you switch over!

The GitHub repository is here:
https://github.com/elixir-lsp/vscode-elixir-ls

And the Visual Studio Code extension is here:
https://marketplace.visualstudio.com/items?itemName=elixir-lsp.elixir-ls

If you are having any issues or would like to open any pull requests, please try the new extension or clone the new repository first. You may find that the problem is already resolved 🙂

Thank you and happy Elixiring.

Would this be helpful? Any edits?

Keywords blocks following a pipe |> like case and if don't get highlighted.

The official language servers are named,

• Microsoft/vscode-html-languageservice
• Microsoft/vscode-css-languageservice
• Microsoft/vscode-json-languageservice

so I propose renaming this fork to vscode-elixir-languageservice. Community language servers don’t follow this convention but if we’re renaming to avoid collision, we might as well follow the official ones. Now would be the best time too, before word gets around.

This shouldn’t be confused with Microsoft/vscode-languageserver-node, which is a LSP implementation in Node.

Happy to submit a pull request but this involves changing the repo’s name too.

Is there any chance this PR can be merged here JakeBecker/vscode-elixir-ls#55 ?

I think the current syntax highlighting is not optimal, with the spec highlighting at the same 'level' as regular code. Having a more toned down highlighting would be ideal

Problem

The vscode-elixir-ls plugin debugger fails on a new phoenix application mix test task.

Reproduce

1. Create a new phoenix application

mix phx.new hello # accept when prompted
cd hello

2. Verify that mix test works in terminal

 mix test

# 13:12:05.053 [info]  Already up
# ...

# Finished in 0.07 seconds
# 3 tests, 0 failures

# Randomized with seed 130324

3. Verify that mix_test task fails in VS Code
   • .vscode/launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "mix_task",
            "name": "mix (Default task)",
            "request": "launch",
            "projectDir": "${workspaceRoot}"
        },
        {
            "type": "mix_task",
            "name": "mix test",
            "request": "launch",
            "task": "test",
            "taskArgs": [
                "--trace"
            ],
            "startApps": true,
            "projectDir": "${workspaceRoot}",
            "requireFiles": [
                "test/**/test_helper.exs",
                "test/**/*_test.exs"
            ]
        }
    ]
}

Started ElixirLS Fork debugger v0.3.1
Elixir version: "1.10.2 (compiled with Erlang/OTP 22)"
Erlang version: "22"
** Invalid beam file or no abstract code: 'Elixir.HelloWeb.PageControllerTest'
** Invalid beam file or no abstract code: 'Elixir.HelloWeb.ErrorViewTest'
** Invalid beam file or no abstract code: 'Elixir.HelloWeb.LayoutViewTest'
** Invalid beam file or no abstract code: 'Elixir.HelloWeb.PageViewTest'
(Debugger) Task failed because an exception was raised:
    ** (UndefinedFunctionError) function HelloWeb.PageViewTest.__ex_unit__/0 is undefined (module HelloWeb.PageViewTest is not available)
        HelloWeb.PageViewTest.__ex_unit__()
        (ex_unit 1.10.2) lib/ex_unit/runner.ex:118: ExUnit.Runner.run_module/2

Expected Behaviour

I expect the tests to execute in the same way as in the external terminal.

When I comment out all of the requireFiles, the task runs but I am unable to set breakpoints.

Environment

elixir -v  # Elixir version
# Erlang/OTP 22 [erts-10.6] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [hipe]
# Elixir 1.10.2 (compiled with Erlang/OTP 22)

mix phx # Phoenix version
# Phoenix v1.4.16

code -v # Microsoft Visual Studio Code version
# 1.43.0
# 78a4c91400152c0f27ba4d363eb56d2835f9903a
# x64

uname -srvmo # machine information
# Linux 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux

Name: ElixirLS Fork: Elixir support and debugger
Id: elixir-lsp.elixir-ls
Description: Elixir support with debugger, autocomplete, and more. Powered by ElixirLS.
Version: 0.3.1
Publisher: elixir-lsp
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=elixir-lsp.elixir-ls

There is an conflict with Code Spell Checker extension, (and maybe with other spell checkers as well).

When I have both extension installed, there is no grammar check in .ex and .exs files. I know the problem is caused by VSCode Elixir LS extension. Because when I disable it, I loose syntax highlight etc, but spell checker mark typos.

And big thank you for keeping this package alive!

Hey, thanks for the great editor support for elixir!

I faced with some UI missing feature. So straight to the details. If you have a simple non umbrella project then paths are relative to the project's root which is totally fine to hover and click on the path. But if you have an umbrella app then task output is relative to the application running the test, so you can't hover and click the path to open. Seems it comes from fileLocation in problem matcher(not 100% sure). Rapidly checking the doc didn't give me an insight how to handle this. And googling didn't give me the answer on "is it possible to show stacktrace with absolute paths?"

So the question now it is possible at all?