Automic VaultAutomic Vault

brew

ex-vi mit Homebrew, MacPorts, pacman installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für ex-vi in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install ex-vi

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install ex-vi

MacPorts ports tree · editors/ex-vi/Portfile · Quelle: api.github.com

Überblick

Paketzusammenfassung

UTF8-friendly version of traditional vi

Befehle und Aliase

  • vedit

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 10 Plattformziele verfügbar.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

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

Config paths the tool may read or write during local use.

Unix
~/.exrc

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
veditcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version050325
Manager aktualisiert2026-06-05
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://ex-vi.sourceforge.net/

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:ex-vi
Version050325
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/ex-vi
Homepagehttps://ex-vi.sourceforge.net/
Repositoryhttps://ex-vi.cvs.sourceforge.net/ex-vi
Upstream-Dokumentationhttps://ex-vi.sourceforge.net/
LizenzBSD-4-Clause AND BSD-4-Clause-UC
Quellarchivhttps://downloads.sourceforge.net/project/ex-vi/ex-vi/050325/ex-050325.tar.bz2
Zuletzt aktualisiert2026-06-05T02:30:08+02:00
Pulseupdated
Von macOS bereitgestellte Bibliothekenncurses
Bottleverfügbar (auf arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameex-vi
Version Scheme0
Revision0
Conflicts With
  • macvim
  • vim
  • vim-classic
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

MacPorts95%

ex-vi

sudo port install ex-vi
  • normalized package name match
  • Abgeglichen nach: Ex Vi
MacPorts ports tree · api.github.com · MacPorts ports tree: editors/ex-vi/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment