ec (easy-conflict)

Terminal Git mergetool with a 3-way TUI and Neovim integration

With Lazygit

ec (easy-conflict) is a 3-way terminal native Git merge conflict resolver. Supports diff3 base comparison, and helps you resolve merge conflicts faster without leaving the terminal.

Features

1. 3 pane TUI with ours, result, and theirs
2. Diff3 base view when available via git merge-file
3. No args mode that lists conflicted files and lets you pick one
4. Non interactive modes for CI or scripts
5. Optional backup of the merged file

Installation

Homebrew

brew install ec

Npm

npm install -g @chojs23/ec

Or run without installing:

npx @chojs23/ec

The npm package is a thin installer that downloads the matching prebuilt binary from GitHub Releases at install time. Set EC_SKIP_DOWNLOAD=1 to skip the postinstall download in restricted environments.

Nix

Install the packaged release from nixpkgs:

nix profile add nixpkgs#ec

Run the latest repo state without installing:

nix run github:chojs23/ec

Install the latest repo state into your profile:

nix profile add github:chojs23/ec

The nixpkgs package can lag behind the latest upstream release. Use the direct repo commands above if you want the newest branch or tag immediately.

Install script

You can run the installer through Make:

make install

• On Windows, this runs scripts/install.ps1.
• On Linux/macOS, this runs scripts/install.sh.

Go install

go install github.com/chojs23/ec/cmd/ec@latest

Via curl

curl -fsSL https://raw.githubusercontent.com/chojs23/ec/main/scripts/install.sh | sh

Arch Linux (AUR)

build from source:

pikaur -S easy-conflict

binary:

pikaur -S easy-conflict-bin

Windows

Download a Windows binary from GitHub Releases and add it to your PATH.

PowerShell installer (default: latest release, install to $HOME\\.local\\bin):

irm https://raw.githubusercontent.com/chojs23/ec/main/scripts/install.ps1 | iex

Available release artifacts:

• ec-windows-amd64.exe
• ec-windows-arm64.exe

Build from source

make build

Quick start

Run with no args inside a git repo that has conflicts

ec

Notes

ec does not run git add after you write

Git will still decide whether the merge is resolved based on the file contents

Git mergetool configuration

You can set ec as your git mergetool by adding this to your git config

git config --global merge.tool ec
git config --global mergetool.ec.cmd 'ec "$BASE" "$LOCAL" "$REMOTE" "$MERGED"'
git config --global mergetool.ec.trustExitCode true

Jujutsu merge-editor configuration

You can set ec as your jujutsu merge-editor by adding this to your jujutsu config

jj config set --user ui.merge-editor 'ec'
jj config set --user merge-tools.ec.merge-args '["$base", "$left", "$right", "$output"]'

Usage

Interactive

ec <BASE> <LOCAL> <REMOTE> <MERGED>
ec --base <path> --local <path> --remote <path> --merged <path>

No args mode

ec

Non interactive

ec --check --merged <path>
ec --apply-all ours --base <path> --local <path> --remote <path> --merged <path>

Neovim plugin (terminal buffer)

This repo includes a minimal Neovim plugin that opens ec in a terminal buffer.

Install with your plugin manager and ensure ec is on your PATH.

Minimal config

require("ec").setup()

Using lazy.nvim

{
  "chojs23/ec",
  keys = {
    { "<leader>gr", ":Ec<CR>", desc = "Open ec" },
  },
}

{
  cmd = "ec",
  open_cmd = "tabnew",
  cwd = nil,
  float = true,
  close_on_exit = true,
}

{
  width = 0.92,
  height = 0.86,
  border = "rounded",
  title = "ec",
  title_pos = "center",
  zindex = 50,
}

Commands

:Ec
:Ec --base <path> --local <path> --remote <path> --merged <path>

Resolver screen

The resolver shows three panes in one view.

Conflicts are shown as focused blocks. The center pane is the output that will be written to the merged file.

You can move between conflicts, choose a side, and apply it. The status line shows which conflict you are on and whether it is resolved.

Use e to open $EDITOR with the current result. When you exit the editor, the resolver reloads the merged file and keeps manual edits.

Blue: modified lines (changed vs base)

Green: added lines

Red: conflicted lines where both sides differ

Key bindings

Keybindings are vim-like by default.

Navigation

• n / p: next and previous conflict
• gg / G: jump to top / bottom
• zz: recenter on selected hunk start
• j / k / up / down: vertical scroll
• ctrl+u / ctrl+d: half-page up / down
• H / L / left / right: horizontal scroll

Selection and apply

• h / l: select ours or theirs
• a / space: accept selection
• o / t / b / x: apply ours, theirs, both, or none
• d: discard selection
• O / T: apply ours or theirs to all

Other

• u: undo
• ctrl+r: redo
• e: open $EDITOR with current result
• w / ctrl+s: write file without quitting
• q: back to selector or quit

Theme configuration

The TUI can load colors from a theme config file.

Config path:

$XDG_CONFIG_HOME/ec/themes.json (when XDG_CONFIG_HOME is set)

If XDG_CONFIG_HOME is not set, ec uses os.UserConfigDir()/ec/themes.json. Typical defaults are ~/.config/ec/themes.json on Linux, ~/Library/Application Support/ec/themes.json on macOS, and %AppData%\ec\themes.json on Windows.

Example:

{
  "default": "warm",
  "themes": {
    "warm": {
      "header_bg": "94",
      "header_fg": "230",
      "added_bg": "58",
      "conflicted_bg": "88",
      "result_fg": "#f1f1f1",
      "modified_bg": "#2f5f7a"
    }
  }
}

Missing keys fall back to the built-in defaults.

Hex colors require a TrueColor-capable terminal to avoid 256-color downsampling.

Supported keys: title_fg, pane_border, selected_pane_border, side_pane_border, selected_side_border, header_bg, header_fg, footer_bg, footer_fg, line_number, ours_highlight_bg, ours_highlight_fg, theirs_highlight_bg, theirs_highlight_fg, result_fg, result_highlight_bg, result_highlight_fg, modified_bg, modified_fg, added_bg, added_fg, removed_bg, removed_fg, conflicted_bg, conflicted_fg, insert_marker_fg, selected_hunk_marker_fg, selected_hunk_marker_bg, selected_hunk_bg, status_resolved_fg, status_unresolved_fg, result_resolved_marker_fg, result_resolved_border, result_unresolved_border, toast_bg, toast_fg, selector_resolved_fg, selector_unresolved_fg, dim_foreground_light, dim_foreground_dark, dim_foreground_muted.

Backup behavior

Backups are off by default. Use --backup to write a sibling file named .ec.bak before writing the result.

Base view behavior

Base chunks come from git merge-file --diff3 output. If the base stage is missing for a file, the tool continues without a base view and prints a warning.

Contributing

New features and bug reports are welcome.

Feel free to open an issue or a pull request.

License

MIT