leanprover / leanprover/vscode-lean4

Rename symbol dialog does not do unicode input translation

Open
#690 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
313
Forks
104
Avg merge
1h 56m
Merged PRs (30d)
1

Description

Description

When I want to rename a symbol (by pressing F2), I cannot easily input a unicode identifier, the unicode input sequences are not translated. If I try to type the sequence and press enter anyway, I get the following error:

Failed to process request 10622: Can't rename: \ph\1 is not an identifier

Context
Steps to Reproduce
  1. Press F2 over an identifier.
  2. Type \ph\1

Expected behavior: The input is changed to φ₁

Actual behavior: The input stays exactly as typed.

Versions

[Version of vscode-lean4 (Hover over 'lean4' in the 'Extensions' menu)] v0.0.220
[Output of lean --version in the folder that the issue occured in] Lean (version 4.24.0, commit v4.24.0, Release)
[OS version] NixOS 25.05 (Warbler)

Impact

Minor annoyance. The workaround is to type the identifier in the editor somewhere else, and copy-paste it into the rename dialog

Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The payload names no file or test; begin at the VS Code F2 rename dialog entry point and reproduce the issue with \ph\1 over an identifier. Done means the dialog translates the sequence to φ₁ and the rename request succeeds instead of reporting that the input is not an identifier.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.