micro-editor
vis
Our great sponsors
micro-editor | vis | |
---|---|---|
226 | 56 | |
23,740 | 4,147 | |
- | - | |
8.9 | 8.1 | |
5 days ago | 1 day ago | |
Go | C | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
micro-editor
- Modeless Vim
-
Essential Command Line Tools for Developers
To see more screenshots of micro, showcasing some of the default color schemes, see here.
View on GitHub
-
Go: What We Got Right, What We Got Wrong
Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:
- gdu: a NCDU clone, much faster on SSD mounts [1]
- duf: a `df` clone with a nicer interface [2]
- massren: a `vidir` clone (simpler to use but with fewer options) [3]
- gotop: a `top` clone [4]
- micro: a nice TUI editor [5]
Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.
[1]: https://github.com/dundee/gdu
[2]: https://github.com/muesli/duf
[3]: https://github.com/laurent22/massren
-
Text Editor: Data Structures
> The worst way to store and manipulate text is to use an array.
Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.
Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.
Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).
[1] https://github.com/zyedidia/micro
[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...
- A nano like text editor built with pure C
-
A simple guide for configuring sudo and doas
There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:
-
what terminal emulator do you use and why?
found that micro has dedicated info page for copy paste
-
Microsoft is exploring adding a command line text editor into Windows, and it wants your feedback
I really like micro, a nano-like editor with a very sane, regular people friendly keybinding.
micro: winget install zyedidia.micro
vis
- Oasis – a small, statically-linked Linux system
-
Why Kakoune
> I wonder if the author has ever heard of vis[0]
Yes.
https://github.com/martanne/vis/wiki/Differences-from-Kakoun...
https://github.com/mawww/kakoune/wiki#onboarding
> which imho fulfills far better each one of those premises
Not very motivated for such a harsh critic..
> Kakoune gives you:
> Small and understandable core.
> Proficiency with POSIX tools, and maybe even some programming languages other than sh.
> Structural regular expressions as a central way of text manipulation.
> With multiple selections created via regular expressions, acting upon regular expressions.
> Fresh take on the modal editing paradigm.
I wonder if the author has ever heard of vis[0] which imho fulfills far better each one of those premises
-
The Text Editor Sam by Rob Pike
If you want an editor that uses Sam's structural regexes with keyboard-focussed vi-style interaction, you might be interested in https://github.com/martanne/vis
-
Can we write a Neo-vim Successor using rust?
Not Rust, but there's vis which aims to be a Vi(m) inspired editor with Sam's structural regular expressions.
-
Helix: Release 23.03 Highlights
> They either break from Vim's model (kakoune, helix) or follow Vim along with all it's flaws (Neovim, Vis).
I am sincerely curious of what flaws from Vim has Vis inherited, in your opinion.
I have the impression that the design idea of Vis is taking only the modal design of Vi (not Vim), plus the structural regular expressions of Sam, then make it as clean as possible with programmability via Lua plugins.
In fact, the state non-goals [1] seems to clearly distant itself from Vim.
- Helix: Post-Modern Text Editor
- Mle is a small, flexible, terminal-based text editor written in C
-
Quels sont vos utilitaires indispensables ?
vis, le fils caché de vim(1) et sam(1)
-
NextVI - The Suckless Editor
vis.
What are some alternatives?
helix - A post-modern modal text editor.
filemanager-plugin - A file manager plugin for the editor "Micro"
kakoune - mawww's experiment for a better code editor
xclip - Command line interface to the X11 clipboard
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
editorconfig-core-go - EditorConfig Core written in Go
html-to-markdown - ⚙️ Convert HTML to Markdown. Even works with entire websites and can be extended through rules.
edex-ui - A cross-platform, customizable science fiction terminal emulator with advanced monitoring & touchscreen support.
xurls - Extract urls from text
gofeed - Parse RSS, Atom and JSON feeds in Go
nextvi - Next version of neatvi (a small vi/ex editor) for editing bidirectional UTF-8 text