Linked file not previously opened by Marked2 won't open
// Please enter a detailed description of the issue // Description of the issue: Linked file not previously opened by Marked2 won't open
// Please enter a list of steps required to reproduce the issue // Steps to reproduce:
- Create a file (let's call it foo.md) with a link to another file (e.g. bar in your favorite text editor
- Create file bar.md in same text editor
- Open foo.md with Marked2 and click on the link for bar.md. You might get the dialog asking how you want to handle the file. If you select default app (assuming that's your text editor) or open in new window, nothing will happen.
- Open bar.md in Marked2 and close it. Repeat step 3 and the file will now open in your selection.
I find it hard to believe that I've stumbled onto something new. I found this (http://support.markedapp.com/discussions/problems/197-using-file-li...) discussion about adding the "file:///" and the dialog is working, but it doesn't do anything with a file that Marked2 hasn't opened previously. There's also stuff from 2012.
The fact that you've kept this code running for all these years is greatly appreciated!
// If applicable please attach a sample document that causes the issue for you.
// Configuration (do not edit) Marked 2 1007 (Mac App Store)
macOS Version: 10.15.7
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml, mmd
|?||Show this help|
|ESC||Blurs the current field|
|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 22 Oct, 2020 11:42 AM
Are foo and bar in the same folder?
2 Posted by Todd Vanyo on 22 Oct, 2020 12:46 PM
Support Staff 3 Posted by Brett on 22 Oct, 2020 01:10 PM
That’s very odd. I’ll have to do some testing on my end.
Support Staff 4 Posted by Brett on 22 Oct, 2020 02:44 PM
Looks like this must have something to do with sandboxing, as I can
replicate it with the MAS version but not with the direct version (which
isn't sandboxed). All of the calls appear to be correct, but NSWorkspace
is just failing to respond to the request. This will take some digging,
but with the impending release of Big Sur and some major bugs it's going
to cause, it won't be high on my immediate todo list.
If you'd like to transfer your license to the direct version and avoid
the problem in the meantime, just let me know.
5 Posted by Todd Vanyo on 22 Oct, 2020 03:53 PM
I can live with it for now.