[Question]: When using the Tasks plugin for auto-completion, it prompts "Failed to save file."

[xyy-1997]

Bug Description | BUG 描述

• 场景：在Thino的输入框中输入待办事项
• 描述：
  • 无法使用 Ctrl + L 快捷键直接切换待办事项列表
  • 手动输入“- [ ]” 后，使用 Tasks 插件的自动补全功能插入优先级或其他信息时报错 “Failed to save ...”
  • 上述输入的待办事项无法在 Tasks 的查询代码中显示
• 新建一个md文档后重复上述步骤不会报错，Tasks插件也能正常工作

Relevant Screenshot | 相关截图

To Reproduce | 重现问题

No response

Obsidian Version | Obsidian 版本

1.6.3

Which editor are you using? (If applicable)

• [X] New Editor (WYSIWYG) | 新编辑器
• [ ] Legacy Editor (Markdown) | 旧编辑器

Checklist

• [X] I updated to the latest version of the plugin. 我更新到了插件的最新版本。

[xyy-1997]

经过后续测试发现，重开一个库之后，在kanban文件中也会发生第2、3个bug，但是第一个bug确实是Thino的问题。极大可能是Obsidian更新导致的tasks插件的bug

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically...

---

After subsequent testing, it was found that after reopening a library, the second and third bugs would also occur in the kanban file, but the first bug was indeed a Thino problem. It is most likely a bug in the tasks plugin caused by the Obsidian update.

[juestchaos]

无法使用 Ctrl + L 快捷键直接切换待办事项列表，是可以的 而且这不是 task 插件的功能，是ob 默认自带的。

如图这里可以通过快捷键切换

[xyy-1997]

无法使用 Ctrl + L 快捷键直接切换待办事项列表，是可以的 而且这不是 task 插件的功能，是ob 默认自带的。

如图这里可以通过快捷键切换

那看来是我这边环境的问题，我试了pc端和安卓都不行，可能是某个插件冲突了

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically...

---

It is not possible to use the Ctrl + L shortcut keys to directly switch to the to-do list, but it is possible. And this is not a function of the task plug-in, but comes with ob by default.

As shown in the figure, you can switch through shortcut keys


It seems to be a problem with my environment. I tried both PC and Android but it didn't work. It might be a plug-in conflict.

[juestchaos]

欢迎你测试出来是哪个插件后告诉我们，我们会记录在 faq 中，方便提醒其他用户，或者尝试联系哪个插件的作者兼容

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically...

---

You are welcome to tell us which plug-in is compatible after you test it. We will record it in the FAQ to remind other users, or try to contact the author of which plug-in is compatible.