tag:support.markedapp.com,2011-09-11:/discussions/questions/6417-back-buttonopen-preferenceMarked: Discussion 2014-08-05T17:20:33Ztag:support.markedapp.com,2011-09-11:Comment/340301642014-08-05T17:01:12Z2014-08-05T17:01:12ZBack Button/Open Preference<div><p>There's a reset alerts button in General preferences that will
prompt<br>
you again next time. If you don't check the "Remember this
choice"<br>
button, it will ask you every time.</p>
<p>Marked is not intended to be a browser, which is why I've
left<br>
navigation features out of it. It also isn't built to be a web
browser,<br>
as every page is read, processed and then the HTML is loaded
from<br>
memory, not read from the disk. A back button would just be a
synthetic<br>
file representation. You can always add back links to your
sub-pages,<br>
but I don't think document navigation in general is in my
long-term<br>
plan.</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/340301642014-08-05T17:20:32Z2014-08-05T17:20:32ZBack Button/Open Preference<div><p>Thanks for the quick reply!</p>
<p>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!</p>
<p>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...</p>
<p>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.</p>
<p>Thanks for the great product, and quick answer!</p>
<p>Nathan</p></div>nathan