CriticMarkup not rendered
Using Marked 2 v2.6.25. Markdown documents with CriticMarkup is rendered empty.
Example:
This is a {>>test<<} md document with a comment.
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 22 Sep, 2023 12:30 PM
You need to install the Command Line Tools.
https://www.freecodecamp.org/news/install-xcode-command-line-tools/
Thanks,
Brett
On 22 Sep 2023, at 5:03, Dean wrote:
2 Posted by Dean on 22 Sep, 2023 08:41 PM
Actually, Command Line Tools already is installed.
macOS Ventura 13.6 (22G120)
It's also already updated.
Support Staff 3 Posted by Brett on 22 Sep, 2023 09:44 PM
If you open Terminal and run:
which python
What does it return?
Thanks,
Brett
On 22 Sep 2023, at 15:41, Dean wrote:
4 Posted by Dean on 24 Sep, 2023 04:44 PM
Nothing.
Btw. the system Python is
/usr/bin/python3
There's no /usr/bin/python nor python2 installed.
I created a symlink named
pythonpointing to python3, nothing changed in Marked 2.Support Staff 5 Posted by Brett on 25 Sep, 2023 01:30 PM
Marked should recognize the /usr/bin/python3 binary. This is odd. Could
you please send me the output of Help->Report an Issue?
-Brett
On 24 Sep 2023, at 11:43, Dean wrote:
Support Staff 6 Posted by Brett on 25 Sep, 2023 01:30 PM
Also attach a sample file containing CriticMarkup that demonstrates the
issue for you, please.
On 24 Sep 2023, at 11:43, Dean wrote:
7 Posted by Dean on 25 Sep, 2023 04:31 PM
Alright!
See below.
Attached.
Dean
// Please enter a detailed description of the issue // Description of the issue:
As reported at http://support.markedapp.com/discussions/problems/175103-criticmark... ,
Markdown documents with CriticMarkup is rendered empty. (Using Marked 2 v2.6.25., with the latest XCode (Version 14.3.1 (14E300c)) and Command Line Tools installed.)
/usr/bin/python3 is there (version 3.9.6) and /usr/bin is in $PATH.
which python3points at /usr/bin/python3.which pythonreturns nothing.// Please enter a list of steps required to reproduce the issue // Steps to reproduce:
// If applicable please attach a sample document that causes the issue for you.
This is a {>>test<<} md document with a comment.
// Configuration (do not edit) Marked 2 1046 (Mac App Store)
macOS Version: 13.6
additionalMathJaxConfig:
allowPageBreakInCode: YES
bookTxtIsLeanpub: NO
summaryMdIsGitBook: NO
codeIsPoetry: NO
codeCanWrap: YES
collapsibleHeadlines: NO
convertGithubCheckboxes: YES
convertGithubEmoji: YES
convertYAMLToMMD: NO
defaultMathJaxConfig: TeX-AMS-MML_HTMLorMML
defaultPreviewStyle: swiss
defaultProcessor: MultiMarkdown
enableMiniMap: NO
excludeBlockQuotesFromCounts: NO
excludeFootnotesFromCounts: NO
excludeVerbatimFromCounts: NO
excludeCaptionsFromCounts: NO
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml
githubNewlines: YES
h1IsPageBreak: NO
h2IsPageBreak: NO
hrIsPageBreak: NO
includeMathJax: YES
includeKatex: NO
limitTextWidth: NO
mathNumberEquations: NO
mathNumberEquationsSide: 0
mathNumberEquationsAMSOnly: NO
minimalJavaScript: NO
outlineModeExtensions:
permissionGranted: NO
printHeaderBottomLeft:
printHeaderBottomRight:
printHeaderFirstPage: NO
printFooterFirstPage: NO
printHeaderTopLeft:
printHeaderTopRight:
processHTMLFiles: YES
removeMetadataForPreview: NO
removeYAMLHeaders: NO
scrollToEdit: YES
shouldDetectCritic: YES
shouldHighlightMarkupErrors: NO
shouldLoadCritic: NO
syntaxHighlight: NO
syntaxHighlightOnlyLang: NO
useCustomMarkdownProcessor: NO
customMarkdownProcessor:
useCustomPreprocessor: NO
customPreprocessor:
useFirstH1AsPrintTitle: YES
Support Staff 8 Posted by Brett on 25 Sep, 2023 05:19 PM
Could you go to Preferences->Advanced and set debug mode at the bottom
to "All" then open the debug log from Help->Open Debug Log and see if
there are any messages when loading your criticmarkup test?
Your test file loads fine for me and I get the tabbed Critic interface,
so I need to figure out where the script is failing.
Thanks,
Brett
On 25 Sep 2023, at 11:30, Dean wrote:
9 Posted by Dean on 25 Sep, 2023 05:49 PM
See the attached file.
Support Staff 10 Posted by Brett on 25 Sep, 2023 06:05 PM
Ok, that gives me a little to go on. I’ll need to do some debugging and may need you to run a test build of the app for more info. Will try to get this sorted this week.
Thanks,
Brett
On Sep 25, 2023 at 12:49 PM -0500, Dean <[email blocked]>, wrote:
11 Posted by Dean on 21 Oct, 2023 11:55 PM
Any update?
Support Staff 12 Posted by Brett on 24 Oct, 2023 02:42 PM
Not yet. Just got through some Sonoma madness and things seem to have settled down, so I can take a closer look at this this week. For some reason the CriticMarkup processor is returning an empty result. Could you try this in Terminal?
Replacing TEST_MARKDOWN.md with a path to a Markdown file containing CriticMarkup. Just curious if the error is happening at the script level or not.
(Depending on which version of Marked you have installed, the path to markedcritic.py may change. For Setapp it will be
/Applications/Setapp/Marked.app/...Support Staff 13 Posted by Brett on 02 Nov, 2023 03:34 PM
I have someone on my forum reporting the same thing and gave him a test build to try out. Have you had a chance to run that command line test yet?
Support Staff 14 Posted by Brett on 06 Nov, 2023 08:10 PM
I just published v2.6.31. When it's avaialable on your update channel
(Should be ready now for Paddle customers, in review for MAS and
Setapp), let me know if it solves the issue for you.
Thanks,
Brett
On 21 Oct 2023, at 18:55, Dean wrote:
15 Posted by Dean on 08 Nov, 2023 08:04 AM
Unfortunately, it didn't work.
(I appreciate your help, Brett. Thanks for your hard work!)
Apparently the script is fine:
which python3returns/usr/bin/python.There's an additional complication due to a macOS Sonoma bug, but it's such a mess I'll first check what's going on in my machine. I'll come back. Please wait...
Support Staff 16 Posted by Brett on 08 Nov, 2023 12:59 PM
you created that /usr/bin/python as a symlink, didn't you? What was the original location of python3?
17 Posted by Dean on 09 Nov, 2023 07:33 AM
Actually, no. It's done by Apple. I.e.
/usr/bin/python3is the Python installed by Apple (The official Python doc confirms this: https://docs.python.org/3/using/mac.html).
It's also not a symlink.
Another thing to note is that there's no
/usr/bin/python(i.e. without the suffix3). This is a bug in XCode as discussed here:https://developer.apple.com/forums/thread/704099?page=2
People in the forum fixed the problem by running some XCode command. Sadly, it doesn't work for me.
I'm running out of ideas on how I could fix this on my side.
Can you somehow allow
/usr/bin/python3or/opt/bin/local/python3as the python to be used? The latter is actually a symlink created by MacPorts. Another idea is to find the user-setpython3from the PATH environment variable, or just let the user specify a custom path to python.Support Staff 18 Posted by Brett on 09 Nov, 2023 12:38 PM
Marked does look for /usr/bin/python3. In your last email you said
`which python` revealed /usr/bin/python. Was that a mistake?
On 9 Nov 2023, at 1:33, Dean wrote:
19 Posted by Dean on 10 Nov, 2023 12:43 AM
Yes, this one is a mistake. It's
/usr/bin/python3. Apologies.Support Staff 20 Posted by Brett on 10 Nov, 2023 02:48 PM
I'm running out of things to try. Marked definitely looks for /usr/bin/python3 after checking for /opt/homebrew/bin/python and the older Framework installation (which doesn't exist on Sonoma). And the script is working from the command line…
Adding /opt/homebrew/bin to Marked's checks fixed this issue for the user on the forum, so I still believe something is amiss with Python in your case, but I can't figure out what or why your install would be any different. I'll try to put together a build with some more verbose logging to see if we can figure out where it's going wrong.
21 Posted by Dean on 11 Nov, 2023 01:22 AM
Thank you.
I will wait for your build with the log.
Meanwhile...
This is not relevant to me since I don't have homebrew installed.
A possibility is that pre-installed packages for /usr/bin/python3 of Sonoma might be conflicting with something used by Marked 2.
Here's the list of pre-installed packages given by /usr/bin/pip3:
~~~
Here's everything in the site-package directory (My /usr/bin/python3 has only one site-package directory):
~~~