dotfiles
no-ansi
dotfiles | no-ansi | |
---|---|---|
4 | 1 | |
1 | 0 | |
- | - | |
8.3 | 2.7 | |
almost 2 years ago | over 2 years ago | |
Shell | Rust | |
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.
no-ansi
-
No_color
I did a quick GitHub search and found two of them:
https://github.com/kurtbuilds/no-ansi
Written in rust and ultimately uses vte from alacritty to write through a virtual terminal. Can be given a file on the command line.
https://github.com/emptymonkey/dumb
Written in Lex and just strips a number of specific escape sequences (written 9 years ago so likely doesn't include a few). Only stdin to stdout.
What are some alternatives?
wpaperd - Modern wallpaper daemon for Wayland
bemenu - Dynamic menu library and client program inspired by dmenu
sway-systemd - Systemd integration for Sway session
grc - generic colouriser
dotfiles - My dotfiles managed with chezmoi
no_color - Website data for no-color.org
emacs-theme-gruvbox - Gruvbox is a retro groove color scheme for Emacs. Port of the Vim version.
chalk - 🖍 Terminal string styling done right
colorized-logs - tools for logs with ANSI color
nofun - filter ANSI colors and animations
dumb - A tool for stripping control characters and escape sequences from terminal output in Linux.