Fabian Homborg 0072367512 fish_add_path: Don't resolve symlinks ... The case for symlinked directories being duplicated a lot isn't there, but there *is* a usecase for adding the symlink rather than the target, and that's homebrew. E.g. homebrew installs ruby into /usr/local/Cellar/ruby/2.7.1_2/bin, and links to it from /usr/local/opt/ruby/bin. If we add the target, we would miss updates. Having path entries that point to the same location isn't a big problem - it's a path lookup, so it takes a teensy bit longer. The canonicalization is mainly so paths don't end up duplicated via weird spelling and so relative paths can be used.		2020-09-12 19:28:01 +02:00
..
completions	[ffmpeg] Prevent -codec from matching -codec:[vas]	2020-09-07 16:52:47 -05:00
functions	fish_add_path: Don't resolve symlinks	2020-09-12 19:28:01 +02:00
groff	workaround broken groff man page config	2016-10-19 13:43:04 -07:00
tools	Make prompts forward compatible with fish 3.1.2 by passing locally exported variable	2020-09-05 09:58:55 +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	Call "fish_command_not_found" if a command wasn't found	2020-09-06 11:15:54 +02:00
lynx.lss	Install custom LSS script to /usr/local/share/fish on make install	2017-09-26 14:31:11 -05:00