Johannes Altmanninger efce176ceb Support help argument in "{ -h" ... Unlike other builtins, "{" is a separate token, not a keyword-string token. Allow the left brace token as command string; produce it when parsing "{ -h"/"{ --help" (and nowhere else). By using a decorated statement, we reuse logic for redirections etc. Other syntax elements like "and" are in the builtin list, which - adds highlighting logic - adds it to "builtin --names" - makes it runnable as builtin (e.g. "builtin '{'" would hypothetically print the man page) These don't seem very important (highlighting for '{' needs to match '}' anyway). Additionally, making it a real builtin would mean that we'd need to deactivate a few places that unescape "{" to BRACE_BEGIN. Let's not add it to the built in list. Instead, simply synthesize builtin_generic in the right spot. I'm assuming we want "{ -h" to print help, but '"{" -h' to run an external command, since the latter is historical behavior. This works naturally with the above fake builtin approach which never tries to unescape the left brace.		2025-01-19 18:29:07 +01:00
..
completions	Fix double expansion of tokenized command line	2025-01-19 18:29:07 +01:00
functions	Support help argument in "{ -h"	2025-01-19 18:29:07 +01:00
groff
tools	default color scheme: Make commands "normal" color	2024-10-15 21:21:30 +02:00
__fish_build_paths.fish.in
config.fish	Move generated completions to cache directory	2024-04-27 10:39:30 +02:00