You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thank you for this great plugin. It makes my life easier for sure. Especially, I love how it blurs the boundary between note-taking and note-naming.
I noticed that, under some circumstances, this plugin causes an infinity loop like this:
Screen.Recording.2023-09-19.at.1.23.29.mov
At first, the heading is
# [[hello]]
Then, this plugin renames the note "hello.md" because the square brackets are illegal characters.
At this point, the link in the heading points to this note itself.
Then, I add some text to this heading:
# [[hello]] world
Now this plugin renames the note "hello world", which triggers Obsidian's link updates. As a result, we get
# [[hello world]] world
And this process (theoretically) never ends.
So it would be great if this plugin could take care of this kind of stuff.
One possible (imperfect) solution would be, instead of hooking on the vault.on('modify'), running the sync when the cursor moves from a heading line to a non-heading line.
The text was updated successfully, but these errors were encountered:
Hi, thank you for this great plugin. It makes my life easier for sure. Especially, I love how it blurs the boundary between note-taking and note-naming.
I noticed that, under some circumstances, this plugin causes an infinity loop like this:
Screen.Recording.2023-09-19.at.1.23.29.mov
At first, the heading is
Then, this plugin renames the note "hello.md" because the square brackets are illegal characters.
At this point, the link in the heading points to this note itself.
Then, I add some text to this heading:
Now this plugin renames the note "hello world", which triggers Obsidian's link updates. As a result, we get
And this process (theoretically) never ends.
So it would be great if this plugin could take care of this kind of stuff.
One possible (imperfect) solution would be, instead of hooking on the
vault.on('modify')
, running the sync when the cursor moves from a heading line to a non-heading line.The text was updated successfully, but these errors were encountered: