Brett on 05 Aug, 2014 05:01 PM
There's a reset alerts button in General preferences that will prompt
you again next time. If you don't check the "Remember this choice"
button, it will ask you every time.
Marked is not intended to be a browser, which is why I've left
navigation features out of it. It also isn't built to be a web browser,
as every page is read, processed and then the HTML is loaded from
memory, not read from the disk. A back button would just be a synthetic
file representation. You can always add back links to your sub-pages,
but I don't think document navigation in general is in my long-term
I think I see good reasons to stay away from navigation; it seems like it would open up a whole new set of problems. I'm in no way complaining; I love the product, and I think it will serve my needs as-is—now that I know how to reset the alerts!
In my mind, the rendering process isn't connected, though. Processing to HTML for every page is exactly what I'm looking for. It means I can edit directly, rather than having to sync things through a static generator like Jekyll/Octopress. I love using "Open in Editor" to pop over to an editor; and that changes are immediately reflected back in Marked. So, I'm not sure what you mean by "synthetic file representation." In my mind, it's just an undo of a navigation action...
My point being, if you wanted to go further down this path, I think it works well! But I also thinks it serves my needs already.