turbo
micro-editor
turbo | micro-editor | |
---|---|---|
9 | 227 | |
419 | 23,903 | |
- | - | |
6.7 | 9.4 | |
about 2 months ago | 7 days ago | |
C++ | 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.
turbo
-
The Tilde Text Editor
https://github.com/magiblot/turbo which is built using Turbo Vision framework
- Turbo: An experimental text editor based on Scintilla and Turbo Vision
-
I miss Turbo C, I've never used such a fantastic IDE again. It could include assembly commands directly from C code, it had a powerful graphics library for the 80s. in forty years I've used many languages, environments, frameworks... but I still miss the simplicity and power of Turbo C under MS/DOS/
also https://github.com/magiblot/turbo
-
Lesser Known Terminal Editors
Turbo - editor made using TurboVision, with support for Unicode: https://github.com/magiblot/turbo
-
Building Rich Terminal Dashboards
Show them this, too:
https://github.com/magiblot/turbo
Applications like tvedit were designed for MS-DOS, which offered full interaction with the mouse and keyboard, and many of them were commercial products aimed at a general audience. TUI applications from the Unix tradition, however, were designed for use in terminals with limited capabilities, and were aimed at more technical users (or were created by the users themselves).
User-friendly TUI applications in MS-DOS were succeeded by Windows applications, while the largest revolution in the last 20 years in Unix TUIs has been the widespread support of 256/24-bit colors and UTF-8. Hence the gap in usability between the two worlds.
-
An experimental text editor based on Scintilla and Turbo Vision
Scintilla provides a few default platform adapters: GTK, Qt, Win32, etc. In order to have it work in a terminal application, I just wrote my own adapter.
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?
TuiCss - Text-based user interface CSS library
helix - A post-modern modal text editor.
pkg - Package your Node.js project into an executable
filemanager-plugin - A file manager plugin for the editor "Micro"
GUMBO-Editor - The simple text editor in written in C++
kakoune - mawww's experiment for a better code editor
reflex-vty - Build terminal applications using functional reactive programming (FRP) with Reflex FRP.
xclip - Command line interface to the X11 clipboard
tilde - The Tilde text editor
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
python-prompt-toolkit - Library for building powerful interactive command line applications in Python
editorconfig-core-go - EditorConfig Core written in Go