For example, the settings could be stored in a .dynamic-highlights-settings file in a folder so that those setting apply for all files in the folder.
And in addition: a yml property dynamic-highlights-setting-location provides the path to a settings file.
Or have the plugin setting page allow you to set up an association between the value of another yml property on a file and a dynamic highlights settings file.
A use case: I have "condensed notes" where I try to avoid using "a", "an", "the", "we", "is", "be", "are", "when" for brevity (and have highlights for these words), but obviously I have other notes where these highlights don't make sense.
Different files require different highlights.
For example, the settings could be stored in a .dynamic-highlights-settings file in a folder so that those setting apply for all files in the folder.
And in addition: a yml property
dynamic-highlights-setting-locationprovides the path to a settings file.Or have the plugin setting page allow you to set up an association between the value of another yml property on a file and a dynamic highlights settings file.
A use case: I have "condensed notes" where I try to avoid using "a", "an", "the", "we", "is", "be", "are", "when" for brevity (and have highlights for these words), but obviously I have other notes where these highlights don't make sense.
This FR would also cover the requests in #24 .