This would be even better =)
What would be even better ?
Mhm, I understood your statement as a plan to allow {== and == as syntax for highlighting. At the moment only text in {== will be show highlighted. But as many other applications uses == this would be great to allow both.
DEVONthink 3 supports both CriticMarkup and alternate syntaxes like ==...==
. Tools > Summarize Highlights > Markdown retains the used syntax.
Oh my… you are right. Don’t know why I thought == won’t work and did not tested it before. My bad.
Besides I’m a bit sad about your decision about the syntax of the summarized highlights. I think visual highlights are only necessary if there is a need to emphasize some words between other text. But the exported .md-file with the PDF highlights only contains those highlights and therefore has no need for visual emphasizing.
if it bothers you, you could turn it off with a simple style sheet.
But that would disable all highlights with {==. I think I’ll try those scripts first.
And it’s amazing. Thank you
I adjusted the regex a bit to:
(() => {
const app = Application("DEVONthink 3");
const recs = app.selectedRecords();
recs.forEach(r => {
const text = r.plainText();
const newText = text.replaceAll(/\*\s\{==(.*?)==\}/g, "> $1");
r.plainText = newText;
})
})()
And it is working great
Only if you were using a global stylesheet. Which you do not have to.
The next release will add a new preference.
Wow, this is great. Thanks
New feature is great Thanks