all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Criticism of jit-lock--antiblink-post-command
Date: Wed, 27 Nov 2019 09:30:59 +0000	[thread overview]
Message-ID: <CALDnm51xuq7XVVUQyXcR4FP7iz0wcnmf1YDa=XxSUcX4mqHVfQ@mail.gmail.com> (raw)
In-Reply-To: <95046d793384835470809c187eb865be@webmail.orcon.net.nz>

On Wed, Nov 27, 2019 at 5:54 AM Phil Sainty <psainty@orcon.net.nz> wrote:
>
> On 2019-11-27 10:09, João Távora wrote:
> > Regarding the markers, I'll have a look. But it seems
> > premature optimization.
>
> AFAIK that one is standard best practice for working with
> markers,

I understand that, and I think I've seen cases where it
matters.  Just this one doesn't seem to (for now, at
least). But it's very easy to fix and doesn't introduce
particular complexity in this case, so consider it done.

> even if you're not expecting it to make a noticeable
> difference.

Hmm, I do expect best practices to make noticeable
differences, at least for some value of "noticeable".
Otherwise, it becomes cargo-culting, don't you
think?

João



  reply	other threads:[~2019-11-27  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 19:52 Criticism of jit-lock--antiblink-post-command Alan Mackenzie
2019-11-26 20:51 ` Stefan Monnier
2019-11-27  4:45   ` Eli Zaretskii
2019-11-27 13:46     ` Stefan Monnier
2019-11-27 16:10       ` Eli Zaretskii
2019-11-26 21:09 ` João Távora
2019-11-27  5:54   ` Phil Sainty
2019-11-27  9:30     ` João Távora [this message]
2019-11-27 13:38       ` 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

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

  git send-email \
    --in-reply-to='CALDnm51xuq7XVVUQyXcR4FP7iz0wcnmf1YDa=XxSUcX4mqHVfQ@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=psainty@orcon.net.nz \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.