dotfiles
sway-systemd
dotfiles | sway-systemd | |
---|---|---|
4 | 3 | |
1 | 125 | |
- | - | |
8.3 | 2.7 | |
almost 2 years ago | 18 days ago | |
Shell | Python | |
Creative Commons Zero v1.0 Universal | 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.
dotfiles
-
high input latency (>200ms) on each keypress when editing markdown with treesitter in neovim
I've enabled filetype.lua using g.do_filetype_lua = 1 and disabled filetype.vim using g.did_load_filetypes = 0. I'm using the markdown treesitter parser. Here's the --startuptime log file when a markdown file is opened. Here's my ~/.config/nvim.
-
What's the current most effective way of setting env variables in Sway?
You can use my dotfiles for reference if you want.
-
Can Swaybg cycle wallpapers?
Here's my simple systemd timer to rotate wallpapers in case you're using a distro with systemd.
-
No_color
> Why is this so annoying? It's a very common workflow that allows you to customize how an application behaves and simplify how you run it.
I don't know about others but I'm not a fan of monstrosity like this
https://github.com/ayushnix/dotfiles/commit/2eb66eff8a03a5bf...
If I stuff it into a wrapper script, I'm essentially trying to emulate config files, which is what should've been used in the first place. This is why I prefer using config files rather than creating uglier and harder to maintain wrapper scripts.
> I'm a big fan of following the 12factor[1] approach.
I guess if you don't want state associated with your deployments, environment variables are better but I would still argue that they aren't manageable when their values become large as shown above or if their numbers start approaching double digits because when that happens, you're essentially emulating config files anyways.
sway-systemd
-
What's the current most effective way of setting env variables in Sway?
This runs Sway in the context of a systemd service, so it will inherit systemd's environment. I use sway-systemd to import stuff like WAYLAND_DISPLAY into the systemd context among other things. My custom env vars are in .config/environment.d which will be loaded by systemd automatically: Sway env, generic Wayland env
-
User service to save/restore settings to be run on start/exit of graphical environment
Thanks, I had some time and was able to get the service working after following your suggestion. I came across sway-systemd and that along with seeing how you did things made things a lot clearer. The following service should execute the script and let it finish (it finishes in less than a second) before exiting the graphical session, right? Would it be possible to modify it to run it even earlier after killing sway (or right before)? save-desktop-settings.service:
-
OOM Killer Kills All User Processes
Anyways, I did that to address the same issue with Sway in Fedora and the script should be fully functional with i3. Feel free to try if you're willing to give systemd-oomd another chance. And here is a little extra to go even further and isolate individual windows in tmux.
What are some alternatives?
wpaperd - Modern wallpaper daemon for Wayland
dotfiles - All my dotfiles.
no-ansi - A single-function CLI tool to strip escape codes from input
systemd - The systemd System and Service Manager
dotfiles - My dotfiles managed with chezmoi
dotfiles - Colin's configurations for bash, vim, i3, git, tmux, etc.
emacs-theme-gruvbox - Gruvbox is a retro groove color scheme for Emacs. Port of the Vim version.
colorized-logs - tools for logs with ANSI color
grc - generic colouriser
dumb - A tool for stripping control characters and escape sequences from terminal output in Linux.
dotfiles - My all dotfiles config for my all computer linux base
nvim-treesitter - Nvim Treesitter configurations and abstraction layer