Package Details: zettlr 1.8.7-2

/api/cask/zettlr.json (JSON API) Cask code on GitHub. Current version: 1.8.7. Analytics: Installs (30 days) zettlr: 271: Installs (90 days) zettlr: 901: Installs (365.

Package Actions

• View PKGBUILD / View Changes

The file in /usr/bin/zettlr was linked to /opt/Zettlr/zettlr, but the actual binary is /opt/Zettlr/Zettlr. It was an easy fix, but perhaps the last line in PKGBUILD should be updated. Itsagoodbrain commented on 2020-11-30 19:40. Zettlr: A Markdown editor for the 21 st century Download Zettlr uses Matomo to analyse our visitors's behaviour. In compliance with the GDPR (General Data Protection Regulation), you can choose to opt out of tracking. You are currently opted in.

Dependencies (7)

• electron(electron-ozone, electron-beta-bin, electron-nightly-npm)
• git(git-git)(make)
• pandoc(pandoc-bin, pandoc-sile-git)(make)
• yarn(yarn-nightly)(make)
• pandoc(pandoc-bin, pandoc-sile-git)(optional) – For exporting to various format
• texlive-bin(texlive-bin-svn, texlive-full, texlive-installer)(optional) – For Latex support
• ttf-lato(ttf-google-fonts-git, ttf-google-fonts-typewolf)(optional) – Display output in a more comfortable way

BrLi commented on 2021-01-18 14:39

@mefistofeles it is a broken change in electron 11.1.1->11.2.0

you can try to downgrade it from your pacman cache. Winrar torrent for mac.

mefistofeles commented on 2021-01-18 00:23

Hello, I keep getting a segfault error when I run zettlr, as follows

Also dmesg is showing the following:electron[65090]: segfault at 58 ip 00005557ecf2ace6 sp 00007ffd4b8ff7f0 error 4 in electron[5557ece78000+5e74000]

Any ideas why this may be happening? (Up to date archlinux, btw)

tovo commented on 2021-01-11 23:01

Hi,Can't build it:

> ERROR: Integrity checks (sha256) differ in size from the source array.

Probably need to update sha256 signature.

caleb commented on 2021-01-07 14:21

@BrLi You can't download raw files from branch HEADs and save them to unversioned file names and expect it not to break, that's just miss-handling sources. Bare filenames for sources like you were using only works for sources that are versioned in the Git repo alongside the PKGBUILD. All others must have version information in the file name, and in the case of files that may need bumping separately from the official pkgrel version they should also include the pkgrel version. I've fixed the sources array to handle versioning and checksums for the offending files. This should solve both the current snafu with the zh-TW translation and future ones with the other files.

Secondarily I question the wisdom of injecting stuff that's not in the upstream project making this package a different product that what's on the tin. Have you contributed the translation work and any issues with CSLs upstream?

BrLi commented on 2020-12-30 10:26

@rdricco, did you ever git pull the new updates from AUR?

the last attempt would be to just remove that line from source and checksum arrays if you don't need that translation. Adobe after for mac os x.

rdricco commented on 2020-12-29 05:46

Didn't work @BrLi. I removed everything related to Zettlr and still gets the validation error on zh-TW.json

Zettler Relay

BrLi commented on 2020-12-25 01:47

currently upstream is having problem compiling without downloading pandoc (appx. 150MB extra bandwidth) on 1.8.4, while from 1.8.3 there is parameter problem in the default pandoc export command, thus would stay in 1.8.2 for a while until above issues are fixed.

BrLi commented on 2020-12-24 23:26

@rdricco make sure you're doing a clean build, ie. the directory is clean and the sources doesn't exist before fetching by makepkg.

rdricco commented on 2020-12-22 23:41

BrLi commented on 2020-12-12 06:43

@Nielzsen, @lambtho: please check that you're using the latest stable nodejs, aka.community/nodejs 15.4.0-1.

If things still happens, please report the bug upstream, as it is in source code where I didn't touch.

Also, the *-bin should always work, as it is just a repackage from distributed binary.

This is the official documentation for the Zettlr Markdown Editor. This documentation describes the features Zettlr offers for writing text and organizing your files, as well as customizing your experience. In case you have not yet received a copy of Zettlr, you can do so now by going to our download page. Zettlr is currently supported on Windows (7 or newer), macOS (10.10 or newer), and various Linux distributions. Please consult the setup instructions for platform-specific instructions on installing the application on your computer.

On this Documentation¶

This documentation is structured with Zettlr's extensive feature set and target group in mind. We have sorted all available features into a few central categories. If you know exactly what you are looking for, the search bar at the top right is the right starting point for you, otherwise, please follow the descriptions below:

• The First Steps section contains instructions on how to set up everything necessary to start working with Zettlr. It also provides a short 'getting started' guide in case you want to see what the app offers.
• A section on concepts familiarizes you with a few concepts that form the basis of how Zettlr works. It is recommended to read through these documents carefully.
• Guides contain a few guides for quickly setting up Zettlr for broadly described use cases. You will likely need to modify the presented settings to match your own workflow, but these are great starting points to have Zettlr work for you.
• The Core describes the central writing and file management feature sets of Zettlr: What it can do, how it can do it, and where you can customize it.
• Academic Tools focuses on features that are especially useful to –but not limited to!– students and academics.
• References contain information on general topics (such as an explanation of all available settings) which serve as a quick reference for you.

Get Involved!¶

Zettlr Github

Zettlr is a free and open source software, which means that its source code is publicly available, and the application comes at no cost. However, this also means that there is no paid staff behind the app – it is completely managed by the community. This means that we actively encourage users to get involved with the app! Depending on your skills and what you like most, there are various ways in which you can help Zettlr out:

Zettlr Android

• You can translate the app in more languages, and improve existing ones
• You can translate and improve the documentation (GitHub account required)
• You can join the community on Reddit and the forum and help new and other users
• You can tackle open issues on GitHub and help develop the application itself

Zettlr Review

More information on how to get involved can be found here in the documentation.