Github messages for voidlinux
 help / color / mirror / Atom feed
From: zenny <zenny@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [Package Request] GccEmacs
Date: Mon, 09 Nov 2020 10:43:32 +0100	[thread overview]
Message-ID: <20201109094332.efeZTGwEqkKuAuhobRwi8TvjUBRQNFBGsqnbo-4YZQ8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24240@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]

Closed issue by zenny on void-packages repository

https://github.com/void-linux/void-packages/issues/24240

Description:
# Package Name
GCCemacs (http://akrl.sdf.org/gccemacs.html)

# Linux-related link
https://www.emacswiki.org/emacs/GccEmacs
http://akrl.sdf.org/gccemacs.html#org248e6b1
http://akrl.sdf.org/gccemacs.html#orgec98bb2

# Practical Rationale

> This (slowness) comes up often. The first thing folks fresh off the boat from other editors will notice is that Emacs has a low threshold for performance issues. It doesn’t take much to get it to scroll like molasses... There is an unfortunate but necessary adjustment of expectations new users must undergo, when they adopt Emacs. Doom has inherited this curse. It’s raison d’etre is to improve the situation, but I can only go so far, especially if you choose to enable all the most expensive features. You will unavoidable find cases where Emacs is just slow.

Reference:
https://github.com/hlissner/doom-emacs/blob/fd3b89854eb13ddb2c8ecc2da68a9cbb0dcdb836/docs/faq.org#why-is-emacsdoom-slow

> One of the things that irritated me the most about emacs was how slow it was when the text in one of the files got very long. If a line (paragraphs are considered one line in emacs) gets too long, emacs starts to slow down till you start a new paragraph. As someone who does writing for a living, taking notes, inserting citations, this starts to get very annoying. Upon conversation with the creator of DOOM emacs, I installed GCC emacs. There are a bunch of different ways to do this, but I followed the amazing gist written by mjlbach. When I ran into trouble he took time out to help me figure it out. Much thanks to him. As a result, my emacs runs as fast as it ever has.

Reference:
https://github.com/sunnyhasija/DOOMEmacs/blob/master/README.org#move-to-gcc-emacs

# Manual installation in Void

Tried to install in voidlinux without success as follows:

```
$ git clone https://git.savannah.gnu.org/emacs.git
$ cd emacs
$ git checkout feature/native-comp
$ ./autogen.sh
$ ./configure --with-nativecomp
...
configure: error: Installed libgccjit has failed passing the smoke test.
You can verify it yourself compiling:
<https://gcc.gnu.org/onlinedocs/jit/intro/tutorial01.html>.
Please report the issue to your distribution.
Here instructions on how to compile and install libgccjit from source:
<https://gcc.gnu.org/wiki/JIT>.
```

ATTN: @leahneukirchen (the emacs package maintainer)

  parent reply	other threads:[~2020-11-09  9:43 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 11:57 [ISSUE] [Package Request] GCCemacs zenny
2020-08-13  9:03 ` [Package Request] GccEmacs leahneukirchen
2020-08-13 12:10 ` zenny
2020-08-13 12:20 ` zenny
2020-08-16 23:31 ` Javyre
2020-08-17  7:45 ` zenny
2020-08-17  7:55 ` zenny
2020-08-21  0:27 ` Javyre
2020-09-27 23:10 ` ap4y
2020-10-24  4:25 ` ericonr
2020-10-29  8:49 ` zenny
2020-10-29  8:50 ` zenny
2020-10-29 19:36 ` zenny
2020-11-03 17:59 ` Javyre
2020-11-03 17:59 ` Javyre
2020-11-05  8:09 ` zenny
2020-11-05 14:45 ` Javyre
2020-11-05 21:00 ` zenny
2020-11-06  5:24 ` zenny
2020-11-06 18:33 ` zenny
2020-11-09  9:43 ` zenny
2020-11-09  9:43 ` zenny [this message]
2021-02-15 21:06 ` lane-brain
2021-02-15 22:38 ` ericonr
2021-02-16  0:29 ` ericonr
2021-02-16  1:08 ` lane-brain
2021-02-16  1:10 ` lane-brain
2021-02-16  1:11 ` lane-brain
2021-02-16  1:12 ` lane-brain
2021-02-16  1:13 ` lane-brain
2021-02-16  1:14 ` lane-brain
2021-02-16  1:15 ` lane-brain
2021-02-16  1:19 ` ericonr
2021-02-16  1:40 ` lane-brain
2021-02-16  1:40 ` lane-brain
2021-02-27  0:12 ` xianwenchen
2021-06-22 18:20 ` lulcat
2021-06-22 18:21 ` lulcat
2021-10-17  8:03 ` basicfunc
2021-10-17 15:47 ` leahneukirchen
2022-01-11 10:01 ` soanvig
2022-01-11 14:07 ` basicfunc
2022-01-11 14:09 ` basicfunc
2022-04-16 14:05 ` [ISSUE] [CLOSED] " leahneukirchen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201109094332.efeZTGwEqkKuAuhobRwi8TvjUBRQNFBGsqnbo-4YZQ8@z \
    --to=zenny@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).