From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: johnw@gnu.org, 14518@debbugs.gnu.org
Subject: bug#14518: C and Emacs Lisp code parts
Date: Thu, 07 Jul 2016 18:16:13 +0300 [thread overview]
Message-ID: <83furllbr6.fsf@gnu.org> (raw)
In-Reply-To: <dc92986b-cfb1-02dc-4baf-9938e437e141@easy-emacs.de> (message from Andreas Röhler on Thu, 7 Jul 2016 09:33:12 +0200)
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, John Wiegley <johnw@gnu.org>
> Date: Thu, 7 Jul 2016 09:33:12 +0200
>
> IMHO in the case given the reasons are pretty simple. See for example in
>
> 'prepare-abbrev-list-buffer':
> ...
> (dolist (table abbrev-table-name-list)
>
> Such happens not only there. With the number of active modes/tables it growths - maybe exponentially?
>
> Also: why define-abbrevs must process the whole buffer? Why not deal with just the changed parts?
(This is no longer about C vs Lisp, right?)
If you want to propose changes in abbrevs.el whose purpose is to speed
it up, please do. But please also include with the changes the
rationale in the form of timing measurements, so that, if the code
becomes more complicated as result, we could judge the speed-up
against the added complexity.
Thanks.
next prev parent reply other threads:[~2016-07-07 15:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <624c3d37-c829-7187-a699-7d7bbc211a20@online.de>
[not found] ` <83ziq1u668.fsf@gnu.org>
[not found] ` <ad1775e4-f480-f05d-2c66-b86d5d3bdacf@online.de>
[not found] ` <20160701091653.GA2531@acm.fritz.box>
[not found] ` <5fcdeec5-fcde-d0ab-e256-e1b2ceb40ccb@online.de>
[not found] ` <83shvttsq6.fsf@gnu.org>
[not found] ` <m2a8hvzood.fsf@newartisans.com>
2016-07-06 7:25 ` bug#14518: C and Emacs Lisp code parts Andreas Röhler
[not found] ` <fc7419b6-3544-3204-357f-2739a83669d5@online.de>
2016-07-06 14:01 ` Noam Postavsky
2016-07-06 14:52 ` Eli Zaretskii
2013-05-31 9:30 ` bug#14518: abbrev edits - delay when saving Andreas Röhler
2013-06-01 3:01 ` Leo Liu
2013-06-01 5:52 ` Andreas Röhler
2013-06-05 10:11 ` Andreas Röhler
2013-06-05 13:12 ` Stefan Monnier
2013-06-05 17:02 ` Glenn Morris
2013-06-05 17:20 ` Andreas Röhler
2013-06-07 1:43 ` Glenn Morris
2013-06-07 5:38 ` Andreas Röhler
2013-06-07 7:13 ` Glenn Morris
2013-06-07 7:41 ` Andreas Röhler
2016-07-06 15:44 ` bug#14518: C and Emacs Lisp code parts Glenn Morris
2016-07-06 16:15 ` Eli Zaretskii
2016-07-06 22:36 ` John Wiegley
2016-07-07 7:33 ` Andreas Röhler
2016-07-07 15:16 ` Eli Zaretskii [this message]
2016-07-06 16:21 ` Andreas Röhler
2016-07-06 16:37 ` Eli Zaretskii
2016-07-06 17:27 ` Andreas Röhler
2016-07-06 17:35 ` Eli Zaretskii
2016-08-05 23:38 ` bug#14518: Status: abbrev edits - delay when saving npostavs
2016-12-07 19:56 ` Glenn Morris
2016-07-06 15:27 ` bug#14518: C and Emacs Lisp code parts Phillip Lord
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=83furllbr6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14518@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.de \
--cc=johnw@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).