edit marker
I have the show edit marker checked in Preferences > Preview but do not see the little red bar indicating changes any more. I am not sure what I changed to trigger this. Perhaps my switching to the new OS 10.10.3 (14D127a)? --gildas
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Brett on 01 Apr, 2015 06:05 PM
Is Marked scrolling to your changes and just not showing the marker, or
not scrolling at all?
2 Posted by gweltaz on 01 Apr, 2015 06:19 PM
It doesn't scroll at all, actually.
Support Staff 3 Posted by Brett on 01 Apr, 2015 06:29 PM
That indicates that the JavaScript isn't loading at all, which can be
caused when upgrading from older versions of Marked 2 direct purchase to
newer versions that don't use the sandbox. The fastest solution is to
delete the preferences in both the sandbox and outside of it and reboot.
Assuming you're not using the MAS version (please let me know if you
are):
1. Quit Marked 2.
2. The sandbox preferences are located at
~/Library/Containers/com.brettterpstra.marked2. You can delete that
entire folder.
3. The newer preferences are located in the file at
~/Library/Preferences/com.brettterpstra.marked2.plist.
4. After emptying the trash, reboot and launch Marked 2 again.
Sorry about the inconvenience. Marked tries to port the old preferences
to the new location after the first upgrade to the newer location, but
in some cases it seems to fail.
-Brett
4 Posted by gweltaz on 01 Apr, 2015 06:47 PM
Thank you for the super-rapid reply. I followed the steps above and everything works like before, including using my own css. I had previously junked the preference file in ~/Library/Preferences but not realized there was also a ~/Library/Containers/com.brettterpstra.marked2 folder. Thanks again.
5 Posted by gweltaz on 03 Apr, 2015 01:39 AM
I tested further and found out the cause of the failure of edit marker + scrolling seems to be a piece of my custom processor.
In Preferences > Advanced > Custom Processor, I'm using pandoc (Path: /usr/local/bin/pandoc), and as Arguments:
-r markdown -w html -s --filter pandoc-citeproc
That works: scrolling and edit marker work as expected.
If I add to the args the unmodified pandoc html template ( --template=/Users/gweltaz/.pandoc/templates/template.html), edit marker and scrolling fail.
So, I stopped using that pandoc template.html. The only problem---a very small one---is that the "Author: Gildas H." in my metadata now appears as a section title (<h2> level), while the title in the metadata shows correctly as a chapter header (<h1>).
Any suggestions about either the pandoc template.html or my Arguments line? I looked at the template but couldn't see what I should change if anything.
--Gildas
Support Staff 6 Posted by Brett on 03 Apr, 2015 02:24 AM
All of Marked's preview features depend on it having control of the
containing HTML, so if your template is returning a complete HTML
document, it's inserting that into Marked's existing DOM and breaking it
with illegal nesting of <html> tags.
Can you show me the markup for your metadata and start of the doc? Is it
possible that Pandoc is creating the h2?
-Brett
7 Posted by gweltaz on 03 Apr, 2015 03:03 AM
I looked again at the local ~/.pandoc/templates/template.html and noticed a js script in it:
<!--[if lt IE 9]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
I removed the script from the template, because of what you said in msg 3 above re. java not loading, re-inserted the call to the .pandoc/templates/template.html and lo and behold, it works. That is, formatting of the html is what I want, and scrolling + edit marker function correctly.
So, I'm happy with the solution I hit upon by trial and error (I'm no programmer!).
--gildas
Support Staff 8 Posted by Brett on 03 Apr, 2015 03:04 AM
Cool. WebKit should be able to parse around the nested DOM under normal
circumstances, but the shim would probably force it to fail. Good call.
-Brett