emacs-lsp / lsp-metals

lsp-mode :heart: metals
https://emacs-lsp.github.io/lsp-metals
GNU General Public License v3.0
58 stars 34 forks source link

Run/Debug leads to Wrong type argument: stringp, nil #11

Closed d12frosted closed 4 years ago

d12frosted commented 4 years ago

Describe the bug When using lens actions (run or debug) leads to error Wrong type argument: stringp, nil and run/debug doesn't start.

To Reproduce

  1. Update all packages to the latest version.
  2. Install latest release of metals-emacs.
  3. Open any project with the following scala code.
  4. Enable lsp-lens-mode.
  5. Click on 'run'.
object LensTest extends App {
  println("hello world")
}
(use-package scala-mode
  :hook
  (scala-mode . subword-mode)
  (scala-mode . lsp))

(use-package lsp-metals
  :after scala-mode)

(use-package lsp-ui
  :defer t
  :commands lsp-ui-mode)

(use-package lsp-mode
  :defines (lsp-session-file)
  :init
  (setq lsp-auto-guess-root t))

Expected behavior The application should run 😸

Screenshots Screen Recording 2020-06-24 at 17 44 10

Logs Stack trace is not useful for me. Not sure how to better debug the problem.

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  intern(nil)
  #f(compiled-function () (interactive nil) #<bytecode -0x2ef46e78e656b28>)()
  funcall-interactively(#f(compiled-function () (interactive nil) #<bytecode -0x2ef46e78e656b28>))
  call-interactively(#f(compiled-function () (interactive nil) #<bytecode -0x2ef46e78e656b28>) nil nil)
  command-execute(#f(compiled-function () (interactive nil) #<bytecode -0x2ef46e78e656b28>))
d12frosted commented 4 years ago

@yyoncho thank you very much, that PR fixes the problem!