.ie \n(.g .ds Aq \(aq
.el .ds Aq '
.TH jj-config-list 1  "list " 
.SH NAME
jj\-config\-list \- List variables set in config files, along with their values
.SH SYNOPSIS
\fBjj config list\fR [\fB\-\-include\-defaults\fR] [\fB\-R\fR|\fB\-\-repository\fR] [\fB\-\-ignore\-working\-copy\fR] [\fB\-\-include\-overridden\fR] [\fB\-\-no\-integrate\-operation\fR] [\fB\-\-user\fR] [\fB\-\-ignore\-immutable\fR] [\fB\-\-repo\fR] [\fB\-\-at\-operation\fR] [\fB\-\-workspace\fR] [\fB\-\-debug\fR] [\fB\-T\fR|\fB\-\-template\fR] [\fB\-\-color\fR] [\fB\-\-quiet\fR] [\fB\-\-no\-pager\fR] [\fB\-\-config\fR] [\fB\-\-config\-file\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fINAME\fR] 
.SH DESCRIPTION
List variables set in config files, along with their values
.SH OPTIONS
.TP
\fB\-\-include\-defaults\fR
Whether to explicitly include built\-in default values in the list
.TP
\fB\-\-include\-overridden\fR
Allow printing overridden values
.TP
\fB\-\-user\fR
Target the user\-level config
.TP
\fB\-\-repo\fR
Target the repo\-level config
.TP
\fB\-\-workspace\fR
Target the workspace\-level config
.TP
\fB\-T\fR, \fB\-\-template\fR \fI<TEMPLATE>\fR
Render each variable using the given template

The following keywords are available in the template expression:

* `name: String`: Config name, in [TOML\*(Aqs "dotted key" format].
* `value: ConfigValue`: Value to be formatted in TOML syntax.
* `overridden: Boolean`: True if the value is shadowed by other.
* `source: String`: Source of the value.
* `path: Option<FsPath>`: Path to the config file.

Can be overridden by the `templates.config_list` setting. To
see a detailed config list, use the `builtin_config_list_detailed`
template.

See [`jj help \-k templates`] for more information.

[TOML\*(Aqs "dotted key" format]: https://toml.io/en/v1.0.0#keys

[`jj help \-k templates`]:
    https://docs.jj\-vcs.dev/latest/templates/
.TP
\fB\-h\fR, \fB\-\-help\fR
Print help (see a summary with \*(Aq\-h\*(Aq)
.TP
[\fINAME\fR]
An optional name of a specific config option to look up
.SH "GLOBAL OPTIONS"
.TP
\fB\-R\fR, \fB\-\-repository\fR \fI<REPOSITORY>\fR
Path to repository to operate on

By default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory.
.TP
\fB\-\-ignore\-working\-copy\fR
Don\*(Aqt snapshot the working copy, and don\*(Aqt update it

By default, Jujutsu snapshots the working copy at the beginning of every command. The working copy is also updated at the end of the command, if the command modified the working\-copy commit (`@`). If you want to avoid snapshotting the working copy and instead see a possibly stale working\-copy commit, you can use `\-\-ignore\-working\-copy`. This may be useful e.g. in a command prompt, especially if you have another process that commits the working copy.

Loading the repository at a specific operation with `\-\-at\-operation` implies `\-\-ignore\-working\-copy`.
.TP
\fB\-\-no\-integrate\-operation\fR
Run the command as usual but don\*(Aqt integrate any operations

When this option is given, the operations will still be created as usual but they will not be integrated to the operation log. The working copy will also not be updated.

The command will print the resulting operation ID. You can pass that to e.g. `jj \-\-at\-op` to inspect the resulting repo state, or you can pass it to `jj op restore` to restore the repo to that state. You can also pass the ID to `jj op integrate` to integrate the operation.

Note that this does *not* prevent side effects outside the repo. For example, `jj git push \-\-no\-integrate\-operation` will still perform the push.
.TP
\fB\-\-ignore\-immutable\fR
Allow rewriting immutable commits

By default, Jujutsu prevents rewriting commits in the configured set of immutable commits. This option disables that check and lets you rewrite any commit but the root commit.

This option only affects the check. It does not affect the `immutable_heads()` revset or the `immutable` template keyword.
.TP
\fB\-\-at\-operation\fR \fI<AT_OPERATION>\fR
Operation to load the repo at

Operation to load the repo at. By default, Jujutsu loads the repo at the most recent operation, or at the merge of the divergent operations if any.

You can use `\-\-at\-op=<operation ID>` to see what the repo looked like at an earlier operation. For example `jj \-\-at\-op=<operation ID> st` will show you what `jj st` would have shown you when the given operation had just finished. `\-\-at\-op=@` is pretty much the same as the default except that divergent operations will never be merged.

Use `jj op log` to find the operation ID you want. Any unambiguous prefix of the operation ID is enough.

When loading the repo at an earlier operation, the working copy will be ignored, as if `\-\-ignore\-working\-copy` had been specified.

It is possible to run mutating commands when loading the repo at an earlier operation. Doing that is equivalent to having run concurrent commands starting at the earlier operation. There\*(Aqs rarely a reason to do that, but it is possible.
.TP
\fB\-\-debug\fR
Enable debug logging
.TP
\fB\-\-color\fR \fI<WHEN>\fR
When to colorize output
.br

.br
\fIPossible values:\fR
.RS 14
.IP \(bu 2
always
.IP \(bu 2
never
.IP \(bu 2
debug
.IP \(bu 2
auto
.RE
.TP
\fB\-\-quiet\fR
Silence non\-primary command output

For example, `jj file list` will still list files, but it won\*(Aqt tell you if the working copy was snapshotted or if descendants were rebased.

Warnings and errors will still be printed.
.TP
\fB\-\-no\-pager\fR
Disable the pager
.TP
\fB\-\-config\fR \fI<NAME=VALUE>\fR
Additional configuration options (can be repeated)

The name should be specified as TOML dotted keys. The value should be specified as a TOML expression. If string value isn\*(Aqt enclosed by any TOML constructs (such as array notation), quotes can be omitted.
.TP
\fB\-\-config\-file\fR \fI<PATH>\fR
Additional configuration files (can be repeated)