esup
micro-editor
esup | micro-editor | |
---|---|---|
9 | 227 | |
394 | 23,964 | |
- | - | |
1.8 | 9.4 | |
over 2 years ago | 4 days ago | |
Emacs Lisp | 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.
esup
-
Why does elpaca make emacs startup so much faster?
Probably the best way to figure out what's going on at startup time is ESUP (Emacs Start Up Profiler): https://github.com/jschaf/esup You could run it on the old config and the new. Although I suppose the processes may be different enough that there's nothing meaningful to compare.
-
[Emacs] A full fledge configuration
I agree with you. For startup profiling, use-package-report and https://github.com/jschaf/esup can help too.
-
An easy trick I found to improve Emacs start-up time
A very useful tool for achieving faster startup is esup (https://github.com/jschaf/esup) which times each code block that runs in the emacs startup.
-
Slow emacs startup only on work laptop
Have you tried running M-x esup with https://github.com/jschaf/esup to see what is taking up the start-up time?
-
Zee: A modern text editor for the terminal written in Rust
Are you on Emacs 28? Native-comp is enabled by default and it's Just Worked™ for me. Or are you on at least Emacs 27? Emacs 27 added native JSON parsing; stuff like lsp-mode works a lot better now.
(Personally running Emacs 29 built from source on an M1 Pro; everything is instant! Even on my old dumpy i5 machine, everything except startup was pretty snappy, with the exception of startup which took ~4 seconds.)
If it's startup you're concerned about, try the esup[1] package to figure out what's taking so long.
[1]: https://github.com/jschaf/esup
-
Emacs taking a lot of time to load
If you're really interested what happens on startup, you can play around with the startup profiler( https://github.com/jschaf/esup ) or similar packages that time the execution of your .emacs.
-
Do any of you have some tips on speeding up emacs:
I used the Emacs Startup Profiler (ESUP) https://github.com/jschaf/esup which identified several culprits in my init files. Removing or deferring the loading of those packages took my startup time from ~15 seconds to about 2.5 seconds. (Still room for improvement!)
-
What is your startup time
GitHub - jschaf/esup: ESUP - Emacs Start Up Profiler
-
How to diagnose slow emacs at run-time.
Try out esup
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?
emacs-from-scratch - An example of a fully custom Emacs configuration developed live on YouTube!
helix - A post-modern modal text editor.
.emacs.d - My current Emacs setup.
filemanager-plugin - A file manager plugin for the editor "Micro"
jinx - 🪄 Enchanted Spell Checker
kakoune - mawww's experiment for a better code editor
zee - A modern text editor for the terminal written in Rust [Moved to: https://github.com/zee-editor/zee]
xclip - Command line interface to the X11 clipboard
digga - A flake utility library to craft shell-, home-, and hosts- environments.
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
config
editorconfig-core-go - EditorConfig Core written in Go