CuteVim
micro-editor
CuteVim | micro-editor | |
---|---|---|
4 | 227 | |
85 | 23,964 | |
- | - | |
6.6 | 9.4 | |
4 months ago | 3 days ago | |
Vim Script | Go | |
- | 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.
CuteVim
-
I Just Wanted Emacs to Look Nice – Using 24-Bit Color in Terminals
BTW you should package your emacs config file with the emacs APE to do a cuteemacs, to carry your config files and everything in a portable binary: https://github.com/csdvrx/CuteVim
Another idea: have you considered that the "program that would be run by .bashrc" to generate the "unambiguous 24-bit color capabilities" could set environment variables to communicate them? Like, if you can't stuff them in terminfo, stuff them in environment variables! Env var work well on Windows, and the configuration files of terminal programs could just use these when available to override.
It's be like adding friends to your proposed TERMVERSION: TERMSETF24 etc
-
Modeless Vim
for vim aarch64 and x86-64 : https://github.com/csdvrx/CuteVim
just embed your own vimrc with zip following the instructions
for others, see https://cosmo.zip/pub/cosmos/bin/
-
Actually Portable Vim (With a Cute Vimrc)
> That being said, the config is definitely highly personal
I have very special preferences (like CHORDING EVERYWHERE! :) )
> it would be amazing to have a set of scripts to compile one's own personal .vimrc
Actually, I thought about people who may have different preferences!
If you want to do the same thing but with your own .vimrc, just check the "How can I make my own CuteVim APE?" section in the README (https://github.com/csdvrx/CuteVim?tab=readme-ov-file#how-can...)
This section documents the use of the refresh.sh script from https://github.com/csdvrx/CuteVim/blob/main/refresh.sh
> and related config files (really, the entire .vim directory) into a single APE.
I don't like having a billion files everywhere (like plugins/ etc) so I didn't think about that usecase, but that would be a great addition because most people have a .vim tree: even with my dislike for having too many files, I have myself a few in .vim/after/syntax/ (to apply italics to comments)
If you can contribute a script that converts your .vimrc and .vim/ tree into something that can be added to the APE, I'd be very happy to add it!
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?
wl-gammactl
helix - A post-modern modal text editor.
ModelessVim - Configuration files to turn vim into a modeless editor.
filemanager-plugin - A file manager plugin for the editor "Micro"
kakoune - mawww's experiment for a better code editor
buildroot - Tesla's buildroot repository
xclip - Command line interface to the X11 clipboard
novim-mode - Plugin to make Vim behave more like a 'normal' editor
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
ergoemacs-mode - ergoemacs-mode
editorconfig-core-go - EditorConfig Core written in Go