unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via help-gnu-emacs <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: 3 x need for speed
Date: Tue, 11 Jun 2019 22:11:14 +0200	[thread overview]
Message-ID: <86h88vyja5.fsf@zoho.eu> (raw)

Since the discussion about Elisp being slow,
I have already found two cases where it is:

1) Autocompletion with large search spaces.
   Try do `M-x insert-char h TAB'. This
   takes >10s for me.

2) Colorizing with regexps. Here [1] is an
   example which I had disabled since I got the
   RPi3 (granted, not the fastest of
   computers). Also, I'm not fluent with
   regexps (who is? :)) so I'm pretty sure some
   of that could be written in a better, i.e.
   faster, way.

Also, when I started doing Elisp, this lexical
(static) vs dynamic scope was obviously above
my head. But even then I thought, without
knowing there was an alternative or an explicit
name for either modes, even then I thought
lexical scope was/is much better, and that's
the way I always wrote the code. So in theory,
I should be able to put

;;; -*- lexical-binding: t -*-

in all my files, and it wouldn't brake
anything, right?

Rather, the strange thing is, why did it always
work, typing it lexical style, but actually
having it dynamic?

And the interesting thing will be, will it be
faster this way? The load time perhaps?
Not that that will matter, since I have Emacs
on all the time...

-- 
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal




             reply	other threads:[~2019-06-11 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 20:11 Emanuel Berg via help-gnu-emacs [this message]
2019-06-11 20:14 ` 3 x need for speed Emanuel Berg via help-gnu-emacs

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=86h88vyja5.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).