unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Obsolete variable in cc-defs.el
Date: Tue, 18 Oct 2022 09:30:47 +0000	[thread overview]
Message-ID: <Y05yR4pL+NX4PxmY@ACM> (raw)
In-Reply-To: <jwvtu42azdy.fsf-monnier+emacs@gnu.org>

Hello, Stefan.

On Mon, Oct 17, 2022 at 17:59:13 -0400, Stefan Monnier wrote:
> > That is a mistake in declaring inhibit-point-motion-hooks obsolete.  As
> > long as the properties point_entered and point_left exist and work
> > (regardless of whether they are declared obsolete),
> > inhibit-point-motion-hooks is required.  It's use shouldn't (yet)
> > generate any warnings.

> BTW, your code only uses `inhibit-point-motion-hooks` explicitly in
> Emacs<23.2.  After that it relies on
> `with-silent-modifications` instead.  So the byte-compile obsolescence
> warning only comes from

>     (cc-bytecomp-defvar inhibit-point-motion-hooks)

> which your code can't need when `with-silent-modifications` is `fboundp`.

Indeed.  Which is ironic, given that cc-bytecomp-defvar was invented to
_suppress_ compiler warnings.

I still say a binding of inhibit-point-motion-hooks should be in
with-silent-modifications, although it's not a big thing.  Surely the
intangible text property will "soon" be removed, making the point moot.

>         Stefan

-- 
Alan Mackenzie (Nuremberg, Germany).



      reply	other threads:[~2022-10-18  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  8:59 Obsolete variable in cc-defs.el Lars Ingebrigtsen
2022-10-17 16:53 ` Alan Mackenzie
2022-10-17 21:54   ` Stefan Monnier
2022-10-18  8:26     ` Alan Mackenzie
2022-10-17 21:59   ` Stefan Monnier
2022-10-18  9:30     ` Alan Mackenzie [this message]

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=Y05yR4pL+NX4PxmY@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).