tests/checks/no-config.fish

#RUN: %fish --no-config %s

functions | string match help
# CHECK: help

# Universal variables are disabled, we fall back to setting them as global
set -U
# CHECK:
set -U foo bar
set -S foo
# CHECK: $foo: set in global scope, unexported, with 1 elements
# CHECK: $foo[1]: |bar|

set -q fish_function_path[2]
and echo fish_function_path has two elements
tests: filter control sequences only when interactive This demonstrates that we only write control sequences when interactive. 2024-04-12 12:19:32 +02:00			`#RUN: %fish --no-config %s`
Only use DATADIR in $fish_function_path if no-config is used This only uses the functions fish ships with, but still doesn't allow any customization, which is the point of no-config. This makes it a lot more usable, given that the actual normal prompt and things are there. This still doesn't set any colors, because we don't run __fish_config_interactive because we don't read config.fish (any config.fish), because that would run the snippets. 2021-04-11 11:52:30 +02:00
			`functions \| string match help`
			`# CHECK: help`

			`# Universal variables are disabled, we fall back to setting them as global`
			`set -U`
			`# CHECK:`
			`set -U foo bar`
			`set -S foo`
			`# CHECK: $foo: set in global scope, unexported, with 1 elements`
			`# CHECK: $foo[1]: \|bar\|`

Make functions, completions and tests resilient to running on an embed-data fish In case a completion needs a function from another script, run `complete -C"foo "` to load it, so the full autoloading logic is used. Otherwise these things break if the path is off. E.g. cargo's version will fail if you override the cargo completion in ~/.config/fish/completions without also overriding the rustup completions. In other cases, fix for empty $__fish_data_dir, which will be coming in the next commit 2025-03-25 20:26:23 +01:00			`set -q fish_function_path[2]`
			`and echo fish_function_path has two elements`