From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: emacs-devel@gnu.org
Subject: RE: interactive feel of Emacs: the need for speed, and -Q [measure.el]
Date: Mon, 30 Mar 2020 08:32:12 -0700 (PDT) [thread overview]
Message-ID: <f9537096-58ad-4110-b8a6-cd74965d1744@default> (raw)
In-Reply-To: <87tv26qvwh.fsf@ebih.ebihd>
Not sure what you're asking. But if you're asking
which parts of your non -Q setup could be causing
a slowdown then the answer is typically to bisect
your init file, to narrow the search.
There's also profiling, which you can do after
you've narrowed things down to specific code, if
things aren't obvious at that point.
But I think you already knew this, so probably
I've misunderstood the question.
next prev parent reply other threads:[~2020-03-30 15:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 5:00 interactive feel of Emacs: the need for speed, and -Q [measure.el] Emanuel Berg via Users list for the GNU Emacs text editor
2020-03-30 15:32 ` Drew Adams [this message]
2020-04-07 16:25 ` Emanuel Berg via Emacs development discussions.
2020-04-07 16:49 ` Michael Welsh Duggan
2020-04-08 5:51 ` Emanuel Berg via Emacs development discussions.
2020-04-08 14:17 ` Michael Welsh Duggan
2020-04-12 1:16 ` Emanuel Berg via Emacs development discussions.
2020-04-12 2:51 ` Michael Welsh Duggan
2020-04-14 23:00 ` Emanuel Berg via Emacs development discussions.
2020-04-15 1:34 ` T.V Raman
2020-04-15 2:21 ` Emanuel Berg via Emacs development discussions.
2020-04-15 14:51 ` T.V Raman
2020-04-15 15:43 ` Basil L. Contovounesios
2020-04-15 16:06 ` Stefan Monnier
2020-04-16 19:14 ` Stephen Leake
2020-04-16 19:59 ` Clément Pit-Claudel
2020-04-16 20:14 ` Stefan Monnier
2020-04-23 20:05 ` chad
2020-04-23 20:43 ` Stephen Leake
2020-04-23 20:57 ` Stefan Monnier
2020-04-23 23:35 ` chad
2020-04-24 3:28 ` Stefan Monnier
2020-04-17 8:48 ` Stephen Leake
2020-04-16 20:04 ` Stefan Monnier
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=f9537096-58ad-4110-b8a6-cd74965d1744@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).