You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for the great plugin, it is helping with some planning for a big trip!
This is on Obsidian 1.7.3, flatpak on Linux. Map View is 5.0.3.
While setting it up I did run into an issue with a marker not displaying and realized it is due to the inline tag needing a trailing space or newline before its picked up.
First, no tag, no trailing space or newline
The default marker is shown as expected
Now add an inline tag that has a custom icon, note no space or newline after `tag:Campground'
Default marker is still used
Add a single space (or newline) after the tag and it works
Adding another tag that has its own marker, but without the trailing space
First tag still displayed
And adding a space (or newline as is this case)
Works
I did notice that for a tag already configured with a custom marker that it auto completes and adds a space, so if I type in tag:DontGo then hit enter to choose it from the auto complete drop down then a space is added. But if I type in tag:DontGoHere and then click elsewhere on the note to skip using auto complete then a space isnt (cant be) added and now the marker wont appear.
Similarly if I add a tag that does not have a custom marker configuration then auto complete doesnt apply, so typing tag:New where that tag doesnt have a custom marker config BUT is a previously used tag then auto complete also doesnt kick in and no space is added.
So for the actual request, I am not sure of the best approach but one of these?
Pick up inline tags without a trailing space or newline so they are used properly as markers OR
Any time an inline tag: is populated, add a space at the end automatically with auto complete, even if the tag doesnt have a custom marker config (which seems to be the criteria for auto complete to kick in?)
The first option would also cover off accidentally removing the space while removing an old tag so that might be preferable? Unless the auto complete logic can always apply to ensure there is a space at the end of a tag:.
And again, thank you for the excellent plugin!
The text was updated successfully, but these errors were encountered:
First, thank you for the great plugin, it is helping with some planning for a big trip!
This is on Obsidian 1.7.3, flatpak on Linux. Map View is 5.0.3.
While setting it up I did run into an issue with a marker not displaying and realized it is due to the inline tag needing a trailing space or newline before its picked up.
First, no tag, no trailing space or newline

The default marker is shown as expected

Now add an inline tag that has a custom icon, note no space or newline after `tag:Campground'

Default marker is still used

Add a single space (or newline) after the tag and it works

Adding another tag that has its own marker, but without the trailing space

First tag still displayed

And adding a space (or newline as is this case)

Works

I did notice that for a tag already configured with a custom marker that it auto completes and adds a space, so if I type in
tag:DontGo
then hit enter to choose it from the auto complete drop down then a space is added. But if I type intag:DontGoHere
and then click elsewhere on the note to skip using auto complete then a space isnt (cant be) added and now the marker wont appear.Similarly if I add a tag that does not have a custom marker configuration then auto complete doesnt apply, so typing
tag:New
where that tag doesnt have a custom marker config BUT is a previously used tag then auto complete also doesnt kick in and no space is added.So for the actual request, I am not sure of the best approach but one of these?
Pick up inline tags without a trailing space or newline so they are used properly as markers
OR
Any time an inline
tag:
is populated, add a space at the end automatically with auto complete, even if the tag doesnt have a custom marker config (which seems to be the criteria for auto complete to kick in?)The first option would also cover off accidentally removing the space while removing an old tag so that might be preferable? Unless the auto complete logic can always apply to ensure there is a space at the end of a
tag:
.And again, thank you for the excellent plugin!
The text was updated successfully, but these errors were encountered: