Thanks for you advice above. It was simple to change my logical expressions accordingly. The update will be a simplification for new users.
When I use Kanban mode, it shows everything except the open items, which is the thing I would most want to see.
Also, to use the YesYouKan plugin, I have to manually add the special tag at the bottom. Guess it’s not that big of a deal.
Thanks!
Thanks for reporting @MarkS, I haven't been able to reproduce it.
- Do you see the open checkboxes in the search panel (but not in the note view)?
- Do you see them in the note view (but not on the kanban)?
- Could you provide an example text + example search query that do not work?
The search panel seems to work fine! The note view is not creating kanban entries for open check boxes.
I have a note like this:
- [ ] World rescue project +TEST
- [x] Save the cheerleader +TEST
- [ ] Save the world +TEST
Then I have a ITN query like this:
{"query":[[{"tag":"+test","negated":false}]],"filter":"\"- [ ]\"","displayInNote":"kanban"}
The result is this:
<!-- itags-results-start -->
# Done
## Save the cheerleader
+test
[Test project (L3)](:/71dff83468ae453fb5c6f1c0eb5b667b)
<!-- itags-results-end -->
The two checkboxes that are still open are not included in an “open” section.
The kanban thus looks like this:
Thank you!
This was a sneaky one, but it will get fixed in the next release.
For now, you can work around the issue by disabling the setting Note view: Highlight filter results.
v2.10.0
- added: query mode 'CNF', AND of groups of tags (default for new queries)
- added: right-click in query area to switch between AND (all groups) and OR (any group) modes
- see screenshot
- added: shift+click on nav panel tag to insert into editor (#35)
- improved: focus command shows search panel if hidden
- improved: return focus to editor when hiding nav/search panels
- improved: search tag at cursor keyboard shortcut (Ctrl+Alt+T) (#35)
- fixed: filter highlighting breaking kanban note views
- fixed: quoted filter phrases were case-sensitive
The mismatched </span> tag seems to still be happening.
In list display mode, checkboxes are not rendered as checkboxes (in note display, not the panel)
Hope this helps!
Edit: The mismatched span tag seems to be important – If I delete it, the rendered text disappears.
Thanks @MarkS. Are you sure they are mismatched? All the queries I save start with <!-- itags-query-start --><span style="display: none">. In the Markdown preview, do you see the query displayed?
This might be related to this setting: Note view: Highlight filter results (try to disable it). You are most likely filtering by open checkboxes and highlighting them at the same time.
Oh, I see. The </span> is highlighted and stands out. The starting tag isn’t and so I missed it.
Turning off Highlight filter results restores the rendering of the checkboxes, so all’s good!
Thank you!
Glad to hear @MarkS. I see that highlighting in note views is enabled by default (to match the behaviour of the panel). I might change the default to off to avoid these confusing edge cases.
Do you think there’s any possibility that you will ever have a true per-item option? That is items that are no longer contained by their note.
Right now you can split per-item, but all the filtered items are grouped by the note they are in. So if you have two projects, each in it’s own note and each of which has several date items, and you sort them by date, you do not get an all-up list, but a list of items within the context of each note. This makes it harder to tell if two items are close to each other in time, or if there is some sort of conflict. And of course, in reality you might have several notes, all of which have multiple items with multiple dates, making it even more confusing.
Thanks!
Oh, that’s great!
Thank you!
I have angered the Inline Tag Navigator plugin. It will work just fine if I remove the plugin, restart Joplin, then add the plugin back, but then after a bit it will stop responding. At that point the Refresh button will not function and I can no longer toggle Search or Navigation. I haven’t seen anything in the Joplin logs to help me figure out what I have done to anger it (I did recently start using your amazing plugin even more in my notes than I had in the past). Do you have any recommendations for where I could look to determine how to get myself back into a good state?
Welcome @sbeauregard! Sorry to hear about your issues. A few questions that may help me:
- What platform and Joplin version are you using? (desktop/mobile, OS, Joplin version)
- Does simply restarting Joplin (without removing/reinstalling the plugin) also fix it? This would help distinguish between a runtime issue vs something persisted.
- Roughly how many notes do you have? You mentioned using the plugin more heavily - are we talking hundreds or thousands of tagged notes? How many tags?
- I'm assuming that you followed this page when checking the logs, and looked for messages that refer to
joplin.plugin.alondmnt.tag-navigator.
Note that I also released v2.10.1 with a couple of patches. Although I don't know if they are related to your issue, maybe it's worth testing it.
I am using Joplin for Desktop 3.5.13 (prod, win32) on Windows 11 with Inline Tag Navigation 2.10.0
Restarting Joplin also fixes the issue.
I have 2795 notes and about 100 tags. I use Front Matter tags almost exclusively.
I will leave the development tools open until I see the issue occur and see if I get anything in the logs.
Thanks.
A problem with display on Android, that I believe is happening because of ITN.
Open a note with checkboxes. Check or uncheck a box. Count 10 seconds. The box reverts to its previous state. Although the appearance has changed, if you leave the note and go back in, it will be at the last (correct) state. Except that you don’t know what state it’s in when you’re working with it.
Disabling ITN stops this from happening. That is why I suspect ITN is the source of the behaviour.
Thank you!
Plugin version: v2.10.1
I tried version 2.10.1 and the plugin stopped working in the same way after some time. Still nothing in the logs when it stops working.