dtache
micro-editor
dtache | micro-editor | |
---|---|---|
12 | 227 | |
- | 23,903 | |
- | - | |
- | 9.4 | |
- | 7 days ago | |
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.
dtache
-
Mastering Eshell, Emacs's Elisp Shell
I wouldn't do it simply because there are some things for which it doesn't work best such as using tmux over it and I haven't yet bothered to read & setup dtache which would solve that problem.
-
Living The Eshell Dream: A Reduction in Latency From 70 Seconds to 3 Seconds
Another thing is why people may want to see the whole 10Mb compilation log in realtime? Redirect it to a file, M-x grep the things you need, and you are perfectly fine. There's also https://gitlab.com/niklaseklund/dtache
-
After years on Linux, I just discovered Vim & TMUX. They're fucking amazing.
GNU Screen, tmux and dtach (with convenient Emacs interface) all serve to limit that problem.
-
[Babel] Is it feasible to view the stdout of the code block async process?
Have a look at https://gitlab.com/niklaseklund/dtache
-
Dtache Vterm
Here is a short blog post illustrating how dtache, the package for detached shell commands https://gitlab.com/niklaseklund/dtache, can be integrated with vterm.
-
Improving shell in emacs
Regarding 4), that's what got me into developing dtache https://gitlab.com/niklaseklund/dtache. Could be an alternative if you want to avoid leaving Emacs :)
-
dtache - Version 0.4
There is a version 0.4 out for the **dtache** package. The short description of the package is that it provides the possibility to run commands that are detached from Emacs. To read more see the README here https://gitlab.com/niklaseklund/dtache. The major changes compared to the last release is:
-
Dtache Consult
The other day I merged an extension to integrate dtache with consult. The dtache is the package for detachable shell commands https://gitlab.com/niklaseklund/dtache. The functionality is opt in, and provided through the dtache-consult.el.
-
Dtache Eshell - Integration of dtache in eshell
You can read more about, and see some examples of dtache-eshell in action at https://niklaseklund.gitlab.io/blog/posts/dtache_eshell/, and if you are looking for the source code you will find it here https://gitlab.com/niklaseklund/dtache :)
- dtache : Dtach Emacs
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?