eget
micro-editor
Our great sponsors
eget | micro-editor | |
---|---|---|
13 | 227 | |
741 | 23,872 | |
- | - | |
5.1 | 8.9 | |
27 days ago | 5 days ago | |
Go | Go | |
MIT License | 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.
eget
-
Essential Command Line Tools for Developers
View on GitHub
- gh-dl: download releases from github repo
-
Install GitHub release binaries from the CLI interactively
would be good if you added a comparison with https://github.com/zyedidia/eget on your repo
-
The culmination of several months of work by dozens of people, Flatpak 1.14.0 is now out!
There used to be a project called ginstall.sh that kept like, a manually maintained database of various projects with static binaries and how to install them. It still exists, but maintenance stopped because its model was also not sustainable. Its use case is better covered by tools like asdf, stew, and if you want to get even simpler, eget.
- An ode to Flatpak (and Fedora Silverblue)
-
Asdf Performance
I'm a huge fan of asdf and have been using for years together with direnv! It's great to see how much effort is put into it! I hope more people adopt it so that we don't have to `curl | sh`! One thing I have issues with asdf is security as are no checksums, so, you if I project get compromised you'll get compromised, too. This, of course, is in addition to the third-party asdf plugin getting itself compromised (which is the greater risk). Last, but not least - I wish asdf came with something like eget [0] incorporated so that it can install 99% of the plugins directly and safely! Last, but not least - 99% of the plugins have almost identical code and all that changes is the repo, so, this should be generalized. For example, many years ago I made just one codebase of all HashiCorp plugins [1] and it's been working great!
[0]: https://github.com/zyedidia/eget
[1]: https://github.com/asdf-community/asdf-hashicorp
- get latest github
- Eget – Easily install prebuilt binaries from GitHub
- Zyedidia/eget: Easily install prebuilt binaries from GitHub
- Eget - Easily install prebuilt binaries from GitHub
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?
fetch - Download files, folders, and release assets from a specific git commit, branch, or tag of public and private GitHub repos.
helix - A post-modern modal text editor.
stew - 🥘 An independent package manager for compiled binaries.
filemanager-plugin - A file manager plugin for the editor "Micro"
bin - Effortless binary manager
kakoune - mawww's experiment for a better code editor
pastel - A command-line tool to generate, analyze, convert and manipulate colors
xclip - Command line interface to the X11 clipboard
flatpak-external-data-checker - A tool for checking if the external data used in Flatpak manifests is still up to date
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
office365-pol - [OUTDATED] A PlayOnLinux script that utilizes the version of Wine made for CrossOver to run Microsoft 365 Apps / Office 365 without requiring any paid CrossOver components
editorconfig-core-go - EditorConfig Core written in Go