HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
martanne
vis
C2014–2026
martanne / vis

vis

A vi-like editor based on Plan 9's structural regular expressions

56Distinct people
92Mentions
4Explicit recommenders
5.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A vi-like editor based on Plan 9's structural regular expressions

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Regarding code elegance, OpenBSD[0] surely pride themselves in their code correctness and how they make it clean and understandable. Another example might be my favorite text…

Gualdrapo used a recommendation phrase. 4 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year92 dated mentions

Observed mentions: 2014-11-20 16:13:57 UTC to 2026-08-20 16:08:59 UTC.

051015202014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 20 mentions; 3 submissions, 17 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC918
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC20317
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC12210
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC413
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC927
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC808
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC707
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC808
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC514
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC211
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC505

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Vis - Combining Modal Editing with Structural Regular Expressions Vis aims to be a modern, legacy-free, simple yet efficient editor, combining the strengths of both vi(m) and sam. It extends vi's modal editing with built-in support for multiple cursors/selections and combines it with sam's structural regular expression based command language. A universal editor, it has decent Unicode support and should cope with arbitrary files, including large, binary or single-line ones. Efficient syntax highlighting is provided using Parsing Expression Grammars, which can be conveniently expressed using Lua in the form of LPeg. The editor core is written in a reasonable amount of clean (your mileage may vary), modern and legacy-free C code, enabling it to run in resource-constrained environments. The implementation should be easy to hack on and encourages experimentation. There is also a Lua API for in-process extensions. Vis strives to be simple and focuses on its core task: efficient text management. Clipboard and digraph handling as well as a fuzzy file open dialog are all provided by independent utilities. There exist plans to use a client/server architecture, delegating window management to your windowing system or favorite terminal multiplexer. The intention is not to be bug-for-bug compatible with vi(m). Instead, we aim to provide more powerful editing features based on an elegant design and clean implementation. Build instructions In order to build vis you will need a C99 compiler, a POSIX.1-2008 compatible environment as well as: curses (recommended) Lua >= 5.2 (optional) LPeg >= 0.12 (optional runtime dependency required for syntax highlighting) TRE (optional for more memory efficient regex search) Assuming these dependencies are met, execute: $ ./configure && make && sudo make install By default the configure script will try to auto detect support for Lua using pkg-config(1). See configure --help for a list of supported options. You can also manually tweak the generated config.mk file. Or simply use one of the distribution provided packages. Documentation End user documentation can be found in the vis(1) manual page and the Wiki. Read the FAQ for common questions. Learn about some differences compared to sam(1) and vim(1), respectively. C API as well as Lua API documentation is also available. Non Goals Some features which will not be implemented: tabs / multiple workspaces / advanced window management file and directory browser support for file archives (tar, zip, ...) support for network protocols (ftp, http, ssh ...) encryption compression GUIs (neither x11, motif, gtk, win32 ...) although the codebase should make it easy to add them VimL right-to-left text ex mode, we have more elegant structural regexp diff mode vimgrep internal spell checker lots of compile time configurable features / #ifdef mess How to help? There are plenty of ways to contribute, below are a few ideas: Artwork Color Themes Homepage? Documentation Manual Pages Improve :help output Lua API Documentation and Examples Unit Tests Plugin Development API Design Testing Infrastructure Distribution Packaging Core Editor Design Checkout the Developer Overview to get started and do not hesitate to ask question in the #vis-editor IRC channel on libera (join via your browser).
Read the full README on GitHub

What Hacker News says

92 sources
I don't think there is a client that will let me connect to 9front from Android, is there? I see what you mean in this and the other comment. With 9front, you rely less on issuing commands to remote machines because you can directly access their resources. It's worth keeping in mind when comparing Plan 9 and Unix from a Unix user's perspective. Being able to pick large fonts on the server isn't the same as leaving the fonts up to the client. When I use terminal emulators, SSH, and tmux, I can switch between different clients with different resolution, pixel density, and screen orientation and have the text display acceptably on each (minus text reflow for history, which is an issue). > I consider the Sam regular expresions far more powerful than the vi keys themselves. I agree, structural regular expressions seem like a better version of
Read the rest
vi commands. It was reasonably easy to make some complex edits in https://github.com/martanne/vis when I tried it, and it felt like I'd only scratched the surface. I could see myself still using vis if it had tabs like Vim. (Tabs are a stated non-goal for vis.)
In Terminals should generate the 256-color palette
People should be aware of two related editors: https://anvil-editor.net/ is more directly inspired by and similar to Acme (but makes no attempt to borrow from Vim). https://github.com/martanne/vis is a minimalist editor that stays close to Vim but adds Sam-style regular extensions and multi-cursor editing (but not Acme-style "execute anything on screen"). For example, you can select all instances of a regex and edit them all at once afterwards interactively.
In Ad: An Adaptable Text Editor
Another editor that people might be interested in (and I think more people should know about) is https://github.com/martanne/vis. It is, in some ways, the opposite of Ki; instead of straying further from vim, Vis is just Vim + good multiple cursor support + sam-styled structural regexes (I didn't know what those are before using Vis, I consider it a detail of how the multiple cursor interface works). Thus, Vis is easier to learn than Helix/Kakoune and gives you (IMO) the most useful feature of Helix/Kakoune. Unfortunately, Vis is also a bit bare-bones, I don't think it has LSP support for instance.
In Show HN: Ki Editor – Multicursor syntactical editor
I've added links to the below quote: >"oasis uses smaller and simpler implementations of libraries and tools whenever possible: musl instead of glibc (https://www.musl-libc.org/) sbase instead of coreutils (https://git.suckless.org/sbase/file/README.html) ubase instead of util-linux (https://git.suckless.org/ubase/file/README.html) pigz instead of gzip (https://zlib.net/pigz/) mandoc instead of man-db (https://mandoc.bsd.lv/) bearssl instead of openssl (https://bearssl.org/) oksh instead of bash (https://github.com/ibara/oksh) sdhcp instead of dhclient or dhcpcd (https://core.suckless.org/sdhcp/) vis instead of vim or emacs (https://github.com/martanne/vis) byacc instead of bison (https://invisible-island.net/byacc/) perp and sinit instead of sysvinit or system 44 (http://b0llix.net/perp/ https://github.com/wereHamster/perp https://troubl
Read the rest
eshooters.com/linux/diy/suckless_init_on_plop....) netsurf instead of chromium or firefox (https://www.netsurf-browser.org/) samurai instead of ninja (https://github.com/michaelforney/samurai) velox instead of Xorg (https://github.com/michaelforney/velox) netbsd-curses instead of ncurses (https://github.com/sabotage-linux/netbsd-curses)" (Oh, and not to quote Dwayne "The Rock" Johnson's character "Maui" from Disney's Moana or anything -- but "You're welcome!" <g> :-) <g>)
In Oasis – a small, statically-linked Linux system
I am kind of in the same situation as you - I am no consumated developer whatsoever but happen to be a graphic designer who likes to fiddle with some code and terminal stuff. I've been typesetting stuff with ConTeXt[0], from letters to books to my invoices with ConTeXt + LuaTeX. Some examples at [1]. Nowadays I use vis[2] to do that. [0] https://en.wikipedia.org/wiki/ConTeXt [1] https://imgur.com/a/HEzh1x5 [2] https://github.com/martanne/vis
In Ask HN: Best tools for self-authoring books in 2023?

Showing the 15 most recent of 92 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.