Package Details: ghostwriter 1.8.1-1

Git Clone URL: (read-only, click to copy)
Package Base: ghostwriter
Description: A cross-platform, aesthetic, distraction-free Markdown editor
Upstream URL:
Licenses: GPL3
Submitter: TamCore
Maintainer: J5lx
Last Packager: J5lx
Votes: 44
Popularity: 1.50
First Submitted: 2016-03-28 19:12
Last Updated: 2020-02-23 01:16

Dependencies (7)

Required by (0)

Sources (1)

Latest Comments

1 2 3 Next › Last »

J5lx commented on 2019-02-02 17:17

I can confirm that this is the case, however this is very clearly an upstream issue, and it has even been reported before: Apparently it was supposed to be fixed quite a while ago, but there seem to be other users who still have that problem. If Pandoc support is important to you, you should help resolve the problem in the conversation linked above. Also, that issue above is pretty easy to find by searching for the error message, so in the future please try using a search engine when you encounter problems.

j0hannes commented on 2019-02-02 16:44

Pandoc stopped working:

Export failed: --smart/-S has been removed. Use +smart or -smart extension instead. For example: pandoc -f markdown+smart -t markdown-smart. Try pandoc --help for more information.

J5lx commented on 2018-11-29 12:03

Sorry if I’m only adding more confusion here, but could you clarify when and where I provided a binary package of ghostwriter? I did attempt to provide binary builds of my packages a while ago, but I don’t remember doing so for ghostwriter. However, if there’s still a binary package flying around somewhere that I’ve forgotten about then I should probably remove it to prevent users from running into problems.

berturion commented on 2018-11-29 07:33

Thanks for this explanation @J5lx. I am sorry, I think I didn't expressed myself correctly, I was asking the opposite (I am french). I understand that a rebuild is a technical necessity like you said and I agree with that. And that's why I didn't understand why you provided a binary before, that implied manual operation by the user to re-compile when the program fails because of an incompatible library version. :) For me, it is better waiting a little for a compilation and being sure that the program will work than having a binary that can fail following the library versions installed on the system. But everything is clear now. Thank you for providing Ghostwriter to Arch users. I really love it.

J5lx commented on 2018-11-26 21:56

I agree that having to rebuild the package is annoying, but unfortunately it is a necessary evil and the only reliable way to avoid it completely is by keeping the version of hunspell that ghostwriter was compiled against (1.6 here) installed on your system alongside the new version (1.7). Given that no hunspell package for 1.6 specifically exists right now, you’d have to create one yourself, and that’s arguably even more annoying that simply rebuilding ghostwriter. The reason for this mess is that the hunspell update from 1.6 to 1.7 included a soname change (from to To the best of my knowledge, this usually indicates an ABI break, meaning that even though it may be possible to compile software against either version, software that has already been built against the older version may not be compatible with binaries of the newer version. In other words, the compiled executable of ghostwriter that you originally built on your system cannot be guaranteed to be compatible with the new version of hunspell even when the source is compatible. Having an AUR package that requires to be rebuilt after an update like this isn’t about some sort of “advantage” – it’s simply a technical necessity. I hope this clears things up.

berturion commented on 2018-11-26 18:43

Thanks, it works now. I saw the package rebuilding itself. Yes I use yay sometimes or pamac with AUR enabled. No offense, but I don't understand the advantage of having an AUR package that needs a manual building operation. Though, for me it's ok now. Even if it is longer to update because of this compilation, I am sure now that it will work at the end.

J5lx commented on 2018-11-25 19:05

In a situation like that, try to rebuild the package. 95% of the time that’s all it takes to fix the problem. To make it easier for you, I made a new package release, so if you’re using some sort of AUR helper you should get the package rebuilt automatically the next time you update.

berturion commented on 2018-11-25 18:31

I confirm that ghostwriter fails to launch with the following error:

ghostwriter: error while loading shared libraries: cannot open shared object file: No such file or directory

sosonok commented on 2018-11-25 08:31

After latest hunspell update, Ghostwriter won't run. It's looking for version 1.6.

kaslusimoes commented on 2018-08-13 13:09

Changed a few things to support the latest version. The patch previously being used is no longer needed because it was already introduced in the new version:


prepare() {
  cd "${srcdir}/${pkgname}-${pkgver}"