Package Details: leo 6.0-1

Git Clone URL: https://aur.archlinux.org/leo.git (read-only)
Package Base: leo
Description: Literate programmer's editor, outliner, and project manager
Upstream URL: http://leoeditor.com/
Licenses: custom
Submitter: None
Maintainer: rraval
Last Packager: rraval
Votes: 28
Popularity: 0.001086
First Submitted: 2006-05-08 11:34
Last Updated: 2019-08-21 00:24

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

djscholl commented on 2012-04-26 01:30

Thank you for your comments, Arch user exaos. I have bumped the Arch version to fix the execute permissions on /opt/leo/launchLeo.py.

Please let me clarify the spell check situation. With a default Arch installation, and python2-pyenchant installed, leo will start. However, it starts with error messages, and the spell check will not work. The reason is that Leo is written to install into a user-writable directory. Workarounds may be required when installing leo with Arch package management, which installs into system directories. This is why the leo.install file reports that leo "can be configured" to use pyenchant.

The leo spell check requires a user-writable dictionary file, so that words can be added. The default dictionary /opt/leo/leo/plugins/spellpyx.txt is shared by users, and is not user-writable. The pyenchant error message is misleading, as the dictionary file contents are valid, but the permissions are not valid. To configure spell check requires several steps. First, create ~/.leo/myLeoSettings.leo for your personal leo settings, as described in the Leo website documentation. Next, edit your personal settings to tell leo about your personal dictionary file. Under settings -> spell checking, find the headline "enchant_local_dictionry = None". Change "None" to "~/.leo/spellpyx.txt", and save your personal settings. Finally, copy the spellpyx.txt file from its default location to your ~/.leo directory. The next time you start leo, the spell check should work with no error messages. Please post again if you still have issues.

Anonymous comment on 2012-04-24 15:12

Do not install `python2-pyenchant` as recommended! It will cause leo failed to start. Another problem is, the `/opt/leo/launchLeo.py` is not executable after install, please fix it!

djscholl commented on 2012-03-30 23:26

Update for new upstream version, thanks to Arch user mesteiral.

djscholl commented on 2011-07-28 23:44

Upstream updated to 4.9. Note that there is now only one GUI (pyqt). The tkinter GUI is gone.

djscholl commented on 2011-06-15 20:18

Minor version bump because python2-qt was renamed to python2-pyqt.

djscholl commented on 2011-01-22 00:40

Arch version bump to change pyqt to python2-qt, thanks to Arch user adaptee.

adaptee commented on 2011-01-21 04:15

dependency 'pyqt' should be renamed into 'python2-qt'

djscholl commented on 2010-12-16 13:49

Update to 4.8-final release from upstream. I have switched from the AUR python-pmw to the Pmw bundled with leo because the AUR python-pmw PKGBUILD was broken by the Arch update to python 3. The Pmw tests bundled with leo mostly fail, and so do the tests in the AUR python-pmw. This may be a reason to prefer the leo qt GUI, which runs by default. Note that leo is a large package with a long history, and many helper scripts, plugins, extensions, etc. I updated the main calling script from python to python2, but there are other places where "python" is hard-coded. If you encounter issues with some component of leo, one of the first things you should do is investigate whether another "#!/usr/bin/env python" needs to be changed to "#!/usr/bin/env python2".

djscholl commented on 2010-11-16 03:09

Bumped the Arch version number for compatibility with the python 3 upgrade, thanks to Arch users hollunder and boon.

boon commented on 2010-11-10 15:49

It works for me, thanks for your efforts!