dotfiles VS no_color

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.

You can use my dotfiles for reference if you want.

Here's my simple systemd timer to rotate wallpapers in case you're using a distro with systemd.

> 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.

This sounds like a really good pattern, and something that deserves to become a modern standard (like https://no-color.org/).

I feel like this should be made opt in somehow. If you are a noninteractive process and stdin is a tty then you probably shouldn't be swallowing input. I frequently blind-type the next command while a long running command is active, because well behaved noninteractive programs don't swallow input from stdin.

Does this support the environment variable for NO_COLOR too? https://no-color.org/

Some of us prefer tools which work best without them.

Allow me to repeat my plea for CLI developers to take a little time to read https://no-color.org and ensure their programs honor things like NO_COLOR, npm config set color false, TERM=dumb, INSIDE_EMACS etc.

https://news.ycombinator.com/item?id=35017940

Change: [#1908] Detects if terminal is VT100 capable and uses colors for the output, can be disabled using NO_COLOR.

Why not let termenv do the hard part of making this portable across terminals? It also supports lesser-known conventions like NO_COLOR.