Dylan Smith 364d3dbbf8 exec: Don't format status returned directly from builtin function
The builtin function returns the raw status, which is not the same as
the integer return by waitpid. Therefore, the WIF macros shouldn't be
used for checking or obtaining the status.

This bug can be seen by executing (eval false). The builtin eval
function returns 1, but proc_format_status misinterprets it as a signal
by checking WIFSIGNALED, so adds 128 to the status to return 129.

Signed-off-by: Grissiom <chaos.proton@gmail.com>
2010-11-24 00:27:16 +08:00
2010-11-23 23:50:49 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 10:18:26 +08:00
2010-11-23 23:05:21 +08:00
2010-10-05 21:14:43 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 14:31:18 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 09:51:16 +08:00
2005-10-25 01:26:25 +10:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-11-22 08:42:57 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2005-09-20 23:26:39 +10:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 10:18:26 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2005-09-20 23:26:39 +10:00
2010-09-18 09:51:16 +08:00
2010-09-18 09:51:16 +08:00
2005-09-20 23:26:39 +10:00
2005-09-20 23:26:39 +10:00
2010-09-18 09:51:16 +08:00
2005-09-20 23:26:39 +10:00
2010-09-18 10:14:14 +08:00

How to find documentation for fish
==================================

The fish documentation is distributed in an intermediate format. To
view it, you have to type:

  % make user_doc

Which will create the directory user_doc, containing html
documentation for fish. If you build and install fish, the
documentation will be available through the 'help' builtin.

After installation, you can start fish by typing fish in the
terminal. After fish has started, try using the help command for more
information.
Description
The user-friendly command line shell.
Readme 112 MiB
Languages
Rust 71.3%
Shell 19.5%
Python 5.8%
CMake 1.4%
JavaScript 0.5%
Other 1.2%