paru doesn't seem to be using bat when it can, or isn't using my config?

[ninetailedtori]

Yea, I have confirmed it IS using bat on moor, but I just don't know why it isn't respecting my themes! It's being a little silly :3

...
#
# BINARY OPTIONS
#
[bin]
Makepkg = /usr/bin/makepkg
Pacman = /usr/bin/pacman
Git = /usr/bin/git
Asp = /usr/bin/asp
Bat = /usr/bin/bat
Sudo = sudo
# FileManager = /usr/bin/spf
# MFlags =
# GitFlags =
# GpgFlags =
# BatFlags =
# SudoFlags =
# FileManagerFlags =
# ChrootFlags =
Pager = /usr/bin/bat
# PreBuildCommand =
...

# This is `bat`s configuration file. Each line either contains a comment or
# a command-line option that you want to pass to `bat` by default. You can
# run `bat --help` to get a list of all possible configuration options.

# Specify desired highlighting theme (e.g. "TwoDark"). Run `bat --list-themes`
# for a list of all available themes
--theme-light="Catppuccin Latte"
--theme-dark="Catppuccin Macchiato"
--style=full
--decorations=never
--color=always

# Enable this to use italic text on the terminal. This is not supported on all
# terminal emulators (like tmux, by default):
--italic-text=always

# Uncomment the following line to disable automatic paging:
--paging=auto

# Uncomment the following line if you are using less version >= 551 and want to
# enable mouse scrolling support in `bat` when running inside tmux. This might
# disable text selection, unless you press shift.
# --pager="less -FJKMRSUfi -x4 --modelines=5 --mouse --status-line --use-color"
# --pager="ov"
# --pager="most "
--pager="moor --follow"

# Syntax mappings: map a certain filename pattern to a language.
#   Example 1: use the C++ syntax for Arduino .ino files
#   Example 2: Use ".gitignore"-style highlighting for ".ignore" files
--map-syntax "*.ino:C++"
--map-syntax ".ignore:Git Ignore"

[pfeifferj]

I think this is expected behavior related to how bat's adaptive theme detection works.

when you use --theme-dark and --theme-light in your bat config, bat needs to query your terminal's background color using OSC 11 escape sequences. the query is sent to the terminal and the response is read from stdin.

paru pipes PKGBUILD content to bat's stdin, which means bat cannot receive the terminal's response to the color query. detection fails silently and bat falls back to its default theme.

I verified this on a clean test system by comparing the ANSI color codes:

explicit --theme="Catppuccin Macchiato": 38;5;189, 38;5;116, 38;5;150
default theme: 38;5;231, 38;5;203, 38;5;186
adaptive themes (your config): 38;5;231, 38;5;203, 38;5;186

the adaptive config produces identical output to the default theme, not catppuccin.

if you add this to your paru.conf:

BatFlags = --theme=dark

the --theme=dark option tells bat to skip detection and use whatever you have set in --theme-dark. this way your bat config's theme setting is still respected, but without requiring terminal detection.

alternatively, you can use an explicit theme:

BatFlags = --theme="Catppuccin Macchiato"

[ninetailedtori]

Oohhhh lemme test that, that might be the problem! I'm gonna try both to see what's gonna work best heheh, probably just explicit :3

[ninetailedtori]

Yep, can confirm that's the solution to my problem! Seems paru wasn't allowing bat to detect my theme correctly, and it's to do with how it pipes content, yea. Would it be possible to pipe it direct from paru in order to fix this issue though?

[pfeifferj]

yea it's fixable. paru currently pipes PKGBUILD content to bat's stdin, which blocks the terminal query. the fix would be to write to a tempfile and pass the path instead, but idk if this is a worthwhile tradeoff.

[ninetailedtori]

Yea, that doesn't sound like a worthwhile perf hit ;w; Maybe paru could grab the theme=dark/light from the terminal directly? And then pass that to all the tools it uses?

[mattfbacon]

I don't understand the problem, why can't paru forward any data it receives on its stdin to the pager?