Plugin: Inline Tag Navigator [v2.10.6, 2026-05-16]

Noted. Thank you very much.

I just published a fix (v2.6.2). It's not perfect (sometimes the diagram jitters a bit on load, or renders a bit wide), but it should bring back mermaid rendering on mobile. I'll see if I have a better fix in a future release.

It’s so much better now. Thank you for taking the time to fix it.

@shikuz hi!

Can you please help me with syntax in the “Filter” field?

I have nested notebooks like this:

  • Parent
    • Child

When I write in “Filters” = “Parent/” - I see only lines from notes inside Parent, but not Child.

UPD: Sorry, just found the answer: I should set the “Search: Extract the full notebook path” setting ON. With this setting, it works.

v2.6.3

  • added: nested tag support for date tags (FR #24)
  • improved: memory management

@shikuz hi! Is it possible to make for the Case 2 the same Search result, as it was in the Case 1? So the main task will be visible. Does it create any unexpected errors? Because now it is difficult to use with nested listings.

UPD: Alright, I withdraw my question. Even if it's technically possible to do, the search by tag in the top-level line and simultaneously by tag in the bottom-level line won't work. Combining tag searches across two different lines seems to me to be a much more complex task. I'll try to keep writing everything in a single line. Even if it looks a bit unstructured.

Thanks @tnwn, I had thought about this bottom-up inheritance of tags in the past, but ended up finding of all kinds of edge cases, and decided that the implementation would be a little more complex than I find it worth (still possible).

That said, I do plan (hopefully) to add a feature to expand the context around search results. This way, you could see more of the note where the results originated, including parent list items, or parts of the text that inform the tagged line.

v2.7.0

  • added: context expansion for search results
    • click ↑ next to results to view more from the note (up to 3 expansion steps)
    • customise length in the settings
  • added: CSS styling for core and context lines
  • added: search status panel messages
  • added: HTML sanitisation for search results
  • improved: settings descriptions with examples
  • improved: panel and dialog styling

standard search result

with expanded context (↑)

Just a quick bug or feature issue for me. I sometimes highlight and/or color tags in my notes. I see those are not found in v2.7.0. I’m sure the html or markdown formatting wrapper is the issue (<span…..>#mytag or ==#mytag==).
Great plugin!

Thanks @djsudduth, it was due to strict HTML sanitsation. It should be resolved in v2.7.1.

Still not working for either case in 2.7.1. Examples in my notes:
1 —–

The existence of numberless visible stars can prove nothing against the existence of numberless invisible ones. <span style="color: #e03e2d;">#project</span>

Bessel roughly estimated the period of the companion of

Example 2:

t will pass through a red giant stage and eventually become a white ==#dwarf==.

Thanks for clarifying @djsudduth. I thought you were reporting on a regression (which was correct! :grinning_face_with_smiling_eyes: styling was more restricted in v2.7.0).

While by default the plugin does not expect inline styling of tags (all tags look the same), what you want can actually be achieved via configuration.

  1. You need to ensure that tags are recognised when they are adjacent to HTML/Markdown tags (by default, they must be preceded by whitespace). To do so, in the Tag Navigator advanced settings set the Tag regex setting to (?<=^|[\s>=])#([^\s#'",.()\[\]:;\?\\=]+).
  2. You need to allow tags' font color to be customised. To do so, in the Tag Navigator advanced settings set the Search: Panel style setting to: .itags-search-renderedTag {color: inherit}.

Now, inline tag styles like <span style="color:#e03e2d">#project</span> (no space between the color: field and its value), and ==#project== work for me.

A little help needed here… I'm not sure what's going on but I'm not getting tags rendered in the editor anymore. I have the required rich markdown plugin installed according to the instructions here

***

***

Joplin Mobile 3.5.9 (prod, android)

Device: android

Client ID: 501fbde695fb4216b98eb0351cc00e56

Sync Version: 3

Profile Version: 49

Keychain Supported: No

Alternative instance ID: -

Revision: 4dc021b52 (release-3.5)

Admonition markdown extension: 1.1.0

AlertsPerfect: 1.0.1

CodeMirror 6 snippets: 0.1.0

Collapsible Sections: 1.9.3

Easy Backlinks: 1.3.1

Github Alerts: 1.0.5

History Panel: 1.0.4

Inline Tag Navigator: 2.7.3

New Random Note Viewer: 1.0.0

Quick Links: 1.3.2

Rich Markdown: 0.15.0

Secure Notes: 1.2.4

Android API level: 33

WebView version: 144.0.7559.59

WebView package: com.google.android.webview

FTS enabled: 1

Hermes enabled: 1

@xpleromax could you check in your Rich Markdown settings if Theme is set to "Stylish"?

I attached a screenshot of my settings and the code I copied from the custom settings.

[   {     "name": "rm-tag-hash",     "regex": "(?<=^|\\s)[#]([^\\s#@+'\",.()\\[\\]:;\\?\\\\]+)"   },   {     "name": "rm-tag-plus",     "regex": "(?<=^|\\s)[+]([^\\s#@+'\",.()\\[\\]:;\\?\\\\]+)"   },   {     "name": "rm-tag-at",     "regex": "(?<=^|\\s)[@]([^\\s#@+'\",.()\\[\\]:;\\?\\\\]+)"   },   {     "name": "rm-tag-slash",     "regex": "(?<=^|\\s)(\\/\\/)([^\\s#@+'\",.()\\[\\]:;\\?\\\\]+)"   } ]

I see! The mobile version of Rich Markdown that I prepared only has the style for rm-tag already predefined. Since, unlike on desktop, you cannot define custom CSS on mobile, you should avoid (on mobile only) class names like rm-tag-hash, rm-tag-at, etc.

How do we filter for unchecked checkboxes only?

The documentation says to use “- in the filter box. I’ve tried that literally (with the quotes) and just by typing in the checkbox. In either case both checked and unchecked boxes show up.

Thanks!

Oh, and Discourse changed the [ and ] brackets to a checkbox, but in Joplin I’m using the square brackets.

Seems like I need to improve the documentation here a little.

Try the following: Right-click on the title of a note on the plugin's panel, and select "Split by item".

I'll try to explain what you've been seeing: When filtering results (just like you have), sections within notes are either displayed or hidden. What is "a section"? They are seperated on the panel by dividers. By default, all the found lines under the same heading constitute a section. In this setting, any section with an open task will be shown, and only sections with no open tasks at all will be hidden. When you change the definition of "a section" to be an individual item, tasks are filtered individually.

group by heading filter (default)

split by item filter

UPDATE: Improved the documentation here and here.

I’ve carefully gone through all the settings, but can’t find what I’m looking for.

Is there a setting that will prevent the search from repopulating with the contents of a note containing a saved search?

The use case is that if you make adjustments to a search, and then go back to the original note to save it, your adjustments are overwritten.

Thanks!

I undrstand your use case @MarkS. There is currently no way to skip loading a saved query, but it might be a good idea to add a setting to optionally turn it off (then users can decide to load them manually with the load command).

As a workaround, you can save the query in whatever note is currently open, then cut and paste it into the destination note.