You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's expected that installing bat would use bat for scoop cat, but it doesn't. Instead, you need to explicitly set scoop config cat_style to enable this.
Additional context/output
This is confusing, as scoop help shows:
cat Show content of specified manifest. If available, ``bat`` will be used to pretty-print the JSON.
it should instead state that if configured, bat will be used, e.g. use scoop config cat_style plain, or perhaps it should use bat by default, if installed.
We planned to enable bat by default, just as aria2 does. But using bat means more time to show the content, and change the default behavior. Maybe the info hasn't been changed.
Bug Report
Current Behavior
This is a follow up to bug #4905
Expected Behavior
It's expected that installing
bat
would usebat
forscoop cat
, but it doesn't. Instead, you need to explicitly set scoop config cat_style to enable this.Additional context/output
This is confusing, as scoop help shows:
cat Show content of specified manifest. If available, ``bat`` will be used to pretty-print the JSON.
it should instead state that if configured, bat will be used, e.g. use
scoop config cat_style plain
, or perhaps it should use bat by default, if installed.Possible Solution
@niheaven says:
We planned to enable bat by default, just as aria2 does. But using bat means more time to show the content, and change the default behavior. Maybe the info hasn't been changed.
System details
Windows 11, 64-bit, PS 7.2.6, Windows Terminal
Scoop Configuration
The text was updated successfully, but these errors were encountered: