unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: New hook before-region-change-functions wanted
Date: Mon, 11 Sep 2017 16:45:05 +0000	[thread overview]
Message-ID: <20170911164505.GA3605@ACM> (raw)
In-Reply-To: <E1drDML-00007a-Vs@fencepost.gnu.org>

Hello, Richard.

On Sun, Sep 10, 2017 at 21:17:57 -0400, Richard Stallman wrote:
>   > > The other approach has the virtue of being entirely internal.  It will
>   > > not require an announcement, or adding to the Lisp manual.

>   > Yes.  This other approach is slightly more difficult to debug with, but
>   > not unreasonably so.

> Just from curiosity, why is it more difficult to debug with?
> Since it has no effect on behavior, and its only effect is to speed
> up some cases, I'd expect it to have no effect on debugging.

> Is there something I am missing?

As I said, the difference was small.

With the hook in place, the filling and use of the cache was entirely
disjoint from swapping the caches in and out - the former occurred on
calling syntax-ppss, the latter on the hook called from
widen/narrow-to-region.

Using the actual solution, the swapping in and out of the caches
occurred at the beginning of syntax-ppss (if needed), and NOT on
widen/n-t-r.  So until I got used to it, I was calling n-t-r, then
forgetting a token invocation of syntax-ppss, and wondering why the
caches hadn't been swapped.

In that sense, the hook would have been a cleaner solution.  A pity
about its overwhelming disadvantages.

> -- 
> Dr Richard Stallman
> President, Free Software Foundation (gnu.org, fsf.org)
> Internet Hall-of-Famer (internethalloffame.org)
> Skype: No way! See stallman.org/skype.html.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2017-09-11 16:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08 14:46 New hook before-region-change-functions wanted Alan Mackenzie
2017-09-08 15:07 ` John Wiegley
2017-09-08 15:10 ` Eli Zaretskii
2017-09-08 15:12   ` Alan Mackenzie
2017-09-08 20:47 ` Dmitry Gutov
2017-09-09 13:46   ` Stefan Monnier
2017-09-08 22:22 ` Richard Stallman
2017-09-09  8:33   ` Alan Mackenzie
2017-09-10  2:44     ` Richard Stallman
2017-09-10  7:37       ` Alan Mackenzie
2017-09-11  1:17         ` Richard Stallman
2017-09-11 16:45           ` Alan Mackenzie [this message]
2017-09-12 15:46       ` Andreas Röhler
2017-09-09 13:44 ` Stefan Monnier
2017-09-10 18:53   ` Alan Mackenzie
2017-09-10 22:21     ` Stefan Monnier
2017-09-10 23:02       ` Drew Adams

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=20170911164505.GA3605@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).