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

Multi-line Strings Break lsp-execute-code-action

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
emacs-lisp, java
Domain
developer-experience, devtools

Research direction

Reproduce the issue with the shown Main.java example, then start from the lsp-execute-code-action path and the c-clear-string-fences error reported in the Emacs messages buffer. Trace how multiline strings affect the action and marker handling; done means missing Java objects are populated successfully while the multiline string remains present.

Written by the indexing model from the issue text.

Description

Describe the bug
Multi-line String literals completely breaks lsp code actions.

To Reproduce

  1. Create an example directory.
  2. Inside create a Main.java file.
  3. Inside Main.java create the following Main class.
class Main {
  List<Object> l = new ArrayList<Object>();
}
  1. Call lsp-execute-code-action, import the dependencies and notice the code actions still working.
  2. Remove the imported objects and Create a multiline String. Your file should now look like this:
class Main {
  List<Object> l = new ArrayList<Object>();
  String s = """
    hello
    """;
}
  1. Attempt to lsp-execute-code-action once again.

From here, you'll see an error message in the mini buffer and messages buffer similar to the following:

c-clear-string-fences: Args out of range: #<marker (moves after insertion) at 131 in Main.java>, #<marker (moves after insertion) at 131 in Main.java>

Expected behavior
Emacs should populate the missing objects like normal.

Logs
I think this is purely a client error as there are no lsp errors, but errors generated by emacs.

Work-Around

Comment out all the multiline strings and revert the buffer. You will now be able to execute code actions once again.

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.