Marked not updating on saves.
Just got Marked.
It's not updating on saves - I have to manualy refresh it to see changes.
I've tried text editing with Textmate, Textmate 2, and
cat. I've opened the files both by dragging files into
Marked, and by doing File > Open.
OS X 10.7.1
How should I go about debugging this? Is there some obvious setting I am missing?
Comments are currently closed for this discussion. You can start a new one.
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 04 Jan, 2012 05:30 PM
Do you have Spotlight enabled? It's not strictly necessary on Lion anymore (assuming you have Marked 1.3.2 or higher), but may affect the systems ability to detect changes.
If that's not the issue, open Console.app and use the search field to filter for "marky". Then open a file and see if any telling error messages come up. Unless there's an error, though, the issue is likely with your filesystem. Let me know about these two things and I'll see if we can determine a more specific cause.
Thanks,
Brett
2 Posted by Daniel Von Fang... on 04 Jan, 2012 06:28 PM
I'm running Marked Version 1.3.2 (190)
Spotlight is enabled on the drive, and I can search for the contents of and find the markdown documents I'm editing.
[op ~]$ mdutil -s /Volumes/Macintosh\ HD
/:
Indexing enabled.
Nothing in the console on a search for "marky". Searching for "marked" gets me just:
1/4/12 6:27:02.624 AM installd: Installed "Marked" ()
Support Staff 3 Posted by Brett on 06 Jan, 2012 04:31 PM
I don't have a means of testing on 10.7.1. I have no idea if that has anything to do with it anyway. I'm in Vegas for a week and away from my build machine, but will try to get you a debug version as soon as possible.
In the meantime, run
defaults write com.brettterpstra.marky debugMode 1in Terminal and then check your console again and copy me a chunk of output you get on initial load and after a file save (if anything happens at all).4 Posted by Daniel Von Fang... on 06 Jan, 2012 06:26 PM
Well, I probably ruined a good debugging opportunity, but I just upgraded this morning to 1.7.2 and the problem went away.
Works fine now.
Have a good trip!
Support Staff 5 Posted by Brett on 13 Jan, 2012 04:33 PM
Glad to hear it's working for you, thanks for the update!
Brett closed this discussion on 13 Jan, 2012 04:33 PM.