Latest version of watch (4.0.5) has the precise parameter defaulting to on for Arm MacOS systems

[zestysoft]

Output of brew config

HOMEBREW_VERSION: 4.4.16
ORIGIN: https://github.com/Homebrew/brew
HEAD: 4c9de7d31c6d9e67c4496c3c156e84c3649fec4c
Last commit: 7 days ago
Branch: stable
Core tap JSON: 20 Jan 04:27 UTC
Core cask tap JSON: 20 Jan 04:27 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.1OZwXvcJ6I/org.xquartz:0
HOMEBREW_MAKE_JOBS: 16
Homebrew Ruby: 3.3.6 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.6/bin/ruby
CPU: 16-core 64-bit arm_palma
Clang: 16.0.0 build 1600
Git: 2.48.1 => /opt/homebrew/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.2-arm64
CLT: 16.2.0.0.1.1733547573
Xcode: 16.2
Rosetta 2: false

Output of brew doctor

Your system is ready to brew.

Description of issue

When using watch the output I normally only see when using '-p' is on by default now.
Reverting to 4.0.4 restores default behavior.

[gromgit]

Going by the title of your issue:

Latest version of watch (4.0.5) has the precise parameter defaulting to on for Arm MacOS systems

I'm unable to replicate. With the following script:

#!/bin/sh
echo `date` Sleeping 5 seconds
sleep 5
echo `date` DONE

and this invocation on an M2 MacBook Air:

watch ./test.sh

the timestamps on the script's output clearly indicate a pause of 2 seconds (the default) between invocations, while:

watch -p ./test.sh

outputs timestamps that indicate an immediate re-invocation after exit. Both of these observations are consistent with precise mode not being active.

Your description also doesn't indicate exactly what you're seeing for either watch version concerned, so you should probably elaborate.

[zestysoft]

Sorry, apparently that parameter isn't what causes the binary to display the extra information. With 4.0.4, this is what I usually see:

watch echo hi

with 4.0.5 , the date/time changes and there's the additional "in 0.05s (0)" bit:
watch echo hi

Normally I wouldn't care at all about something small like this, but since the values constantly change (which can have different length digits), it continually catches my eye as something to address.

[gromgit]

Informational displays like this can change at the whim of the upstream developer, and in any case doesn't look like anything actionable from the Homebrew side.