Arch Linux User Repository

Before flagging this package as "out-of-date", please read this:

First of all, I appreciate your help, but I'm already running a script that notifies me once a new version is available. Please wait 1-2 days before flagging, unless it is critical. Usually I manage to push updates on the same day as Typora releases them.

Also: The latest version on their website might not be the latest Linux repository version. E.g. because some updates do not have any changes related to Linux.

To check the latest Linux version, run the following command: curl -s https://www.typora.io/linux/Packages | grep Version | cut -f 2 -d ' ' | sort -V | cut -f 1 -d '-' | uniq

Please do not flag this package as "out-of-date" if the "new version" is not listed in the output of the aforementioned command.

Typora is no longer completely free since it's out of beta. It is possible to use Typora for free on Linux; Some restrictions may apply. See the official FAQ: "Can I use Typora for free?" for more details. Alternatively you can purchase a license.

Please report issues with Typora here: https://github.com/typora/typora-issues

I tried ELECTRON=electron. There is a not-match version warning with first start, just dismiss that, and everything works seamlessly as before.

Is gconf really needed??

If you get the error ERROR: One or more files did not pass the validity check! or curl: (22) The requested URL returned error: 404, it might be that upstream has changed/removed a released package. They have a habit of doing that from time to time. Leave me a comment and I'll update the sum (or version).

You can also try cloning the repo and running make update, which attempts to parse the newest version out of the debian repository index and update the PKGBUILD for you.

New: The PKGBUILD will build with system electron if you set env ELECTRON=electron while building. Please try this out and provide feedback.

Edit: Thanks NicoHood for the PKGBUILD contributions.

Seems that there is a validity check problem.

"ERROR: One or more files did not pass the validity check!"

Typora 0.9.77 uses electron 5.0.4, so I think gconf can be removed from dependencies safely.

And unfortunately electron2 won't work in this case.

Tip: to find out what electron version Typora is using, activate developer tools by pressing Shift + F12 in the main window, switch to 'Console' tab, then type process.versions.electron in the console and press enter.

I suggest adding pandoc as optional dependency, as pandoc can be used for custom exports to other formats such as open office etc. https://support.typora.io/Install-and-Use-Pandoc/

@NicoHood

I don't see any benefit to moving to the tarball. We've already had problems in the past with upstream breaking the package. https://aur.archlinux.org/packages/typora/?O=20&PP=10#comment-624914 They've gotten better, but the tarball will break the package after every release. It looks like someone else wanted to do that too. https://aur.archlinux.org/packages/typora-latest/

We've also tried using system electron before. https://aur.archlinux.org/packages/typora/?O=0&PP=10#comment-669181 I see now that there is now an electron2 package that might work, but it will take some experimentation.

The gconf dependency is based off of what is documented in the Debian package. It may no longer be accurate, but it did depend on it at one time and still shows in the latest debian package. https://aur.archlinux.org/packages/typora/?O=30&PP=10#comment-565571 I'll have to look into the dependencies. I'm not sure about the gtk3 and nss dependencies. https://www.archlinux.org/packages/community/x86_64/electron2/ lists the dependencies for electron2. That might be the best way to go.

I've updated my PKGBUILD again. It now used the archlinux electron. The package size got reduced by 160mb from ~200mb to ~39mb now.