-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
Manual 'double up' arrow doesn't change task priority if followed by Variant Selector #2273
Comments
Thanks for using Tasks. There is descriptive text in your report that is not provided as text for me to copy, so for reasons explained in the following post, I am unable to investigate: https://publish.obsidian.md/tasks/Support+and+Help/Report+a+Bug If you can provide full text, and full numbered steps for a reproduction, as per the above, I will willingly have a look when I have time. Thank you. |
Specific steps to create the error
This is an anomoly, as if you use 🔼 or 🔽 at the end ofthe task, on opening the command palette and the tasks dialogue box, the task status is shown correctly as medium or low in the cases above. |
So the conclusion is that you are using an emoji which is similar in appearance to the one used by Tasks, but not the actual one it uses. What did you do to obtain the Emoji you are using? (Also, this is why we need to ask for precise steps to reproduce user feedback....) |
Actually, the ⏫️ character used by @JasonBates is the right one. However, it is followed by an invisible so-called variant selector VS16 which essentially says that the preceding character should be interpreted as an emoji. It seems that Tasks gets confused by this modifier, and we should probably fix this. |
Wow, thanks @Cito - how were you able to work this out? I have been hunting for a way on Mac to show the actual underlying characters, and not succeeded.... |
This may be useful, although it is a lot to take in: |
To create the emoji, I used ctrl + cmd + space on a Mac, and then selected the emoji from the selector. It’s interesting was that this method works for the single up arrow and the single down arrow, changing the priority as expected, but doesn’t work for the double up arrow. Thanks 🙏 |
You can copy&paste this into a string literal in a JavaScript or Python file and then examine it using Or you can use this very helpful online tool: https://apps.timwhitlock.info/unicode/inspect |
I've added the 'help wanted' label to this. It's outside my zone. |
This has just cost me half an hour, writing some tests for new code in Tasks! |
Suggestion from @therden that calling |
The following has a variant selection in it:
I tried all these, one at a time, and for me, none of them removed the variant selector: const allTasks = createTasksFromMarkdown(markdown.normalize('NFC'), 'filename.md', 'header');
const allTasks = createTasksFromMarkdown(markdown.normalize('NFD'), 'filename.md', 'header');
const allTasks = createTasksFromMarkdown(markdown.normalize('NFKC'), 'filename.md', 'header');
const allTasks = createTasksFromMarkdown(markdown.normalize('NFKD'), 'filename.md', 'header'); |
There's an interesting new issue related to this: It's the opposite way round though. We have ended up with an emoji in the Tasks code that includes VS16 - and Tasks is failing to parse values from any lines that have the emoji without VS16 ⛔ - I am investigating. |
Just released in Tasks 6.1.1. |
Please check that this issue hasn't been reported before.
Expected Behavior
Appending a double up arrow to the end of a task should give that task a high priority
Current behaviour
Appending a double up arrow to a task does not change the task priority.
This is an anomoly as:
BUT ... manually appending a double up arrow to a task does not change the priority of a task in the way that other emojis like the single up arrow does.
Steps to reproduce
Create task with double up arrow manually appended to the end of a task
Create a dataview listing of that task
check the priority assigned
Which Operating Systems are you using?
Obsidian Version
1.4.13
Tasks Plugin Version
0.1.16
Checks
Possible solution
No response
The text was updated successfully, but these errors were encountered: