Package Details: zettlr 1.5.0-1

Git Clone URL: https://aur.archlinux.org/zettlr.git (read-only, click to copy)
Package Base: zettlr
Description: A markdown editor for writing academic texts and taking notes
Upstream URL: https://www.zettlr.com
Licenses: GPL
Submitter: BrLi
Maintainer: BrLi
Last Packager: BrLi
Votes: 2
Popularity: 0.26
First Submitted: 2019-06-17 04:47
Last Updated: 2019-12-21 14:10

Dependencies (8)

Required by (0)

Sources (1)

Pinned Comments

kseistrup commented on 2019-09-07 12:49

The note about $NODE_ENV is still valid: If $NODE_ENV is set to production, building the package fails.

Latest Comments

1 2 Next › Last »

kseistrup commented on 2019-12-21 20:57

Same shit, @BrLi: If NODE_ENV is set to production, building the package fails.

But if I

$ env NODE_ENV= makepkg -s

everything's fine.

BrLi commented on 2019-12-21 14:09

@kseistrup: can you check that if it is still an issue to have NODE_ENV set?

kseistrup commented on 2019-09-07 12:49

The note about $NODE_ENV is still valid: If $NODE_ENV is set to production, building the package fails.

BrLi commented on 2019-09-06 19:45

The install process of nodejs/yarn/electron application is too sequential that it is almost imposible to skip the electron compiling part, if you have any good idea, please don't hesitate to leave a message and let me know.

werod commented on 2019-06-25 05:11

@BrLi Works like a charm for me now. Thank you!

BrLi commented on 2019-06-25 03:30

Ok, the problem is due to webhostinghub-glyphs font in AUR has rename the fontname which is unknown to upstream nor zettlr.

I've update the PKGBUILD of the font to include the original font which should fix the issue.

werod commented on 2019-06-24 20:37

This is what it looks like for me, with the icons missing on the toolbar across the top.

https://imgur.com/a/YevFyhe

BrLi commented on 2019-06-21 19:55

@Blueko: would you mind taking some screenshot?

Blueko commented on 2019-06-21 17:33

@Brli I can confirm UI is broken for me, may be for the missing fonts.

BrLi commented on 2019-06-17 07:10

Agree with @kseistrup, however, as NODE_ENV is not a predefined env. variable of shell, user should trim that on their own.