rust-analyzer expands with "$0"

[otavio]

Hello,

I am using rust-analyzer and when I am doing auto-complete, it is expanding to: run_with_archive($0).

No idea where the $0 comes from.

Logs below:

Command "rls" is present on the path.
Command "rust-analyzer" is present on the path.
Command "rls" is present on the path.
Command "rust-analyzer" is present on the path.
Found the following clients for /home/otavio/src/compress-tools-rs/src/lib.rs: (server-id rls, priority -1), (server-id rust-analyzer, priority 1)
The following clients were selected based on priority: (server-id rust-analyzer, priority 1)

[Trace - 06:25:10 PM] Sending request 'textDocument/codeAction - (133)'.
Params: {
  "textDocument": {
    "uri": "file:///home/otavio/src/compress-tools-rs/src/lib.rs"
  },
  "range": {
    "start": {
      "line": 87,
      "character": 24
    },
    "end": {
      "line": 87,
      "character": 24
    }
  },
  "context": {
    "diagnostics": [
      {
        "source": "rust-analyzer",
        "severity": 1,
        "range": {
          "start": {
            "line": 87,
            "character": 21
          },
          "end": {
            "line": 87,
            "character": 21
          }
        },
        "message": "Syntax Error: expected expression"
      },
      {
        "source": "rust-analyzer",
        "severity": 1,
        "range": {
          "start": {
            "line": 87,
            "character": 22
          },
          "end": {
            "line": 87,
            "character": 22
          }
        },
        "message": "Syntax Error: expected SEMI"
      },
      {
        "source": "rust-analyzer",
        "severity": 1,
        "range": {
          "start": {
            "line": 87,
            "character": 23
          },
          "end": {
            "line": 87,
            "character": 23
          }
        },
        "message": "Syntax Error: expected SEMI"
      },
      {
        "source": "rust-analyzer",
        "severity": 1,
        "range": {
          "start": {
            "line": 87,
            "character": 23
          },
          "end": {
            "line": 87,
            "character": 23
          }
        },
        "message": "Syntax Error: expected expression"
      },
      {
        "source": "rust-analyzer",
        "severity": 1,
        "range": {
          "start": {
            "line": 87,
            "character": 24
          },
          "end": {
            "line": 87,
            "character": 24
          }
        },
        "message": "Syntax Error: expected SEMI"
      }
    ]
  }
}


[Trace - 06:25:10 PM] Received response 'nil - (132)' in 999ms.
Result: []


[Trace - 06:25:10 PM] Received response 'textDocument/codeAction - (133)' in 21ms.
Result: []

[yyoncho]

This usually happens when yasnippet is not present, can you check that? Also, can you check if it reproduces with lsp-start-plain.el?

[otavio]

Sure, however, I disabled it:

;; set prefix for lsp-command-keymap (default is "s-l")
  (setq lsp-keymap-prefix "C-c l")

  (use-package lsp-mode
    :ensure t
    :diminish lsp-mode
    :config
    (setq lsp-enable-snippet nil)
    (setq lsp-enable-file-watchers nil)
    (setq lsp-prefer-flymake nil)
    (setq lsp-prefer-capf t)

      ;;; Rust specifics
    (setq lsp-rust-server 'rust-analyzer)

    :hook (;; reformat code and add missing (or remove old) imports
           (before-save . lsp-format-buffer)
           (before-save . lsp-organize-imports)
           ;; modes
           (rust-mode . lsp)
           ;; if you want which-key integration
           (lsp-mode . lsp-enable-which-key-integration))
    :bind (("C-c e" . lsp-execute-code-action))
    :commands lsp)

I set (setq lsp-enable-snippet nil). Shouldn't this respect it?

[flodiebold]

rust-analyzer currently doesn't support completion without snippets.

[otavio]

Makes sense, it'd be good to add a note about it on README, so we avoid this same issue for other users?

[brotzeit]

Would the wiki also be ok ? The readme is quite bloated.

[otavio]

Well, I'd add on both. But not my call.

For me the issue is solved but likely other people can fall on this...