Croft – VS Code inspired terminal user interface text editor
Croft – VS Code inspired terminal user interface text editor
OK, c'est futile, ça n'a probablement aucun intérêt sauf pour les quelques geeks qui aiment changer d'herbage, mais je me suis (re)mis à #helix, l'éditeur de texte (modal) qui serait presque comme (n)vim, mais avec une logique légèrement décalée (selection puis action, pas l'inverse).
Bah c'est bien. Pas besoin de trouze mille plugins, les LSP marchent direct, l'interface est clean ; mention spéciale pour les "pickers", ultra-efficaces.
Ex muss nicht immer Microsoft sein: Nextpad++ ist Notepad++ für den Mac
Es tut sich etwas auf dem Gebiet der Visual-Studio-Code-Alternativen, auch für den Mac. Hatte ich vor zwei Monaten hier schon den CotEditor als Mac-Alternative zu Microsofts Boliden vorgestellt, und im letzten Monat Zed, den plattformübergreifenden Editor, der zum Angriff auf Visual Studio Code bläst, so stelle ich heute die freie Mac-Applikation Nextpad++ vor. https://kantel.github.io/posts/2026061801_nextpadplusplus/ #Nextpad #Texteditor #Mac #Markdown
¿Vim o Neovim? 🖥️
Vim es el clásico inmortal: ultraestable, ligero y preinstalado en casi cualquier servidor Linux. Ideal para edición rápida en producción.
Neovim es el futuro moderno: un fork optimizado que añade ejecución asíncrona, soporte nativo para Lua (configuraciones más rápidas) y un ecosistema de plugins brutal gracias a su LSP integrado.
Vim para emergencias en el servidor; Neovim para desarrollo diario. 💻
The Story of vi
“I’m still using vi because I can’t escape it."
vi was created in 1976 by Bill Joy while he was a graduate student at UC Berkeley. At the time most people used line based editors like ed and ex. These editors were powerful but difficult to use because you could not see the surrounding text while editing. Bill Joy wanted a full screen visual editor that would let users move around and edit interactively.
He originally wrote vi as a visual mode for the ex editor rather than as a completely separate program. When people type vi on many systems today they are actually running ex in visual mode. His goal was to make text editing faster and more intuitive on the hardware available at the time.
One important detail is the terminal Bill Joy used while developing vi. He worked on a Lear Siegler ADM 3A terminal. This keyboard had the Escape key where the Tab key is located on modern keyboards and it had no arrow keys. Because of this layout Bill Joy designed vi to rely heavily on the Escape key and the hjkl keys for movement. These design choices are still used in vi and vim today.
vi quickly became popular because it was fast and worked well over slow network connections. vi became the standard text editor on almost every Unix and Linux system. System administrators and developers learned it because it was almost always available.
vi also played a major role in starting one of the longest running debates in computing history known as the editor wars between vi and Emacs. vi users generally value speed and staying on the home row while Emacs users value its high level of customization. This rivalry has continued for decades.
Although the original vi is quite old its influence remains strong. Even today if you log into a minimal Linux server vi or vim is often the only text editor available by default.
#OpenSourceHistory #ComputingHistory #vi #vim #TechHistory #TextEditor #EditorWars #UnixHistory #linux
Emacs features have a discoverability problem, and we’re chipping away at it one demo at a time. The years since I wrote the last one of these have yielded more surprising and useful finds, so it’s time again for a “batteries included” report. Note This is the third in a series of articles highlighting useful but lesser-known features included in Emacs. Parts 1 & 2: Batteries included with Emacs More batteries included with emacs “Lesser-known” is a subjective judgment.
Vim Classic, a fork of Vim, has released its first version. It's designed for users who want to avoid AI integration in their text editor. A clear stance for those prioritizing a pure, AI-free coding environment.