mirror of
https://github.com/fish-shell/fish-shell.git
synced 2026-05-03 03:41:14 -03:00
17b4b39c8b
Our use of the terminfo database in /usr/share/terminfo/$TERM is both
1. a way for users to configure app behavior in their terminal (by
setting TERM, copying around and modifying terminfo files)
2. a way for terminal emulator developers to advertise support for
backwards-incompatible features that are not otherwise easily observable.
To 1: this is not ideal (it's very easy to break things). There's not many
things that realistically need configuration; let's use shell variables
instead.
To 2: in practice, feature-probing via terminfo is often wrong. There's not
many backwards-incompatible features that need this; for the ones that do
we can still use terminfo capabilities but query the terminal via XTGETTCAP
directly, skipping the file (which may not exist on the same system as
the terminal).
---
Get rid of terminfo. If anyone finds a $TERM where we need different behavior,
we can hardcode that into fish.
* Allow to override this with `fish_features=no-ignore-terminfo fish`
Not sure if we should document this, since it's supposed to be removed soon,
and if someone needs this (which we don't expect), we'd like to know.
* This is supported on a best-effort basis; it doesn't match the previous
behavior exactly. For simplicity of implementation, it will not change
the fact that we now:
* use parm_left_cursor (CSI Ps D) instead of cursor_left (CSI D) if
terminfo claims the former is supported
* no longer support eat_newline_glitch, which seems no longer present
on today's ConEmu and ConHost
* Tested as described in https://github.com/fish-shell/fish-shell/pull/11345#discussion_r2030121580
* add `man fish-terminal-compatibility` to state our assumptions.
This could help terminal emulator developers.
* assume `parm_up_cursor` is supported if the terminal supports XTGETTCAP
* Extract all control sequences to src/terminal_command.rs.
* Remove the "\x1b(B" prefix from EXIT_ATTRIBUTE_MODE. I doubt it's really
needed.
* assume it's generally okay to output 256 colors
Things have improved since commit 3669805627 (Improve compatibility with
0-16 color terminals., 2016-07-21).
Apparently almost every actively developed terminal supports it, including
Terminal.app and GNU screen.
* That is, we default `fish_term256` to true and keep it only as a way to
opt out of the the full 256 palette (e.g. switching to the 16-color
palette).
* `TERM=xterm-16color` has the same opt-out effect.
* `TERM` is generally ignored but add back basic compatiblity by turning
off color for "ansi-m", "linux-m" and "xterm-mono"; these are probably
not set accidentally.
* Since `TERM` is (mostly) ignored, we don't need the magic "xterm" in
tests. Unset it instead.
* Note that our pexpect tests used a dumb terminal because:
1. it makes fish do a full redraw of the commandline everytime, making it
easier to write assertions.
2. it disables all control sequences for colors, etc, which we usually
don't want to test explicitly.
I don't think TERM=dumb has any other use, so it would be better
to print escape sequences unconditionally, and strip them in
the test driver (leaving this for later, since it's a bit more involved).
Closes #11344
Closes #11345
176 lines
9.7 KiB
Fish
176 lines
9.7 KiB
Fish
if test -d "$__fish_data_dir/man/man1/"
|
|
complete -c help -x -a '(__fish_print_commands)' -d 'Help for this command'
|
|
end
|
|
|
|
# Help topics in index.html
|
|
# This was semi-automated with `grep 'class="anchor"' -A1 /usr/share/doc/fish/index.html
|
|
# It's not fully automated since that requires parsing html with regex,
|
|
# and since this is by definition in sync - we ship the html, and we ship these completions.
|
|
complete -c help -x -a autosuggestions -d Autosuggestions
|
|
complete -c help -x -a builtin-overview -d 'Builtin commands'
|
|
complete -c help -x -a cartesian-product -d 'Cartesian Products'
|
|
complete -c help -x -a color -d 'Setting syntax highlighting colors'
|
|
complete -c help -x -a combine -d 'Combining different expansions'
|
|
complete -c help -x -a debugging -d 'Debugging fish scripts'
|
|
complete -c help -x -a editor -d 'Command line editor'
|
|
complete -c help -x -a emacs-mode -d 'Emacs mode commands'
|
|
complete -c help -x -a escapes -d 'Escaping characters'
|
|
complete -c help -x -a event -d 'Event handlers'
|
|
complete -c help -x -a expand -d 'Parameter expansion (Globbing)'
|
|
complete -c help -x -a expand-brace -d 'Brace expansion {a,b,c}'
|
|
complete -c help -x -a expand-command-substitution -d 'Command substitution'
|
|
complete -c help -x -a expand-command-substitution -d 'Command substitution (SUBCOMMAND)'
|
|
complete -c help -x -a expand-home -d 'Home directory expansion ~USER'
|
|
complete -c help -x -a expand-index-range -d 'Index range expansion'
|
|
complete -c help -x -a expand-variable -d 'Variable expansion $VARNAME'
|
|
complete -c help -x -a expand-wildcard -d 'Wildcard expansion *.*'
|
|
# Note: This is hard-coded in help.fish - it's not an anchor in the html.
|
|
complete -c help -x -a globbing -d 'Parameter expansion (Globbing)'
|
|
complete -c help -x -a greeting -d 'Configurable greeting'
|
|
complete -c help -x -a history -d 'Help on how to reuse previously entered commands'
|
|
complete -c help -x -a history-search -d 'Searchable history'
|
|
complete -c help -x -a identifiers -d 'Shell variable and function names'
|
|
complete -c help -x -a initialization -d 'Initialization files'
|
|
complete -c help -x -a introduction -d Introduction
|
|
complete -c help -x -a job-control -d 'Running multiple programs'
|
|
complete -c help -x -a killring -d 'Copy and paste (Kill Ring)'
|
|
complete -c help -x -a more-help -d 'Further help and development'
|
|
complete -c help -x -a multiline -d 'Multiline editing'
|
|
complete -c help -x -a other -d 'Other features'
|
|
complete -c help -x -a piping -d Piping
|
|
complete -c help -x -a prompt -d 'Programmable prompt'
|
|
complete -c help -x -a quotes -d Quotes
|
|
complete -c help -x -a redirects -d 'Input/Output (IO) redirection'
|
|
complete -c help -x -a shared-binds -d 'Shared bindings'
|
|
complete -c help -x -a syntax -d 'Introduction to the fish syntax'
|
|
complete -c help -x -a syntax-background -d 'Background jobs'
|
|
complete -c help -x -a syntax-conditional -d 'Conditional execution of code and flow control'
|
|
complete -c help -x -a syntax-function -d Functions
|
|
complete -c help -x -a syntax-function-autoloading -d 'Autoloading functions'
|
|
complete -c help -x -a syntax-function-wrappers -d 'Defining aliases'
|
|
complete -c help -x -a syntax-job-control -d 'Job control'
|
|
complete -c help -x -a syntax-words -d 'Some common words'
|
|
complete -c help -x -a tab-completion -d 'How tab-completion works'
|
|
complete -c help -x -a title -d 'Programmable title'
|
|
complete -c help -x -a variables -d 'Shell variables'
|
|
complete -c help -x -a variables-lists -d Lists
|
|
complete -c help -x -a variables-color -d 'Variables for changing highlighting colors'
|
|
complete -c help -x -a variables-export -d 'Exporting variables'
|
|
complete -c help -x -a variables-functions -d 'Variable scope for functions'
|
|
complete -c help -x -a variables-locale -d 'Locale variables'
|
|
complete -c help -x -a variables-scope -d 'Variable scope'
|
|
complete -c help -x -a variables-special -d 'Special variables'
|
|
complete -c help -x -a variables-status -d 'The status variable'
|
|
complete -c help -x -a variables-universal -d 'More on universal variables'
|
|
complete -c help -x -a vi-mode -d 'Vi mode commands'
|
|
complete -c help -x -a vi-mode-command -d 'Command mode'
|
|
complete -c help -x -a vi-mode-insert -d 'Insert mode'
|
|
complete -c help -x -a vi-mode-visual -d 'Visual mode'
|
|
|
|
# Completions
|
|
complete -c help -x -a completion-own -d 'Writing your own completions'
|
|
complete -c help -x -a completion-func -d 'Useful functions for writing completions'
|
|
complete -c help -x -a completion-path -d 'Where to put completions'
|
|
|
|
# Tutorial
|
|
complete -c help -x -a tutorial -d Tutorial
|
|
complete -c help -x -a tut-autoload -d 'Autoloading Functions'
|
|
complete -c help -x -a tut-autosuggestions -d Autosuggestions
|
|
complete -c help -x -a tut-combiners -d 'Combiners (And, Or, Not)'
|
|
complete -c help -x -a tut-command_substitutions -d 'Command Substitutions'
|
|
complete -c help -x -a tut-conditionals -d 'Conditionals (If, Else, Switch)'
|
|
complete -c help -x -a tut-exit_status -d 'Exit Status'
|
|
complete -c help -x -a tut-exports -d 'Exports (Shell Variables)'
|
|
complete -c help -x -a tut-functions -d Functions
|
|
complete -c help -x -a tut-getting_help -d 'Getting Help'
|
|
complete -c help -x -a tut-learning_Fish -d 'Learning fish'
|
|
complete -c help -x -a tut-lists -d Lists
|
|
complete -c help -x -a tut-loops -d Loops
|
|
complete -c help -x -a tut-more -d 'Ready for more?'
|
|
complete -c help -x -a tut-path -d '$PATH'
|
|
complete -c help -x -a tut-pipes_and_redirections -d 'Pipes and Redirections'
|
|
complete -c help -x -a tut-prompt -d Prompt
|
|
complete -c help -x -a tut-running_commands -d 'Running Commands'
|
|
complete -c help -x -a tut-semicolon -d 'Separating Commands (Semicolon)'
|
|
complete -c help -x -a tut-startup -d "Startup (Where's .bashrc?)"
|
|
complete -c help -x -a tut-syntax_highlighting -d 'Syntax Highlighting'
|
|
complete -c help -x -a tut-tab_completions -d 'Tab Completions'
|
|
complete -c help -x -a tut-universal -d 'Universal Variables'
|
|
complete -c help -x -a tut-variables -d Variables
|
|
complete -c help -x -a tut-why_fish -d 'Why fish?'
|
|
complete -c help -x -a tut-wildcards -d Wildcards
|
|
|
|
# Other pages
|
|
complete -c help -x -a terminal-compatibility -d "Terminal features used by fish"
|
|
complete -c help -x -a releasenotes -d "Fish's release notes"
|
|
complete -c help -x -a completions -d "How to write completions"
|
|
complete -c help -x -a faq -d "Frequently Asked Questions"
|
|
complete -c help -x -a fish-for-bash-users -d "Differences from bash"
|
|
|
|
complete -c help -x -a argument-handling -d "How to handle arguments"
|
|
complete -c help -x -a autoloading-functions -d "How functions are loaded"
|
|
complete -c help -x -a brace-expansion -d "{a,b} brace expansion"
|
|
complete -c help -x -a builtin-commands -d "An overview of fish's builtins"
|
|
complete -c help -x -a combining-different-expansions -d "How different expansions work together"
|
|
complete -c help -x -a combining-lists-cartesian-product -d "How lists combine"
|
|
complete -c help -x -a command-substitution -d "(command) command substitution"
|
|
complete -c help -x -a comments -d "# comments"
|
|
complete -c help -x -a conditions -d "ifs and elses"
|
|
complete -c help -x -a defining-aliases -d "How to define an alias"
|
|
complete -c help -x -a escaping-characters -d "How \\\\ escaping works"
|
|
complete -c help -x -a exporting-variables -d "What set -x does"
|
|
complete -c help -x -a functions -d "How to define functions"
|
|
complete -c help -x -a home-directory-expansion -d "~ expansion"
|
|
complete -c help -x -a index-range-expansion -d "var[x..y] slices"
|
|
complete -c help -x -a input-output-redirection -d "< and > redirectoins"
|
|
complete -c help -x -a lists -d "Variables with multiple elements"
|
|
complete -c help -x -a loops-and-blocks -d "while, for and begin"
|
|
complete -c help -x -a more-on-universal-variables
|
|
complete -c help -x -a overriding-variables-for-a-single-command -d "foo=bar variable overrides"
|
|
complete -c help -x -a pager-color-variables -d "How to color the pager"
|
|
complete -c help -x -a path-variables -d 'Why $PATH is special'
|
|
complete -c help -x -a shell-variable-and-function-names -d 'What characters are allowed in names'
|
|
complete -c help -x -a shell-variables
|
|
complete -c help -x -a special-variables
|
|
complete -c help -x -a syntax-highlighting-variables
|
|
complete -c help -x -a syntax-overview
|
|
complete -c help -x -a terminology
|
|
complete -c help -x -a the-fish-language
|
|
complete -c help -x -a the-status-variable -d '$status, the return code'
|
|
complete -c help -x -a variable-expansion -d '$variable'
|
|
complete -c help -x -a variable-scope -d 'Local, global and universal scope'
|
|
complete -c help -x -a variable-scope-for-functions
|
|
complete -c help -x -a wildcards-globbing
|
|
complete -c help -x -a abbreviations
|
|
complete -c help -x -a command-line-editor
|
|
complete -c help -x -a configurable-greeting
|
|
complete -c help -x -a copy-and-paste-kill-ring
|
|
complete -c help -x -a custom-bindings
|
|
complete -c help -x -a custom-prompt -d 'How to write your own prompt'
|
|
complete -c help -x -a directory-stack
|
|
complete -c help -x -a emacs-mode-commands
|
|
complete -c help -x -a help
|
|
complete -c help -x -a interactive-use
|
|
complete -c help -x -a multiline-editing
|
|
complete -c help -x -a navigating-directories
|
|
complete -c help -x -a private-mode
|
|
complete -c help -x -a programmable-prompt
|
|
complete -c help -x -a programmable-title
|
|
complete -c help -x -a searchable-command-history
|
|
complete -c help -x -a shared-bindings
|
|
complete -c help -x -a syntax-highlighting
|
|
complete -c help -x -a vi-mode-commands
|
|
complete -c help -x -a arithmetic-expansion
|
|
complete -c help -x -a blocks-and-loops
|
|
complete -c help -x -a builtins-and-other-commands
|
|
complete -c help -x -a command-substitutions
|
|
complete -c help -x -a heredocs
|
|
complete -c help -x -a process-substitution
|
|
complete -c help -x -a prompts -d 'How to make your own prompt'
|
|
complete -c help -x -a quoting -d 'How "" and \'\' work'
|
|
complete -c help -x -a special-variables
|
|
complete -c help -x -a string-manipulation
|
|
complete -c help -x -a test-test
|
|
complete -c help -x -a wildcards-globs
|
|
complete -c help -x -a frequently-asked-questions
|