Closed d12frosted closed 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.
run
debug
Wrong type argument: stringp, nil
To Reproduce
metals-emacs
lsp-lens-mode
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
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>))
@yyoncho thank you very much, that PR fixes the problem!
Describe the bug When using lens actions (
run
ordebug
) leads to errorWrong type argument: stringp, nil
and run/debug doesn't start.To Reproduce
metals-emacs
.lsp-lens-mode
.Expected behavior The application should run 😸
Screenshots![Screen Recording 2020-06-24 at 17 44 10](https://user-images.githubusercontent.com/6507913/85578457-bd679380-b642-11ea-9ff0-2c4e16a72c95.gif)
Logs Stack trace is not useful for me. Not sure how to better debug the problem.