leftwm
micro-editor
Our great sponsors
leftwm | micro-editor | |
---|---|---|
22 | 227 | |
2,726 | 23,872 | |
1.9% | - | |
8.4 | 8.9 | |
15 days ago | 5 days ago | |
Rust | 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.
leftwm
- Any new Opensource projects in (rust) looking for contributors. I want to start my journey as an OSS contributor.
- if I wanted to make a Tiling Window Manager in Rust, how would I go about it?
-
Where should I adventure myself
(Also I wouldn't mind if you want to contribute to leftwm ;))
- LeftWM – A tiling window manager for Adventurers
-
Preferred DE/WM?
LeftWM if you are adventurous and want to support more Rust projects on Linux.
-
Picom backend optimization
I'm using a tiling window manager (LeftWM) and picom with experimental backends for compositing. I'm running into issues configuring picom for use on my laptop when I am on battery power. Two problems arise:
-
Is there a good tutorial for writing an X11 Tiling Window manager in Rust?
I've looked at these: - DWM: A popular, compact WM written in C - LeftWM: A popular, configurable WM written in Rust - GabelstaplerWM: An obscure, compact WM written in Rust - XCB DWM: An abandoned rewrite of DWM using XCB
-
Arch + Tiling Window Manager
Been using and liking LeftWM: https://github.com/leftwm/leftwm
-
Different window managers (e.g. tiling) on Windows?
In particular, I think that "ultrawide-vertical-stack" (based on "CenterMain" from LeftWM) is quite close to what you are looking for. Give it a try with komorebic change-layout ultrawide-vertical-stack!
-
Komorebi: Another tiling window manager for Windows 10 based on binary space partitioning
Once again I'm happy to answer any questions, and I want to give a special thanks to nog, leftwm and umberwm, whose work this project borrows from and builds upon.
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?
i3-and-kde-plasma - How to install the i3 window manager on KDE
helix - A post-modern modal text editor.
komorebi - A tiling window manager for Windows 🍉
filemanager-plugin - A file manager plugin for the editor "Micro"
wayland-rs - Rust implementation of the wayland protocol (client and server).
kakoune - mawww's experiment for a better code editor
dwl - dwm for Wayland - ARCHIVE: development has moved to Codeberg
xclip - Command line interface to the X11 clipboard
wlroots - A modular Wayland compositor library
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
my-penrose-config - My personal penrose config
editorconfig-core-go - EditorConfig Core written in Go