amp
micro-editor
Our great sponsors
| amp | micro-editor | |
|---|---|---|
| 17 | 227 | |
| 3,595 | 23,903 | |
| - | - | |
| 8.0 | 9.4 | |
| 14 days ago | 1 day ago | |
| Rust | Go | |
| GNU General Public License v3.0 or later | MIT License |
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.
amp
- Micro – A Modern Alternative to Nano
-
Editors written in rust
Amp - A complete text editor for your terminal
-
Looking for a CLI text editor/viewer that supports colors
You may also want to look here >> https://amp.rs/ << but that's kinda vim fashion You don't like. Nano, by the way, does have syntax color highlighting. Nano can also display line numbers.
- Amp: A text editor for your terminal
- Vim Editor Written in Rust
-
Vi will be around in 2068, whereas Visual Studio Code will be defunct before the end of this decade
Ahem: https://github.com/jmacdonald/amp
-
Please suggest a terminal text editor
I haven't had a need to go with anything other than n/vim or emacs, but just did a quick search and found https://amp.rs/. No idea if it meets your needs, since the old standby's do everything I'm going to need to do in a TUI, but maybe it does what you want.
-
Geany is a fantastic, fast, powerful GUI text editor for many purposes & has a low barrier to entry
ps: Amp is better than vim.
- Lightning-Fast and Powerful Code Editor Written in Rust
-
Thoughts on some of the actively developed text editors written in Rust?
amp
micro-editor
- Ask HN: What software sparks joy when using?
- Modeless Vim
-
Essential Command Line Tools for Developers
To see more screenshots of micro, showcasing some of the default color schemes, see here.
-
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
[4]: https://github.com/xxxserxxx/gotop
[5]: https://github.com/zyedidia/micro
-
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...
[3] https://github.com/cessen/ropey/pull/67
- 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
micro: winget install zyedidia.micro
- What is the best basic ass text editor?
What are some alternatives?
lapce - Lightning-fast and Powerful Code Editor written in Rust
helix - A post-modern modal text editor.
awesome-rewrite-it-in-rust - A curated list of replacements for existing software written in Rust [Moved to: https://github.com/TaKO8Ki/awesome-alternatives-in-rust]
filemanager-plugin - A file manager plugin for the editor "Micro"
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
kakoune - mawww's experiment for a better code editor
google-java-format - Reformats Java source code to comply with Google Java Style.
xclip - Command line interface to the X11 clipboard
zee - A modern text editor for the terminal written in Rust [Moved to: https://github.com/zee-editor/zee]
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
neovim - Vim-fork focused on extensibility and usability
editorconfig-core-go - EditorConfig Core written in Go