Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

org-roam-unlinked-references doesn't work for Chinese sentence #1290

Open
Ualnomis opened this issue Nov 16, 2020 · 2 comments
Open

org-roam-unlinked-references doesn't work for Chinese sentence #1290

Ualnomis opened this issue Nov 16, 2020 · 2 comments
Assignees
Projects

Comments

@Ualnomis
Copy link

Description

Steps to Reproduce

Imagine I have two files like this

#+ TITLE: 二三四

This is 二三四
#+ TITLE: 四五六

一二三四五六
  1. Load doom-emacs
  2. Go to the roam file 二三四
  3. M-x org-roam-unlinked-references
  4. Nothing happens

Backtrace

Expected Results

The 二三四 of 一二三四五六 linked the 二三四

Actual Results

The unlinked reference buffer appears with none found references.

Environment

- Emacs: GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
 of 2020-09-19
- Framework: Doom
- Org: Org mode version 9.4 (nil @ /home/ualnomis/.emacs.d/.local/straight/build-27.1/org-mode/)
- Org-roam: 1.2.2
@Ualnomis Ualnomis changed the title org-roam-unlinked-references doesn't work for Chinese org-roam-unlinked-references doesn't work for Chinese sentence Nov 16, 2020
@randomwangran
Copy link

Hi @Ualnomis

If the content of the file, i.e. 二三四 is exactly the file you are testing with, it should do nothing because there is no link in that file.

I hardly use this function. If you just want to check the broken link, maybe this topic can give you some ideas.

@jethrokuan
Copy link
Member

This is because there's no word boundary between 二三四 within 一二三四五六.

I'll probably add this as a setting as part of the side buffer revamp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Org-roam
Backlog
Development

Successfully merging a pull request may close this issue.

3 participants