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

Render display of custom checkbox #19

Open
yoghurtdewdew opened this issue Aug 29, 2023 · 4 comments
Open

Render display of custom checkbox #19

yoghurtdewdew opened this issue Aug 29, 2023 · 4 comments

Comments

@yoghurtdewdew
Copy link

Sometimes it didn't render the same.

image image
@ivan-lednev
Copy link
Owner

Hello, @yoghurtdewdew,

Rendering is handled by Obsidian in this case, and I don't have control over that. My guess is that the markdown is broken in one of the examples you've sent. If you provide a minimal reproducible snippet of markdown, I can work on that.

@yoghurtdewdew
Copy link
Author

yoghurtdewdew commented Aug 29, 2023

Thank you for your reply! I tested and found that the problem may be due to a line of unbulleted text at the bottom of the unordered list, which makes the part above this line unrenderable:

image

Here are some snippets to test this:

search: match-case:line:("- [k] ")

render succeed:
- [k] 测试
	- [i] 测试
	- [>] 测试
	- 测试
	- 测试
	- [>] 测试

render unsucceed:
- [k] 测试
	- [i] 测试
	- [>] 测试
	- 测试 
	- 测试
	- [>] 测试
	- [>] 测试
测试

@ivan-lednev
Copy link
Owner

Okay, I see what's going on here...

When building cache for a file, Obsidian thinks that the last line is a part of the list:

- one
- two
last line

But Obsidian's markdown renderer thinks this is not a list at all.

I'd recommend installing a plugin called obsidian-linter and automatically adding a blank line after lists. I'll add a workaround if I have some capacity and more people express their grief about his.

@yoghurtdewdew
Copy link
Author

Okay, I see! Thanks for your advise! And yes I use obsidian-linter this plugin but I would prefer less blank lines. A lot of thanks if there would be some way to walk out this problem :)

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

No branches or pull requests

2 participants