Hi,
Apologies if this has already be raised, but a couple of updates ago I noticed this strange behavoir where full directory paths get managled in the Marked preview but appear Ok in Dingus.
Example md:
Shared lifecycle lock:
```text
/run/lock/zabbix-backup.lock
Marked preview:
Shared lifecycle lock:
<<[][run/lock/zabbix-backup.lock]
It happens with all processors. The markdown also previews OK in Zed and in Marked Quick Look.
A line starting with a slash and followed by a path is assumed to be an iA Writer file include and is translated to Marked's include syntax. This would happen anywhere you included a line like that.
It's never come up as an issue before, so I've never added a way to turn this off, but I can.
Thanks for the quick response Brett. That does make sense and in a small test file I can see it happening where all lines starting with /directory/subdir... after ```text are translated to iA Writer inserts.
I'm still a little wary as the file in which I originally noticed it had many such sections and only 1 or 2 were affected. I did checks for non-visible characters, etc., but couldn't narrow it to anything else. Maybe the parsing was thrown out by some error earlier in the file, so I'm hoping being able to turn off iA Writer as needed will help.
Looking forward to the update! :-)
