From: "Perry E. Metzger" <perry@piermont.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: deng@randomsample.de, emacs-devel@gnu.org
Subject: Re: Speed of keyboard macro execution?
Date: Thu, 10 Dec 2015 12:00:51 -0500 [thread overview]
Message-ID: <20151210120051.6be8201f@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <83r3iu9rvp.fsf@gnu.org>
On Thu, 10 Dec 2015 18:43:06 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Wed, 9 Dec 2015 18:03:43 -0500
> > From: "Perry E. Metzger" <perry@piermont.com>
> > Cc: emacs-devel@gnu.org
> >
> > On Wed, 09 Dec 2015 23:13:17 +0100 David Engster
> > <deng@randomsample.de> wrote:
> > > Perry E. Metzger writes:
> > > > Perhaps it would be good to dig in to what is causing the
> > > > issues in question...
> > >
> > > Emacs does not cope very well with very long lines.
> >
> > How might that be addressed?
>
> This is simply bug#13675.
>
> It's a bit disingenuous on the part of that person to compare Emacs
> with another editor _solely_ where there's a known inefficiency in
> Emacs, and pretend that this is somehow representative of the
> general differences in performance between these two editors.
> After all, how frequently do you need to edit files with lines in
> excess of 11K characters?
I don't know if it was disingenuous or not, but I think that being
able to improve performance would not be a bad thing. I've noticed
that a lot of things (like keyboard macros) are often slower than
expected in modern Emacs. We may, as a developer community, have
allowed the speed of modern hardware to lull us into complacency on
issues like performance. Emacs should be the best editor it can
be.
I suppose this ties back in to earlier discussions about automated
testing (as, among other things, automated testing can find
performance regressions before they matter.)
Perry
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2015-12-10 17:00 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 21:39 Speed of keyboard macro execution? Perry E. Metzger
2015-12-09 22:13 ` David Engster
2015-12-09 23:03 ` Perry E. Metzger
2015-12-10 16:43 ` Eli Zaretskii
2015-12-10 17:00 ` Perry E. Metzger [this message]
2015-12-10 17:14 ` John Wiegley
2015-12-10 17:27 ` David Engster
2015-12-10 17:33 ` Perry E. Metzger
2015-12-10 17:39 ` David Engster
2015-12-10 17:53 ` Eli Zaretskii
2015-12-10 18:10 ` Perry E. Metzger
2015-12-10 18:41 ` Eli Zaretskii
2015-12-10 18:44 ` David Kastrup
2015-12-10 18:57 ` Eli Zaretskii
2015-12-10 19:38 ` David Kastrup
2015-12-10 20:00 ` Eli Zaretskii
2015-12-10 20:09 ` David Kastrup
2015-12-10 20:43 ` Eli Zaretskii
2015-12-10 20:55 ` David Kastrup
2015-12-10 20:16 ` Perry E. Metzger
2015-12-10 20:18 ` John Wiegley
2015-12-10 20:36 ` David Kastrup
2015-12-10 20:43 ` John Wiegley
2015-12-10 21:01 ` David Kastrup
2015-12-10 21:26 ` John Wiegley
2015-12-10 23:35 ` David Kastrup
2015-12-11 1:14 ` John Wiegley
2015-12-11 6:27 ` David Kastrup
2015-12-12 22:56 ` John Wiegley
2015-12-12 23:46 ` David Kastrup
2015-12-13 0:16 ` John Wiegley
2015-12-13 0:32 ` David Kastrup
2015-12-12 23:20 ` Per Starbäck
2015-12-12 16:51 ` Perry E. Metzger
2015-12-12 17:42 ` David Kastrup
2015-12-12 23:01 ` Disabling visual lines for macros (was: Speed of keyboard macro execution?) John Wiegley
2015-12-12 23:33 ` Disabling visual lines for macros David Kastrup
2015-12-10 20:45 ` Speed of keyboard macro execution? Perry E. Metzger
2015-12-10 20:50 ` John Wiegley
2015-12-10 20:48 ` Eli Zaretskii
2015-12-10 20:50 ` John Wiegley
2015-12-10 21:13 ` David Kastrup
2015-12-10 17:37 ` Eli Zaretskii
2015-12-10 17:43 ` John Wiegley
2015-12-10 17:54 ` Eli Zaretskii
2015-12-10 18:15 ` Achim Gratz
2015-12-10 18:47 ` Eli Zaretskii
2015-12-12 2:14 ` Joseph Mingrone
2015-12-12 7:39 ` Eli Zaretskii
2015-12-12 17:28 ` Joseph Mingrone
2015-12-12 17:57 ` Eli Zaretskii
2015-12-12 18:12 ` Joseph Mingrone
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=20151210120051.6be8201f@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=deng@randomsample.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
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).