Package Details: emacs-lucid 26.3-1

Git Clone URL: (read-only, click to copy)
Package Base: emacs-lucid
Description: The extensible, customizable, self-documenting real-time display editor (Lucid toolkit version)
Upstream URL:
Licenses: GPL3
Conflicts: emacs
Provides: emacs=26
Submitter: favadi
Maintainer: jpkotta
Last Packager: jpkotta
Votes: 23
Popularity: 0.005593
First Submitted: 2012-07-23 16:07
Last Updated: 2019-09-03 19:05

Required by (416)

Sources (2)

Latest Comments

1 2 3 4 Next › Last »

jpkotta commented on 2018-07-31 16:13

I guess they don't seem very important. It sounds like "color fonts" (which I just learned are a thing) cause Emacs to crash because it doesn't support them. But why use color fonts with Emacs if it doesn't support them anyway? If someone is experiencing problems, I will add the patches.

stef204 commented on 2018-07-31 12:44


are the 3 patches in the official emacs package not needed with lucid or just something you don't feel is needed (mostly the first 2 patches)?

jpkotta commented on 2018-06-14 17:29

@tychoish Yeah I've noticed that. The main emacs PKGBUILD in extra also has that warning. I don't think it's a big deal. If I get some time, I'll try to make that warning go away.

tychoish commented on 2018-06-14 14:52

==> Checking for packaging issues... ==> WARNING: Package contains reference to $srcdir usr/bin/emacs-26.1

It looks like there's an issue in packaging?

CyberShadow commented on 2018-02-19 15:22

Hi, would you mind updating the /var/games permissions fix as it is in the extra/emacs PKGBUILD?

Currently core/filesystem says the mode is 775, but this package says it's 755.

Edit: thanks!

eigengrau commented on 2017-09-11 18:28

Looks like they will be doing 25.3 as an emergency release.

eigengrau commented on 2017-09-11 18:12

Emacs 25.2 suffers from a trivially exploitable remote-code-execution vulnerability [1]. I’m not sure how fast things like this are backported (if at all), but since this is a rather concerning issue, maybe it might make sense to apply the patch [2] in the PKGBUILD to get this shipped to folks who don’t know about this and who haven’t applied any mitigation in their init.el.

[1] <>
[2] <>

jpkotta commented on 2017-07-20 17:11

You can just do a rebuild (`makepkg -f && pacman -U emacs-lucid...`), but yes bumping pkgrel forces it for everyone, which is convenient.

CyberShadow commented on 2017-07-20 08:02

Please bump pkgrel to fix "emacs: error while loading shared libraries: cannot open shared object file: No such file or directory" ?

eigengrau commented on 2017-04-19 05:59

When installing cask I just noticed some packages actually do use versioned requirements, so it might be convenient to have this «provides=emacs=$pkgver». For repo packages this seems to be the standard, so we should probably do this for our packages as well.