Above I suggested this following syntax in response to @AutonomyGaps cool idea about a feature using double bracket syntax within a highlight range to define what the note title should be for that highlight:
==One of the big advantages of the ====Extract Highlights plugin for Obsidian==== is the it can be used to set up MOCs quickly==
I may again be wrong, but I believe I failed to realize that following default Markdown, Obsidian would think the last two equals signs out of the first set of four consecutive equals signs were the end of that first highlight range. I mistakenly assumed that Obsidian immediately ended a highlight range as soon as two consecutive equals signs occur.
Instead it could look like this:
==One of the big advantages of the== ==Extract Highlights plugin for Obsidian== ==is the it can be used to set up MOCs quickly==
I still wanted to leave the initial top syntax suggestion in my original post rather than editing it because some people may still actually like that more. And since this is a plugin, I guess it doesn’t really matter what Obsidian would think without the plugin. But actually it kind of does in the sense that I suggested that particular syntax thinking that in a scenario where you no longer had the Extract Highlight plugin, at least the proper range would be highlighted, albeit in three ranges rather than one. Of course, that is also true for @AutonomyGaps suggestion, but I digress. At this point, I am pretty much sold on the bracket version assuming there wouldn’t be any weird issues that arise when you inevitably highlight something with an uncreated link in it but do not want to to have that name as your extracted highlight note title. But I am sure if @akaalias and others liked the bracket version, he could cook up a nifty way that this would be a non issue.
I didn’t mean to get so involved with this post but once I realized my mistake I didn’t feel good leaving the post up, but then saw it had a vote or two and consequently felt wrong deleting or editing it.
In conclusion, I love these plugins and especially appreciate the group effort at brainstorming the bells and whistles.
Thanks so much!