Skip to content

cabal got annoyingly chatty #10885

Open
@Bodigrim

Description

@Bodigrim

Switch to any package with cabal.project and execute

$ cabal-3.14.1.1-p1 --semaphore build
...does some work...
$ cabal-3.14.1.1-p1 --semaphore build
Configuration is affected by the following files:
- cabal.project
Up to date
Created semaphore called cabal_semaphore_1 with 8 slots.

That's awful lot of lines to tell me that there is nothing to do. Older versions of cabal used to report briefly Up to date, which is much better. Could the default log level of Configuration is affected by... and Created semaphore... be adjusted please?

I mean, I definitely do not need to be reminded every single time that there is cabal.project in my folder. And it gets even worse if there is more than one *.project file. This is a valuable information to display at some verbosity level, but definitely not by default.

As for semaphores, I don't even see how one can act upon this message. Could it be relegated to -v3 only? Seeing it every time I run any Cabal command is mildly infuriating.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions