# Install ex-vi with Homebrew, MacPorts, pacman

UTF8-friendly version of traditional vi. Version 050325 via Homebrew; verified 2026-06-05. Also installable with macports: sudo port install ex-vi.

## Install

```sh
sudo av install brew:ex-vi
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install ex-vi
```

  Evidence: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install ex-vi
```

  Evidence: MacPorts ports tree: editors/ex-vi/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- pacman (92%):

```sh
sudo pacman -S ex-vi-compat
```

  Evidence: Arch Linux sync databases: ex-vi-compat from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

## Package facts

- **Package key:** brew:ex-vi
- **Package manager:** Homebrew
- **Version:** 050325
- **Source summary:** UTF8-friendly version of traditional vi
- **Homepage:** <https://ex-vi.sourceforge.net/>
- **Last updated:** 2026-06-05T02:30:08+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- vedit (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 050325
## Project history and usage

ex-vi, also known as The Traditional Vi, is a modern Unix port of the original ex/vi editor line, preserving classic vi behavior while adding portability and multibyte character support.

### Project history

The project site frames ex-vi as source code for modern Unix systems. It traces vi back to Bill Joy's work at UCB starting around 1976, and notes that the old source became freely usable after Caldera removed usage restrictions from ancient Unix code under a BSD-style license in January 2002.

The port deliberately preserves traditional vi's small size, terminal control style, and feature set. Its changes focus on modern Unix portability, international character-set support including UTF-8, and selected later System V or POSIX.2 behavior.

### Adoption history

ex-vi is adopted as a preservation-minded package rather than a modern editor platform. Package managers carry it for users who want traditional vi semantics, not Vim-style extensions.

The official page lists release 050325 as current and points adventurous users to a public CVS repository, while warning that CVS may be less tested than release archives.

### How it is used

The vi manual describes vi, view, and vedit as visual-display editors based on ex. vi and ex share the same code, with users able to move between ex command mode and vi visual mode.

The manual documents ~/.exrc as a user configuration file, while the -s script mode explicitly disables EXINIT and .exrc processing.

### Why package nerds care

ex-vi matters to package collectors because it is close to historical Unix vi without the larger feature set of clones such as Vim or nvi. It is a compact compatibility and heritage package.

It is also a useful test case for ports that want a real traditional vi, UTF-8 support, and old ex behavior without bundling a much larger editor.

### Timeline

- 1976: vi development began at UCB, according to the project site.
- 2002: Caldera removed usage restrictions from ancient Unix code under a BSD-style license.
- 2005: Release 050325 was published as the current release listed by the project page.
- 2007: The project page footer records Gunnar Ritter's 2007-11-29 update.

### Related projects

- ex is the line editor base shared with vi in this codebase.
- The project compares itself with vi clones and references the Heirloom Toolchest for CVS build components.

### Sources

- <https://ex-vi.sourceforge.net/>
- <https://ex-vi.sourceforge.net/vi.html>
- <https://ex-vi.sourceforge.net/ex.html>
- <http://ex-vi.cvs.sourceforge.net/ex-vi/ex-vi/>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.exrc
## Other Package-Manager Records

- MacPorts - ex-vi: normalized package name match | MacPorts ports tree: editors/ex-vi/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- pacman - ex-vi-compat - 3-1: installed executable or alias match | Arch Linux sync databases: ex-vi-compat from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | The ex and vi commands based on vim's compatibility modes | https://gitlab.archlinux.org/archlinux/packaging/packages/ex-vi-compat


## Combined YAML source

View the package source record on GitHub. [combined/ex-vi.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ex-vi.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph