Skip to content

Fix markdown_language_map not working - #2924

Merged
rchl merged 1 commit into
sublimelsp:mainfrom
jfcherng-sublime:fix/settings/markdown_language_map
May 23, 2026
Merged

rchl merged 1 commit into
sublimelsp:mainfrom
jfcherng-sublime:fix/settings/markdown_language_map

Conversation

@jfcherng

@jfcherng jfcherng commented May 22, 2026 •

Copy link
Copy Markdown
Contributor

Following https://lsp.sublimetext.io/migrating_to_lsp_plugin/#12-replace-markdown_language_id_to_st_syntax_map-with-the-markdown_language_map-setting , but the markdown_language_map setting doesn't work.

The constructor assigned directly to self._markdown_language_map, skipping the property setter and leaving resolved_markdown_language_map always None. Also fixed a spurious debug warning when lang_map is None.

…he setter

The constructor assigned directly to `self._markdown_language_map`,
skipping the property setter and leaving `resolved_markdown_language_map`
always None. Also fixed a spurious debug warning when lang_map is None.

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Jack Cherng <jfcherng@gmail.com>
@rchl
rchl merged commit f6ab9f9 into sublimelsp:main May 23, 2026
8 checks passed
@jfcherng
jfcherng deleted the fix/settings/markdown_language_map branch May 23, 2026 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants