Mahmoud Al-Qudsi 537cde0c72 Avoid auto-colorization of ls output if CLICOLOR_FORCE is set ... We don't set this variable ourselves, but some might set it in their config out of habit coming from shells that don't automatically colorize ls output. This variable overrides stdout tty detection for `ls --color=auto` (but does not modify the behavior of `ls --color=never` or `ls --color=always` regardless of its value) under at least the BSD version of `ls`. (Under the GNU version, it influences colorization only if stdout *is* a tty.) If we detect CLICOLOR_FORCE *and* we are not writing directly to the tty, we skip colorization (by clearing-but-not-erasing `$__fish_ls_color_opt`, so that we don't end up accidentally using its value from another scope).		2024-05-23 20:50:23 -05:00
..
completions	Add completions for reuse-tool (#10511)	2024-05-23 16:53:53 -05:00
functions	Avoid auto-colorization of ls output if CLICOLOR_FORCE is set	2024-05-23 20:50:23 -05:00
groff	workaround broken groff man page config	2016-10-19 13:43:04 -07:00
tools	Fix the acidhub prompt for a commitless repository (#10462)	2024-05-02 19:37:12 +02:00
__fish_build_paths.fish.in	Rename "snippets" to "conf" internally, and document them as snippets	2016-04-06 09:33:09 +08:00
config.fish	Move generated completions to cache directory	2024-04-27 10:39:30 +02:00