up
micro-editor
Our great sponsors
up | micro-editor | |
---|---|---|
25 | 227 | |
8,141 | 23,903 | |
- | - | |
0.0 | 9.4 | |
8 months ago | 1 day ago | |
Go | Go | |
Apache License 2.0 | 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.
up
-
Fx – Terminal JSON Viewer
This fx rewrite is very exciting. I'll have to try it. I thought of fx as a wrapper around jq, that allowed quick iteration over building jq scripts. Sort of an Ultimate Plumber [1] but only for jq. It looks like it is now more like a JavaScript processor plus an interactive viewer.
Someone mention Visidata[2]? VisiData is also a TUI that is great on tabular data, and it can work with json. If your JSON is mostly tabular in nature, Visidata does a great job at showing that data and allowing you to explore it. A lot of json I deal with is tabular-like data. There is a great tutorial [3], that can help you get your bearings with Visidata. Once you understand those basics you might want to look at this thread [4] for what commands you can use with json.
[1] Ultimate Plumber: https://github.com/akavel/up
- Up: Plumber is a tool for writing Linux pipes with instant live preview
-
Show HN: LineSelect, shell utility to interactively select lines in a pipeline
Ultimate plumber can do this.
https://github.com/akavel/up
- Ultimate Plumber – a tool for writing Linux pipes with live preview
-
`jqp`, a TUI playground for `jq`
Been using up for years but this looks nice too
-
An interactive wrapper around `jq`
Fun. But I can achieve the same result (I think) with ultimate plumber and regular jq, but without being restricted just to jq. Feel free to correct me.
-
What are some useful cli tools that arent popular?
Up - The Ultimate Plumber makes the best pipes !
-
A list of new(ish) command line tools – Julia Evans
As an alternative allowing the use of any shell command/pipeline on the results interactively, see also: https://github.com/akavel/up
- RegExr: Learn, Build and Test Regex
-
Is there any command-line application that you wish existed but doesn't (or isn't as good as you wished)?
Would https://github.com/akavel/up solve your problem?
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?
nvim-jqx - Populate the quickfix with json entries
helix - A post-modern modal text editor.
zsh-history-substring-search - 🐠 ZSH port of Fish history search (up arrow)
filemanager-plugin - A file manager plugin for the editor "Micro"
dive - A tool for exploring each layer in a docker image
kakoune - mawww's experiment for a better code editor
fzf-tab - Replace zsh's default completion selection menu with fzf!
xclip - Command line interface to the X11 clipboard
fx - Terminal JSON viewer & processor
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
hurl - Hurl, run and test HTTP requests with plain text.
editorconfig-core-go - EditorConfig Core written in Go