Updating QLMarkdown to use new repo

[joeyhoer]

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

After making all changes to a cask, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask {{cask_file}} is error-free.
• brew style --fix {{cask_file}} reports no offenses.

---

According to this thread, development on the original QLMarkdown has been abandoned and development has been moved to a new maintainer.

[vitorgalvao]

From the documentation on forks:

Forks must have the vendor’s name as a prefix on the Cask’s file name and token. If the original software is discontinued, forks still need to follow this rule so as to not be surprising to the user. There are two exceptions which allow the fork to replace the main cask:

• The original discontinued software recommends that fork.
• The fork is so overwhelmingly popular that it surpasses the original and is now the de facto project when people think of the name.

None of those is true. The submitted fork is so unpopular it doesn’t even pass the notability threshold to be included in the main repos.