Non-normalized data is more robust even when it takes up additional space and offends the de-duplication gods. Kinda goes along with Markdown’s brute force, show-me-everything approach.
2 Likes
A format standard for shared blocks would be interesting. Using a mixture of block IDs and content duplication in export seems best in the meantime.
How did you get % and ? to underline like that?
Thanks,
Mark
1 Like
Somehow just seeing this. Sorry! In case it helps anyone, this is what I have in one of my themes, for indicating a new speaker in my notes by starting a line with % (and resulting in blue text for that line):
"person-line-indicator": {
"regex": "^(%{1,2})(?:\\s+)(\\S.*)\\n((?:\\s+\\S.*\\n)*)",
"matchPosition": 1,
"isMarkdownCharacter": true,
"isHiddenWithoutCursor": false,
"isRevealOnCursorRange": false,
"color": "#b6bdfa"
},
"person-line-person": {
"regex": "^(%{1,2})(?:\\s+)(\\S.*)\\n((?:\\s+\\S.*\\n)*)",
"matchPosition": 2,
"isMarkdownCharacter": false,
"isHiddenWithoutCursor": false,
"isRevealOnCursorRange": false,
"color": "#1062e6"
},
"person-line-addenda": {
"regex": "^(%{1,2})(?:\\s+)(\\S.*)\\n((?:\\s+\\S.*\\n)*)",
"matchPosition": 3,
"isMarkdownCharacter": false,
"isHiddenWithoutCursor": false,
"isRevealOnCursorRange": false,
"color": "#4d57e8"
},
The third part (“person-line-addenda”) is supposed to style anything on the line following one beginning with %, but I don’t think it works. I’ve never had much success with multiline styling in NotePlan. Luckily it isn’t a huge problem for me.
1 Like
I solved the issue of NotePlan burying its notes folder deep in the filesystem by using Finder to put an alias to that folder where I want my notes folder to be.
1 Like
Ah, a smart solution to one of the reasons I don’t use Noteplan. (The other big one being the way filenames behave by default, which I dearly wish the developer would change.)