Plugin: Inline Tag Navigator [v2.6.2, 2025-10-09]

Plugins
81

Hello,
While testing the data import from the Obsidian application, I noticed a probably small regression error.
All inline tags were correctly recognized and are visible in the plugin.
The "Converts note's inline tags to Joplin tags" option works correctly.
The inline tags of the note are converted to Joplin tags

Unfortunately, using the "Converts all note's inline tags to Joplin tags" option does not work correctly.
After selecting this option, a pop-up window appears asking you to confirm the action.
After confirming, the window closes and you can't see anything more happening.
The notes are not filled with Joplin tags.

82

Welcome @darkph! Thanks for reporting, I think that I got the regression fixed now, and it will be included in the next release.

83

v2.3.0

  • new: release notes dialog
  • improved: tag parsing regex to support multilingual tag names (for @4SM)
    • if you are using a custom regex, consider updating it based on the README
  • improved: support filtering results with regex in note views (when setting is enabled)
  • fixed: regression: convert all notes to joplin tags
  • fixed: removed extra slash from notebook path
  • fixed: escape regex characters in note view highlights
  • fixed: escape regex characters in table processing
1 Like
84

Thanks a lot !
It solved my problem.

85

Thanks!

86

Hi there.

Is there a way to import the (default) note tags into the addon?
atm I do not see this as any sort of option.

cheers
B

87

Welcome @Barobrand!

Joplin's default note tags can be converted to inline tags in order to use them in the plugin. See the instructions here.

88

v2.4.0

this release improves the navigation and display of search results.

  • added: 'Search: Result grouping' setting, which determines how results are split into sections: group by heading (default); group consecutive lines (legacy behaviour); split at each item / paragraph. grouping affects the behaviour of search filters
  • added: separate settings 'Note view: Highlight filter results' and 'Search: Highlight filter / tag results'
  • added: 'Search: Wait for note period (ms)' setting, that you may decrease to scroll faster to note lines
  • added: quick link (arrow) to the first result in each note
  • added: 'Note view: Display colors' setting, to use color tags for titles in note view
  • improved: a click on any line in the result list scrolls to that line in the note
  • improved: expanded/collapsed state preserved on mobile
  • improved: on mobile, dismiss the plugin panel when opening a note
  • improved: tag ranges logic
  • improved: render soft line breaks as hard line breaks
  • improved: update the note view when saving a query
  • improved: open external links, and links to note headings
  • improved: support wikilinks to zettel IDs or first word in title
  • fixed: tag parsing in the beginning of a line
89

Hello! Firstly, thanks to @shikuz for the wonderful plug-in.
Unfortunately, I can't get coloured and modifiable (via the contextual menu) [x]it! to-dos in the search panel on my macOS machines. I have them working under Windows with exactly the same settings.
See the example below.

Example: on the left the markdown editor, on the right the tag search panel
Example: on the left the markdown editor, on the right the tag search panel2534×198 10.2 KB

However, I have coloured and editable [x]it! todos if I put a todo in the first line and then I indent the following todo.
![Example: on the left the markdown editor, on the right the tag search panel

Interestingly, indenting the next todo brings up some HTML code:
![Example: on the left the markdown editor, on the right the tag search panel

I have then to indent every second todo to get the proper box:
![Example: on the left the markdown editor, on the right the tag search panel

As I said, it works perfectly under Windows.

Any clues?

Thanks in advance

Francesco

90

Thanks @franz-sp!

Please try disabling the setting Search: Highlight filter / tag results.

91

Thanks! Now it works as intended!

1 Like
92

v2.5.0

this release focuses on enhanced task management.

  • added: kanban view for all tasks in the search results based on checkbox state
  • added: sort by tags now works across all note views and the panel display, with an interactive sort dialog
  • added: repeating customisable date tags #week and #month for recurring scheduling
  • added: command to replace relative dates with absolute dates in current / selected line. #today -> #2025-06-22
  • added: syntax highlighting for code blocks and frontmatter in the panel
  • added: setting: 'Tag conversion tracking' to maintain consistency between Joplin tags and inline tags during conversions
  • added: settings to control which toolbar commands are visible
  • improved: saved queries are hidden in the markdown preview
  • improved: result grouping can be defined in queries and selected in the panel context menu (click on note titles)
  • improved: panel state preservation
  • improved: memory management and security
  • fixed: legacy checkbox interaction behavior
2 Likes
93

v2.5.1

  • fixed: regression: open links with >50 chars URLs
  • improved: convert joplin tags to inline tags skips existing inline tags in body (following this post)
  • improved: settings labels

[EDIT: added the following minor releases]

v2.5.2

  • fixed: regex safety check (#19)

v2.5.3

  • added: setting: middle matter support (#20)

v2.5.4

  • fixed: hide query but not the following text (#21)

v2.5.5

  • fixed: improve JSON query loading with enhanced format handling
  • fixed: apply sorting after note edits

v2.5.6

  • fixed: ensure that date tags are evaluated at least at daily frequency
  • fixed: reset regex state during front matter tag parsing
  • fixed: skip front matter blocks during inline tag parsing
  • improved: use the keywords front matter field for inline tags
94

Hi @shikuz , thank you for your plugin!
I recently discovered it and decided to replace the Inline TODO plugin with it, since your plugin allows for more flexible information retrieval. For example, now I can find all tasks assigned to an @EmployeeA even if they're not the first mentioned in the line and there's another @EmployeeB before them.

Could you please help me figure out what I'm doing wrong with the tag highlighting setup?

When I use:

Rich Markdown: [{ "name": "rm-tag", "regex": "(?<=^|\s)([#@+]|\/\/)([^\s#@+]*\w)" }]

Custom stylesheet:

```
div.CodeMirror .cm-rm-tag {
background-color: #7698b3;
color: white !important;
padding: 0em 2px;
border-radius: 5px;
display: inline;
}
```

I don't get any highlights.

However, if I change it to: [{ "name": "searchMatch", "regex": "(?<=^|\s)([#@+]|\/\/)([^\s#@+]*\w)" }]

Then the highlights appear.

The behavior is the same on both Desktop and Mobile (Rich Markdown Mobile Fork).

Do you know why "rm-tag" isn't being applied?

And one more thing, could you please help me set up Rich Markdown and CSS so that tags have different colors:
Green: +greentag
Blue: @bluetag
Gray: //graytag

I doubt it's possible to configure colors for //dates based on whether they're greater or less than the Current Date, so let them just be gray.

1 Like
95

Which custom stylesheet did you edit? Please check that it’s “Custom stylesheet for Joplin-wide app styles” (userchrome.css).

On the mobile fork, make sure that you activate the “Stylish” theme in Rich Markdown.

Try to separate to 4 regex / classes (in Rich Markdown):

[
  {
    "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#@+'\",.()\\[\\]:;\\?\\\\]+)"
  }
]

And in the userchrome.css: (Adjust the colours to your liking)

div.CodeMirror .cm-rm-tag-hash {
    background-color: #7698b3;
    color: white !important;
    padding: 0em 2px;
    border-radius: 5px;
    display: inline;
}

div.CodeMirror .cm-rm-tag-plus {
    background-color: darkgreen;
    color: white !important;
    padding: 0em 2px;
    border-radius: 5px;
    display: inline;
}

div.CodeMirror .cm-rm-tag-at {
    background-color: darkslateblue;
    color: white !important;
    padding: 0em 2px;
    border-radius: 5px;
    display: inline;
}

div.CodeMirror .cm-rm-tag-slash {
    background-color: darkgray;
    color: white !important;
    padding: 0em 2px;
    border-radius: 5px;
    display: inline;
}
1 Like
96

Great, that's exactly what I needed!

The format wasn't displaying for me because I hadn't selected "Stylish" in Rich Markdown. I had it set to "none".

Choosing "Stylish" changed everything, both on Mobile and Desktop.

The hash/plus/at/slash styles also worked.

Huge thanks! The plugin is simply wonderful.

1 Like
97

@shikuz My Rich Markdown plugin on mobile wants to update from 0.15 to 0.16. Will it replace it with the non-mobile version?

98

Yes, it will replace it with the non-mobile version. I’ll update the mobile version at some point, but I believe that the updates are minimal at this point.

99

Can I use 'Navigation panel: Toggle' Shortcut key？Thanks.

100

Comment of praise: I’ve discovered this plugin recently at it looks exactly what I was looking for.

I recently changed my organization from lots of small notes to just a few more monolithic notes. I was not fond of this in the beginning but my knowledge based got so fragmented by the former approach that I was following levels and levels of breadcrumbs to find what I needed.

With this new approach, however, suddenly my tags became kind of useless because I had many topics into one note, and since notes were long I could not easily find what part was related to which tag. This plugin solves this.

Some time ago I took a look into Logseq, which as far as I understand implements the approach of the atomic unit of information is a bullet point. I like this idea, but I could not adapt well to Logseq (Joplin is still better for my workflow).

I was missing this one feature from Logseq, but this plugin fills that need perfectly from what I see.

Kudos for the awesome plugin @shikuz

:tada:

Edit: grammar

1 Like