Package Details: emacs-ng-git 1:r149638.79390ea31d-1

Git Clone URL: https://aur.archlinux.org/emacs-ng-git.git (read-only, click to copy)
Package Base: emacs-ng-git
Description: A new approach to Emacs - Including TypeScript, Threading, Async I/O, and WebRender
Upstream URL: https://emacs-ng.github.io/emacs-ng/
Licenses: GPL3
Conflicts: emacs, emacs-ng
Provides: emacs, emacs-ng
Submitter: alienzj
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 2
Popularity: 0.000556
First Submitted: 2021-02-04 11:45 (UTC)
Last Updated: 2021-08-01 20:44 (UTC)

Required by (424)

Sources (1)

Latest Comments

haawda commented on 2022-02-26 13:27 (UTC)

The find command in the last line does not work for me. Als --with-nativecomp is an unrecognized configure option (should be --with-native-compilation).

appetrosyan commented on 2021-09-12 16:13 (UTC)

Can't compile. The compiler output is very nondescript, something-something Mutex unlock... What do mutexes have to do with compilation?

dr460nf1r3 commented on 2021-07-04 12:27 (UTC) (edited on 2021-07-04 12:29 (UTC) by dr460nf1r3)

This also seems to miss some makedepends, namely git, python & clang. It would probably also be a good idea to remove -j8 from the make command as not everyone has 8 cores to build this on. Set your personal amount of cores used in /etc/makepkg.conf :)

FabioLolix commented on 2021-05-04 15:34 (UTC)

Please change URl to https://emacs-ng.github.io/emacs-ng/ and add a proper pkgver() in the pkgbuild https://wiki.archlinux.org/title/VCS_package_guidelines#Git

wickedjargon commented on 2021-04-26 15:52 (UTC)

cormacc, I am also having the same issue. I tried emacs -fn "Liberation Mono" but this didn't work. Emacs still works within the terminal though, emacs -nw. I am using gnome if it makes a difference. Please let me know if anyone finds a solution.

cormacc commented on 2021-04-14 10:11 (UTC)

Anyone else having an issue launching this? I get the following error: Font ‘Monospace’ is not defined

No issue with emacs 27.2 Tried temporarily clobbering my .emacs.d to see if it's some rogue setting there, but has no effect.