Interesting…Python on this system is not in /Library/Frameworks.
The system version (3.9.6) is in /usr/bin. I also have a Homebrew-installed version (3.13.0) in /usr/local/bin. I tried creating a symlink to /usr/local/bin/python, but it didn’t help.
I also tried changing the #! line in the script, but that didn’t work either.
I don’t know Python, but I did add some code to the script to create a temp file and write a copy of the output to it. It didn’t create the file. This is inconclusive, though, because I may just have messed it up out of ignorance. There is, though, a growing suspicion that this script isn’t being run at all.
@ttscoff: I see over in the Marked support forum, you wrote that you are redoing CriticMarkup in Ruby. Is that happening? If so, I can wait.
Oh my gosh. I just dug into the code and realized I did already replace the python script with a ruby script. It’s located in ruby/markedcritic.rb. If you’re doing any command line testing, that’s the file to test. I’m so sorry, I must have done that a while back and totally forgotten about it. Ruby is still installed in macOS, so the whole installing Python and linking it step is pointless now.
Which means the issue very likely is Javascript, not the processor script.
Just to check, Marked looks for Ruby in /System/Library/Frameworks/Ruby.framework/Versions/Current/usr/bin/ruby, and if it doesn’t find it there, it looks for /Library/Frameworks/Ruby.framework/Versions/Current/usr/bin/ruby. If neither of those exist, it should be producing an error dialog, so I don’t think that’s the issue. The fact that it gets any output at all indicates the script is running.
Nothing in the Javascript appears to remove DOM content at any point, it just changes the class name of the body to show or hide various elements based on their class. I don’t think JS is the issue here either.
I hate to tell you this, but if you mean /Applications/Marked 2.app/Contents/Resources/ruby/markedcritic.rb, then it isn’t there. Perhaps you’re looking at your development version?
However, what you tell me about where you’re looking for the language support probably gives us the answer to the whole problem. That isn’t where python or ruby lives on this system. The system versions are in /usr/bin. I assume that changed in the later OS releases.
I don’t know how you’re invoking the script, but /usr/bin/env ruby works on command line or #! to pick up the preferred ruby.
You have a serious problem, though. I understand that Apple are phasing out support for these languages, so anybody who needs them will have installed them via XCode or Homebrew, so in /usr/local/bin, but anyone who isn’t a developer won’t have them at all. Textmate gets round this by bundling a Ruby interpreter in the app (1.8.7!), but that’s going a bit far isn’t it?