logseq / logseq/db-test

[macOS] Markdown shortcuts for code, codeblock, strikethrough and others not working on international keyboard layouts

Open
#1,021 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

When an international keyboard layout such as BR or US International is active, there's no way to use backticks and tildes, for example, as shortcuts for inline code and code blocks, strikethrough, etc.

After adding any special character such as those in a block, the block starts behaving in an unexpected way, hiding text, for example.

### Reproduce the Bug

1. On macOS, go to "Keyboard" and change the layout to Portuguese (Brazilian) or English (US International - PC), for example.
2. In Logseq, try to use backticks (`) for inline code or a code block, or tilde (~) for strikethrough in any block.
3. More than one character is added, and the block starts behaving in an unexpected way.

### Expected Behavior

The markdown shortcuts were supposed to work as expected because, on international keyboards, the character is only "resolved" after we press the "space" key. That way, if I want to have something like `inline code`, the expected behavior would be: backtick + space + "inline code" text + backtick + space

### Screenshots

https://github.com/user-attachments/assets/48bcac36-53e3-4a06-93bb-7e6ff1d26ca1

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

macOS Tahoe 26.5.2
Logseq Desktop App, version 2.0.1

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [x] I'm willing to submit a PR (Thank you!)

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

No source files or tests are identified in the report. First reproduce the shortcut behavior in the Logseq Desktop App on macOS using Portuguese (Brazilian) or US International - PC layouts, then trace the markdown shortcut handling. Done means backticks and tildes produce only the intended inline-code, code-block, and strikethrough shortcuts without hiding or duplicating text.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, markdown
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.