Use inline fields
Another option would be to use a dedicated inline field to catch all your lyric idea. See the following example:
... if I had a lyric idea I could tag the phrase (LyricIdea:: Lorem ipsum), and then keep on talking about something else...
This would then allow for dataview to collect all ideas when you feel like it into a list of idea. Using normal parentheses will hide this field name from the note when previewed or reading mode. And if you’re so inclined you could also style these using CSS.
If styling using CSS, I would recommend switching to [LyricIdea:: Lorem ipsum]
, as it is then easier to target both the field name and/or field value. This would allow you to hide the field name, and still to change the appearance of the field value for your lyric ideas.
Using custom tasks
Yet another option is to use custom tasks, see Alternative Checkboxes (Icon Bullets) - Copy and paste - #10 by holroy, where you could then do something like:
- [L] Lorem ipsum dolor sit amet
And then have a dedicated icon for the lyric ideas. These would stand out a little more in your note, but when queried through some task query you would also get a link directly to where you had that idea. And if you used more letters, maybe lower-case l
, you could use that to signify a lyric idea which you’ve completed or are “done with” somehow.
As indicated in the other thread, these tasks can be styled however you want them styled.
If you want easy linkage between queries and ideas, I’d opt for the latter solution. If you want the ideas to blend in with their original note, but still maintain easy searches for them I would opt for the first idea using inline fields.