Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature: lsp-doctor to include check for lsp-java-java-path

Open
  • Is something wrong?
#479 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
emacs-lisp, java
Domain
developer-experience

Research direction

Start at the lsp-doctor entry point and inspect how lsp-java-java-path is handled when lsp-java is loaded. Reproduce the missing-runtime configuration from the issue and make the doctor report whether the configured Java path exists, matching the expected diagnostic wording.

Written by the indexing model from the issue text.

Description

Describe the bug
I spent hours debugging why Emacs failed to give me the full LSP experience. It only said:

make-process--with-editor-process-filter: Doing vfork: No such file or directory

I could find no log/error/message buffer that gave me a hint as to what file or directory that wasn't found. The way I found out, was to bisecting my .emacs.

I thus believe it would be a great improvement if lsp-doctor could check if the Java runtime could be found (when lsp-java has been loaded)

To Reproduce

;; insert the quick start guide .emacs snippet from the README.md

;; then, set a non-existing Java path
(setq lsp-java-java-path "/usr/lib/jvm/java-does-NOT-exist-openjdk/bin/java")

Expected behavior
The doctor should find what's wrong (granted lsp-java is loaded):

M-x lsp-doctor
..
lsp-java could find valid Java runtime: NOT (/usr/lib/jvm/java-does-NOT-exist-openjdk/bin/java does not exist, configure lsp-java-java-path to point to a valid java runtime).
Dominant language
Emacs Lisp
Stars
696
Forks
97
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from emacs-lsp/lsp-java

All issues in emacs-lsp/lsp-java

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.