Package Details: texworks 0.6.1-1

Git Clone URL: (read-only)
Package Base: texworks
Description: A TeX IDE inspired by TeXShop.
Upstream URL:
Licenses: GPL2
Conflicts: texworks-svn
Provides: texworks
Submitter: None
Maintainer: trichards
Last Packager: trichards
Votes: 81
Popularity: 0.805150
First Submitted: 2010-02-16 15:52
Last Updated: 2016-05-02 14:13

Dependencies (12)

Required by (0)

Sources (1)

Latest Comments

trichards commented on 2016-08-05 20:33

@jeanfrancisroy: The list of dictionaries presented in TeXworks is accurate, as far as I can tell. In this screenshot, I have hunspell-en and hunspell-de installed:

After installing the hunspell-en package, it may look like there are lots of different dictionaries in the /usr/share/myspell/dicts directory, but if you look at where those symlinks point to (/usr/share/hunspell), you'll see that most of them are actually just aliases for the en_GB dictionary. There are only three real dictionaries provided by the hunspell-en package, and TeXworks ends up displaying en_ZW for the en_GB dictionary because of the aliases.

jeanfrancisroy commented on 2016-08-05 19:59

TexWorks doesn't seem to find my hunspell dictionaries. If I'm right the default directory for TexWorks dictionaries is /usr/share/myspell/dicts, which on my system contains many dictionaries, but when I launch the application only a subset of those is found: en_CA, en_US, en_ZW and fr_LU.

I don't even know where it finds that list of dictionaries, as I never manually installed any of those. Anybody had it to work?

MarkH commented on 2016-07-06 23:32

I just had a problem where texworks would not start after hunspell was updated (1.3.0 -> 1.4.1) and instead print the error:

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

The solution was to reinstall texworks so it would use the updated hunspell.

jakebailey commented on 2016-04-08 01:33

Thanks, everything builds now. Sorry I didn't respond, I made the post, but forgot to subscribe to the comments. :\

trichards commented on 2016-04-07 14:38

@qwertzdenek: Thanks the the suggestion. I've switched the build to use qt5. Adding qt5-script (and qt5-tools in makedepends) makes the qt5 build work correctly for me in a clean chroot.

qwertzdenek commented on 2016-04-07 14:02

@trichards: I finally built it using QT5. I missed qt5-script. So you need:
'qt5-base' 'qt5-script' 'poppler-qt5'

now you can set desired version to 5 and get rid of 4.
Happy TeXting

trichards commented on 2016-04-07 13:27

@henkm: Thanks for the feedback; I've added that flag to the PKGBUILD.

henkm commented on 2016-04-07 07:24

You can force CMake to use qt4 by adding the following to the CMake options:

This made it compile for me (you may need to clean out leftover stuff, I deleted and redownloaded the whole project)

qwertzdenek commented on 2016-04-06 22:32

@trichards: I can confirm that. CMake require QT4 so I hope he know what is doing. It crashed in section QtPDF for me. I don't know how to force QMake to accept QT5.

trichards commented on 2016-04-06 19:24

@jakebailey: I built this package successfully before pushing changes to the AUR, both in my normal environment, and in a clean chroot.

What is the output of your "TeXworks has been configured:" section while building?

All comments