Automic VaultAutomic Vault

brew

le mit Homebrew, apt, MacPorts installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install le

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install le

MacPorts ports tree · editors/le/Portfile · Quelle: api.github.com

Linux

Debian aptverifiziert · 92%
sudo apt install le

Debian stable package indexes · le · Quelle: deb.debian.org

Überblick

Paketzusammenfassung

Text editor with block and binary operations

Befehle und Aliase

  • le

Verlauf

Projektgeschichte und Nutzung

LE is Alexander V. Lukyanov's terminal text editor, notable for block operations, binary-safe editing, hex mode, mmap-based large-file/device editing, syntax highlighting, and configurable keymaps and colors.

Projektgeschichte

The upstream HISTORY file says Lukyanov started LE in 1993 as first-year laboratory work at Yaroslavl State University while using a BESTA Unix machine with 8 MB of memory and fourteen terminals. The first version could load, browse, insert, delete, and save files.

After that first version, the editor was almost completely rewritten in C++. Lukyanov published it under the GPL in early 1997 after deciding it had become powerful enough to share. The NEWS file marks version 1.2.0 as the first public release.

LE's development history is a long record of terminal-editor pragmatism: regular-expression search, tunable syntax highlighting, rectangular blocks, mmap editing for large files and devices, mouse support, multibyte/UTF-8 support, full undo/redo, many syntax definitions, ncurses portability fixes, and build fixes for Unix-like systems.

Adoptionsgeschichte

LE never became a mainstream editor on the scale of vi, Emacs, nano, or joe, but it persisted in Unix package collections because it occupies a useful niche: a small terminal editor with Norton Editor-like ergonomics plus block, binary, and hex-oriented features.

Package availability in Homebrew, Debian, Ubuntu, and MacPorts shows the usual long-tail survival path for mature terminal tools: stable enough to keep packaging, specialized enough that users seek it by name.

Wie es verwendet wird

LE is used as an interactive terminal editor for text files, DOS/Unix line-ending files, binary-clean editing, hexadecimal viewing/editing, syntax-highlighted source/config editing, rectangular and stream block operations, and cautious mmap replace-mode edits of large files or devices.

Its configuration model is file-based and terminal-oriented: syntax rules can live in package data, ~/.le/syntax, or ./.le.syntax; keymaps and colors can be dumped and customized in ~/.le or package data locations.

Warum Paket-Nerds sich dafür interessieren

LE is significant as a survivor from the 1990s Unix editor ecology. It is small, C++/ncurses-based, GPL-licensed, and full of features that matter to terminal users who edit awkward files: rectangular blocks, binary mode, hex mode, mmap editing, and configurable keymaps.

For package maintainers, LE is a good example of a stable but actively patched classic utility whose changelog is dominated by portability, terminal behavior, syntax updates, and correctness fixes rather than product churn.

Zeitleiste

  • 1993: Alexander V. Lukyanov starts LE as student laboratory work on a BESTA Unix machine.
  • Early 1997: LE is published under the GPL after a substantial C++ rewrite.
  • Version 1.2.0: NEWS marks the first public release.
  • 2001: Version 1.9.0 adds bookmark support and syntax improvements.
  • 2004: Version 1.10.0 adds multibyte encoding support; version 1.11.0 adds full undo/redo.
  • 2010: Version 1.14.5 changes licensing to GNU GPL v3 because regex.c already used it.
  • 2015: Version 1.16.0 integrates the default menu and improves keymap implementation.
  • 2021: Version 1.16.8 records macOS build changes, performance optimizations, and syntax improvements.

Related projects

  • Related editor traditions include vi, Emacs, Norton Editor, Turbo C's file selector style, ncurses-based terminal editors, and hex/binary editors.

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

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
lecliglobales 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-Version1.16.7
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/lavv17/le

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz
  • InfoNo cached GitHub release or tag data was available.https://github.com/lavv17/lenone Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:le
Version1.16.7
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/le
Homepagehttps://github.com/lavv17/le
Repositoryhttps://github.com/lavv17/le
Upstream-Dokumentationhttps://github.com/lavv17/le#readme
LizenzGPL-3.0-or-later AND GPL-2.0-or-later
Quellarchivhttps://github.com/lavv17/le/releases/download/v1.16.7/le-1.16.7.tar.gz
Von macOS bereitgestellte Bibliothekenncurses
Bottleverfügbar (auf arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, 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 Namele
Version Scheme0
Revision0
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.

Debian apt95%

le 1.16.8-1

Text editor with block and binary operations

http://lav.yar.ru/programs.html

sudo apt install le
  • Section: editors
  • Architecture: amd64
  • 4 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Le
Debian stable package indexes · deb.debian.org · Debian stable package indexes: le from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Ubuntu apt95%

le 1.16.8-0.1

Text editor with block and binary operations

http://lav.yar.ru/programs.html

sudo apt install le
  • Section: universe/editors
  • Architecture: amd64
  • 4 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Le
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: le from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz
MacPorts95%

le

sudo port install le
  • normalized package name match
  • Abgeglichen nach: Le
MacPorts ports tree · api.github.com · MacPorts ports tree: editors/le/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.

Combined YAML source

View the package source record on GitHub.

combined/le.yml

Verwendete Quellen

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