-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Auto Jump To Cursor Issues with daily notes #1112
Comments
I am seeing this occur intermittently with version 1.16.0 (current as of my writing this). It didn't occur until I modified my template and dug into settings recently, although since it is intermittent, I can not say what edit or setting change triggered the bug. |
I use |
As a bit of information: I have not seen the issue recently. It is plausible it has been resolved, or was due to a conflict with some other Plugin that I no longer use (I wish there was an option to clear all but one plugin for testing purposes for this reason). |
I still have this issue, as described here: #1232 (comment) |
I disable all my extensions but templater, the issue still exists. |
@joyous-coder Is it the same issue as described in #1232 where you're in reading mode, and therefore there is nowhere to put your cursor? |
Hi there,
I have a daily note template that looks like this:
`---
Aliases: <% tp.date.now("YYYY-MM-DD") %>
[[ <% tp.date.now("YYYY-MM-DD - ddd MMM D", -1, tp.file.title, "YYYY-MM-DD - ddd MMM D") %>|Yesterday]] | [[<% tp.date.now("YYYY-MM-DD - ddd MMM D", 1, tp.file.title, "YYYY-MM-DD - ddd MMM D") %>|Tomorrow]]
<% tp.file.cursor() %>`
I have "automatic jump to cursor" enabled as well as "trigger templater on new file creation."
When I trigger this template manually everything works as expected. However, when the note is created automatically via calendar plugin or "open today's daily note" in the command palette, the note is created, the cursor jumps to the correct place, but then the text "<% tp.file.cursor() %>" is re-inserted to the file. Does anyone know what would be causing this?
The text was updated successfully, but these errors were encountered: