ouch
micro-editor
ouch | micro-editor | |
---|---|---|
12 | 227 | |
1,962 | 23,903 | |
2.2% | - | |
9.4 | 9.4 | |
10 days ago | 4 days 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.
ouch
-
Simple, fast and safety alternative for unzip
There's one that's also written in rust: https://github.com/ouch-org/ouch
-
Ouch - simple compression and decompression for your terminal
I use for some time Ouch, It's a CLI tool for compressing and decompressing various formats (at this moment .tar, .zip, .gz, .xz, .lzma, .bz, .bz2, .lz4, .sz, .zst). You can compress, decompress or list archive. It's just one binary application, without dependencies and for my usage is very fast. I don't create a lot of archives, I usually unpack them when I download something from the web and so far I'm very happy with ouch. It has a simple command syntax. I use on my machines with Debian musl version from release page and on Arch there are packages in AUR (to build with cargo or binary version).
-
Is there a tool to handle decompression of multiple formats?
I personally use ouch. It suppirts a bunch of stuff and to quote the readme:
- Painless Compression and Decompression in the Terminal
-
Is there any command-line application that you wish existed but doesn't (or isn't as good as you wished)?
ouch - a command-line app to unify file compression and decompression
- Hop: 25x faster than unzip and 10x faster than tar at reading individual files
- Ouch 0.3.0 released!
-
Whats your favourite open source Rust project that needs more recognition?
Shameless plug here, my favorite project currently is ouch, nobody knows about it, but I think it might gain some traction when we publish it again.
- ouch: a small, cross-platform unified CLI app for file (de)compression
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?
clap-rs - A full featured, fast Command Line Argument Parser for Rust
helix - A post-modern modal text editor.
compress-tools-rs - A Swiss Army Knife for handling compressed data in Rust
filemanager-plugin - A file manager plugin for the editor "Micro"
GeoRust - Geospatial primitives and algorithms for Rust
kakoune - mawww's experiment for a better code editor
rust-brotli - Brotli compressor and decompressor written in rust that optionally avoids the stdlib
xclip - Command line interface to the X11 clipboard
Popsicle - Multiple USB File Flasher
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
gutenberg - A fast static site generator in a single binary with everything built-in. https://www.getzola.org
editorconfig-core-go - EditorConfig Core written in Go