mirror of
https://github.com/fish-shell/fish-shell
synced 2024-12-27 05:13:10 +00:00
No description
340de73172
Previously, when a command wasn't found, fish would emit the "fish_command_not_found" *event*. This was annoying as it was hard to override (the code ended up checking for a function called `__fish_command_not_found_handler` anyway!), the setup was ugly, and it's useless - there is no use case for multiple command-not-found handlers. Instead, let's just call a function `fish_command_not_found` if it exists, or print the default message otherwise. The event is completely removed, but because a missing event is not an error (MEISNAE in C++-speak) this isn't an issue. Note that, for backwards-compatibility, we still keep the default handler function around even tho the new one is hard-coded in C++. Also, if we detect a previous handler, the new handler just calls it. This way, the backwards-compatible way to install a custom handler is: ```fish function __fish_command_not_found_handler --on-event fish_command_not_found # do a little dance, make a little love, get down tonight end ``` and the new hotness is ```fish function fish_command_not_found # do the thing end ``` Fixes #7293. |
||
---|---|---|
.builds | ||
.github | ||
benchmarks | ||
build_tools | ||
cmake | ||
debian | ||
doc_src | ||
etc | ||
osx | ||
pcre2 | ||
po | ||
share | ||
src | ||
tests | ||
.clang-format | ||
.clang-tidy | ||
.cppcheck.rules | ||
.cppcheck.suppressions | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.oclint | ||
.travis.yml | ||
BSDmakefile | ||
CHANGELOG.rst | ||
CMakeLists.txt | ||
CODE_OF_CONDUCT.md | ||
config_cmake.h.in | ||
CONTRIBUTING.rst | ||
COPYING | ||
Dockerfile | ||
fish.desktop | ||
fish.pc.in | ||
fish.png | ||
fish.spec.in | ||
GNUmakefile | ||
README.rst |
`fish <https://fishshell.com/>`__ - the friendly interactive shell |Build Status| ================================================================================= fish is a smart and user-friendly command line shell for macOS, Linux, and the rest of the family. fish includes features like syntax highlighting, autosuggest-as-you-type, and fancy tab completions that just work, with no configuration required. For more on fish’s design philosophy, see the `design document <https://fishshell.com/docs/current/design.html>`__. Quick Start ----------- fish generally works like other shells, like bash or zsh. A few important differences can be found at https://fishshell.com/docs/current/tutorial.html by searching for the magic phrase “unlike other shells”. Detailed user documentation is available by running ``help`` within fish, and also at https://fishshell.com/docs/current/index.html You can quickly play with fish right in your browser by clicking the button below: |Try in browser| Getting fish ------------ macOS ~~~~~ fish can be installed: - using `Homebrew <http://brew.sh/>`__: ``brew install fish`` - using `MacPorts <https://www.macports.org/>`__: ``sudo port install fish`` - using the `installer from fishshell.com <https://fishshell.com/>`__ - as a `standalone app from fishshell.com <https://fishshell.com/>`__ Packages for Linux ~~~~~~~~~~~~~~~~~~ Packages for Debian, Fedora, openSUSE, and Red Hat Enterprise Linux/CentOS are available from the `openSUSE Build Service <https://software.opensuse.org/download.html?project=shells%3Afish&package=fish>`__. Packages for Ubuntu are available from the `fish PPA <https://launchpad.net/~fish-shell/+archive/ubuntu/release-3>`__, and can be installed using the following commands: :: sudo apt-add-repository ppa:fish-shell/release-3 sudo apt-get update sudo apt-get install fish Instructions for other distributions may be found at `fishshell.com <https://fishshell.com>`__. Windows ~~~~~~~ - On Windows 10, fish can be installed under the WSL Windows Subsystem for Linux with the instructions for the appropriate distribution listed above under “Packages for Linux”, or from source with the instructions below. - Fish can also be installed on all versions of Windows using `Cygwin <https://cygwin.com/>`__ (from the **Shells** category). Building from source ~~~~~~~~~~~~~~~~~~~~ If packages are not available for your platform, GPG-signed tarballs are available from `fishshell.com <https://fishshell.com/>`__ and `fish-shell on GitHub <https://github.com/fish-shell/fish-shell/releases>`__. See the *Building* section for instructions. Running fish ------------ Once installed, run ``fish`` from your current shell to try fish out! Dependencies ~~~~~~~~~~~~ Running fish requires: - curses or ncurses (preinstalled on most \*nix systems) - some common \*nix system utilities (currently ``mktemp``), in addition to the basic POSIX utilities (``cat``, ``cut``, ``dirname``, ``ls``, ``mkdir``, ``mkfifo``, ``rm``, ``sort``, ``tee``, ``tr``, ``uname`` and ``sed`` at least, but the full coreutils plus find, sed and awk is preferred) - The gettext library, if compiled with translation support The following optional features also have specific requirements: - builtin commands that have the ``--help`` option or print usage messages require ``ul`` and either ``nroff`` or ``mandoc`` for display - automated completion generation from manual pages requires Python (2.7+ or 3.3+) and possibly the ``backports.lzma`` module for Python 2.7 - the ``fish_config`` web configuration tool requires Python (2.7+ or 3.3 +) and a web browser - system clipboard integration (with the default Ctrl-V and Ctrl-X bindings) require either the ``xsel``, ``xclip``, ``wl-copy``/``wl-paste`` or ``pbcopy``/``pbpaste`` utilities - full completions for ``yarn`` and ``npm`` require the ``all-the-package-names`` NPM module Switching to fish ~~~~~~~~~~~~~~~~~ If you wish to use fish as your default shell, use the following command: :: chsh -s /usr/local/bin/fish ``chsh`` will prompt you for your password and change your default shell. (Substitute ``/usr/local/bin/fish`` with whatever path fish was installed to, if it differs.) Log out, then log in again for the changes to take effect. Use the following command if fish isn’t already added to ``/etc/shells`` to permit fish to be your login shell: :: echo /usr/local/bin/fish | sudo tee -a /etc/shells To switch your default shell back, you can run ``chsh -s /bin/bash`` (substituting ``/bin/bash`` with ``/bin/tcsh`` or ``/bin/zsh`` as appropriate). Building -------- .. _dependencies-1: Dependencies ~~~~~~~~~~~~ Compiling fish requires: - a C++11 compiler (g++ 4.8 or later, or clang 3.3 or later) - CMake (version 3.2 or later) - a curses implementation such as ncurses (headers and libraries) - PCRE2 (headers and libraries) - a copy is included with fish - gettext (headers and libraries) - optional, for translation support Sphinx is also optionally required to build the documentation from a cloned git repository. Additionally, running the test suite requires python 3.3+ and the pexpect package. Building from source (all platforms) - Makefile generator ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To install into ``/usr/local``, run: .. code:: bash mkdir build; cd build cmake .. make sudo make install The install directory can be changed using the ``-DCMAKE_INSTALL_PREFIX`` parameter for ``cmake``. Building from source (macOS) - Xcode ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. code:: bash mkdir build; cd build cmake .. -G Xcode An Xcode project will now be available in the ``build`` subdirectory. You can open it with Xcode, or run the following to build and install in ``/usr/local``: .. code:: bash xcodebuild xcodebuild -scheme install The install directory can be changed using the ``-DCMAKE_INSTALL_PREFIX`` parameter for ``cmake``. Help, it didn’t build! ~~~~~~~~~~~~~~~~~~~~~~ If fish reports that it could not find curses, try installing a curses development package and build again. On Debian or Ubuntu you want: :: sudo apt-get install build-essential cmake ncurses-dev libncurses5-dev libpcre2-dev gettext On RedHat, CentOS, or Amazon EC2: :: sudo yum install ncurses-devel Contributing Changes to the Code -------------------------------- See the `Guide for Developers <CONTRIBUTING.rst>`__. Contact Us ---------- Questions, comments, rants and raves can be posted to the official fish mailing list at https://lists.sourceforge.net/lists/listinfo/fish-users or join us on our `gitter.im channel <https://gitter.im/fish-shell/fish-shell>`__. Or use the `fish tag on Stackoverflow <https://stackoverflow.com/questions/tagged/fish>`__ for questions related to fish script and the `fish tag on Superuser <https://superuser.com/questions/tagged/fish>`__ for all other questions (e.g., customizing colors, changing key bindings). Found a bug? Have an awesome idea? Please `open an issue <https://github.com/fish-shell/fish-shell/issues/new>`__. .. |Build Status| image:: https://travis-ci.org/fish-shell/fish-shell.svg?branch=master :target: https://travis-ci.org/fish-shell/fish-shell .. |Try in browser| image:: https://cdn.rawgit.com/rootnroll/library/assets/try.svg :target: https://rootnroll.com/d/fish-shell/