Builder specific configs

[LecrisUT]

Is your feature request related to a problem? Please describe.
When building a standalone man page, I want to include a exclude_patterns so that the html files are not calculated. But I do not see a way to attach specific configs to a specific builder.

Describe the solution you'd like
Have a way to add builder specific options such as a builder_opts or expose a variable similar to tags to interogate which builder is being requested.

Describe alternatives you've considered
I have tried to include one dynamically via

def setup(app):
    if app.builder == "man":
        app.config.exclude_patterns = "**"

but this does not work because app.builder is not available at that point.

[AA-Turner]

@LecrisUT Instead of in setup(), try modifying exclude_patterns in a builder-inited event.

A

[AA-Turner]

On the question of builder-specific overrides / config (new thread), I think it's probably reasonable. I'd want to hear opinions from other contributors, though.

[MrClock8163]

Hi!
I'm not a contributor, but I just now ran into a usecase where this would be extremely handy, so I figured I'd give my two cents.

I'm using the Sphinx-Immaterial theme for a documentation that I want to host on ReadTheDocs.
Long story short, I also want to have the downloadable PDF generated.

The specific issue is, that the theme overwrites admonitions with new functionalities, which is very useful for the web docs, but slightly breaks the latex output. The only way to fix this is to put the following settings in the conf.py:

sphinx_immaterial_override_generic_admonitions = False
sphinx_immaterial_override_builtin_admonitions = False
sphinx_immaterial_override_version_directives = False
sphinx_immaterial_generate_extra_admonitions = False

However, I'd like to only disable these for the latex output, which is currently not possible in any straightforward manner (as far as I know), as the builder format is not available in the tags object.

(It's not feasible to overwrite them in the builder-inited event handler, because the theme already overwrote the definitions by that point, and config-inited doesn't have the builder format yet.)

I realize this is primarily a theme issue, but I feel this is a good argument for why builder specific option support would be good to have. It would certainly help in circumventing problems like this.