dotling 0.9.0

A dotfiles management CLI — track, link, and sync your config files across machines
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

# dotling status

Show deployment status of all tracked entries.

## Usage

```sh
dotling status [OPTIONS]
```

## Options

| Flag | Description |
|---|---|
| `--diff` | Show inline diffs for modified copy entries |

## Description

`dotling status` displays the current state of each tracked entry, grouped by category. It checks whether each entry is properly deployed, up to date, or has issues.

### Status indicators

| Status | Meaning |
|---|---|
| `Deployed` | Entry is correctly deployed and in sync |
| `Modified` | Entry has local changes that differ from the repo |
| `Missing` | Target file is missing |
| `Broken` | Symlink points to a non-existent target |
| `Conflict` | Both repo and local file have changed |

### Sync badges

| Badge | Meaning |
|---|---|
| `[in sync]` | Repository and target match |
| `[needs sync]` | One side has changed, run `dotling sync` |
| `[diff]` | Content differs (shown with `--diff`) |

### Fingerprints

For copy-mode and encrypted entries, status checks use Blake2s-256 fingerprints stored in `~/.dotling/fingerprints.toml`. This means you can check status without entering your vault password — it's only needed when actual file modifications are required.

## Examples

```sh
# Show status of all entries
dotling status

# Show inline diffs for modified entries
dotling status --diff
```