Typing block macros (e.g. `#+BEGIN_NOTE`) incorrectly creates a tag with that name
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
- I searched and no similar issues were found
What Happened?
When typing a standard block macro or directive in the editor (such as #+BEGIN_NOTE, #+BEGIN_TIP, etc.), Logseq DB automatically creates a tag with that name (#+BEGIN_NOTE). These macro syntax elements should be treated as block wrappers/directives, not as user-created tags. The same issue affects all other BEGIN_ macros.
Reproduce the Bug
- Open any page or node in the editor.
- Type
#+BEGIN_NOTEand press Shift+Enter - Check your tags or property/tag suggestions.
Observed: A tag named #+BEGIN_NOTE (or similar) is created/registered in the system.
Expected Behavior
Typing #+BEGIN_* directives or block macros should format them as block wrappers or syntax tokens, without creating a corresponding tag in the database.
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
- Platform: Linux Desktop
- Version: 2.0.1-alpha+nightly.20260917 (DB beta)
Additional Context
This affects all BEGIN_ macros (e.g., note, warning, quote, etc.), polluting the user's tag space with formatting syntax.
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the editor with #+BEGIN_NOTE and Shift+Enter, then trace the tag or property/tag suggestion registration path. Verify the behavior across other BEGIN_ macros; done means these directives remain block wrappers or syntax tokens without creating database tags.
Written by the indexing model from the issue text.
Assessment
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100