From: Robert Pluim <rpluim@gmail.com>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: "emacs-devel" <emacs-devel@gnu.org>, Juri Linkov <juri@linkov.net>
Subject: Re: New unwind-protect byte-compiler warning
Date: Tue, 04 Apr 2023 12:32:37 +0200 [thread overview]
Message-ID: <87fs9ghr96.fsf@gmail.com> (raw)
In-Reply-To: <0106E951-59EB-42C9-8F99-4182F56C6311@gmail.com> ("Mattias Engdegård"'s message of "Thu, 30 Mar 2023 10:01:42 +0200")
>>>>> On Thu, 30 Mar 2023 10:01:42 +0200, Mattias Engdegård <mattias.engdegard@gmail.com> said:
Mattias> On master, the byte-compiler now warns about `unwind-protect` forms lacking actual unwinding code, which is very often a mistake. An Emacs build currently yields about 30 warnings of this kind.
Mattias> I'm mostly going to wait for those with good knowledge about the code causing each warning to deal with it. Tell me if I can be of further help. There's no strong urgency.
Mattias> This will eventually leave some warnings claimed by no-one for me to take on, which will be done in a conservative way, maybe after a week.
This one:
In mouse-wheel-global-text-scale:
mwheel.el:450:6: Warning: ‘unwind-protect’ without unwind forms
is because weʼre protecting against errors from
`global-text-scale-adjust', but unlike `text-scale-{in,de}crease',
that doesnʼt signal an error when you reach the scale limit.
Juri, we can add an unwind form of `t', or switch it to
`condition-case', whichever you prefer (Iʼm assuming perhaps
pessimistically that `global-text-scale-adjust' might signal in
future).
Robert
--
next prev parent reply other threads:[~2023-04-04 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 8:01 New unwind-protect byte-compiler warning Mattias Engdegård
2023-03-30 10:08 ` Emanuel Berg
2023-04-01 22:56 ` Basil L. Contovounesios
2023-04-04 10:32 ` Robert Pluim [this message]
2023-04-04 11:20 ` Mattias Engdegård
2023-04-04 12:26 ` Robert Pluim
2023-04-04 12:32 ` Gregory Heytings
2023-04-04 16:10 ` Juri Linkov
2023-04-07 17:40 ` Mattias Engdegård
2023-04-09 14:20 ` Michael Albinus
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=87fs9ghr96.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=mattias.engdegard@gmail.com \
/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.