Patch 16 was for this problem:
Bash waits too long to reap /dev/fd process substitutions used as redirections
with loops and group commands, which can lead to file descriptor exhaustion.
Patch 17 (this one):
There were cases where patch 16 reaped process substitution file descriptors
(or FIFOs) and processes to early. This is a better fix for the problem that
bash50-016 attempted to solve.
probably could do with an update).
Bosh changes (we skipped 2 intermediate releases):
New features with AN-2020-03-11:
- Bourne Shell: set -m now works in scripts as well. Before, bosh did
never call startjobs() when the shell startup was done with a shell
script.
- Bourne Shell: The shell now supports the alternate ;& switch
command limiter in addition to ;; where ;& implements a fallthrough
to the next command list regardless on thether there is a match or not.
New features with AN-2020-03-27:
- Bourne Shell: The case statement now supports the alternate end case
symbol ";;&" that has been introduced by bash. If ";;&" is used instead
of ";;", the next pattern list is evaluated and if there is a match,
the related command list is executed.
New features with AN-2020-04-18:
- Bourne Shell: IRIX has ls(1) installed as /sbin/ls and this caused
some of our unit tests to fail. We now only check for "bin/ls" and
no longer for "/bin/ls" in "type" return messages.
- Bourne Shell/bsh: signames.c has been modified to work correctly if the
number of statically defined realtime signals is odd. This applies to
NetBSD and caused the shells to miss RTMIN+15 on NetBSD.
Thanks to Robert Elz for reporting
- Bourne Shell: A new trap code "ERR" as been introduced. This is modeled
after a feature from ksh88. "trap cmd ERR" causes "cmd" to be called
whenever a command causes a non-zero exit code. The "cmd" is not called
in case that with "set -e" the shell would not exit.
This is not required by POSIX but helpful.
- Bourne Shell: A new set of unit tests for the ERR trap has been added.
- Bourne Shell: An attempt to fix the POSIX behavior for set -e from
October 2018 has been identified to be wrong. If we kept that change,
a list with "set -e; ..." and a failing command would not exit as
expected.
- Bourne Shell: A new piece of code has been added to handle set -e
for function calls.
- Bourne Shell: The man page now better explains the behavior, if in
set -e mode.
- Bourne Shell: print.c::prs_cntl() could cause a buffer overflow with
"unprintable" multi byte UNICODE characters that are printed as list
of octal escape sequences. the buffer overflow happened because there
was only redzone space for one such octal escape sequence.
Thanks to Heiko Eißfeldt for reporting
New features with AN-2020-02-11:
- Bourne Shell: now also using GETOPT_PLUS_FL
- Bourne Shell: A new variable ${.sh.path} returns the absolute path
of the binary associated to the exec() for this shell.
- Bourne Shell: The definition of NUMBUFLEN was moved from print.c to
defs.h to allow others to write into numbuf, knowing it's length.
- Bourne Shell: The archive sh/dotfiles.tar.bz2 now contains an updated
.shrc file that makes use of the new shell variable ${.sh.path}
- Bourne Shell: "for i in; do cmd ...; done" is now valid syntax even
though this is useless, since bosh did already accept:
"for i in $emptyvar ; do cmd ...; done"
But this is in the POSIX standard and other recent shells seem to
accept it.
Thanks to Robert Elz for reporting
- Bourne Shell: Added a new conformance test for the for loop
- Bourne Shell: The call "bosh -version" now prints 2020...
- Bourne Shell Missing features for POSIX compliance:
- Support for $'...' quoting (this is not needed for the current
version of POSIX but for the next POSIX
version that will be named SUSv8).
The development of SUSv8 will start in
late 2016.
We are now expecting the Bourne Shell to be fully POSIX compliant.
- libschily: new man pages starthandlecond.3 and unhandlecond.3
- libschily: handlecond.3 and raisecond.3 now correctly mention
handlecond() & raisecond() instead of handle()/raise(). The old names
from 1980 had to be renamed because os an unfriendly actt from the
C standard commitee.
Thanks to Eric Ackermann for reporting
as a side effect of a code review for SchilliX-ON
- libschily: various small fixes in various man pages from libschily.
Thanks to Eric Ackermann for reporting
as a side effect of a code review for SchilliX-ON
[...]
- Bourne Shell further TODO list:
- Finish loadable builtin support.
- POSIX does not allow us to implement ". -h", so we will
add a "source" builtin to be able to implement "source -h"
- The following builtins (that are available in bsh) are still missing in
the Bourne Shell:
err echo with output going to stderr
glob echo with '\0' instead of ' ' between args
env a builtin version of /usr/bin/env
The following bsh intrinsics are still missing in the Bourne Shell:
- the restricted bsh has restriction features that
are missing in the Bourne shell.
- source -h read file into history but do not execute
and probably more features not yet identified to be bsh unique.
New features with AN-2020-02-11:
- Bourne Shell: now also using GETOPT_PLUS_FL
- Bourne Shell: A new variable ${.sh.path} returns the absolute path
of the binary associated to the exec() for this shell.
- Bourne Shell: The definition of NUMBUFLEN was moved from print.c to
defs.h to allow others to write into numbuf, knowing it's length.
- Bourne Shell: The archive sh/dotfiles.tar.bz2 now contains an updated
.shrc file that makes use of the new shell variable ${.sh.path}
- Bourne Shell: "for i in; do cmd ...; done" is now valid syntax even
though this is useless, since bosh did already accept:
"for i in $emptyvar ; do cmd ...; done"
But this is in the POSIX standard and other recent shells seem to
accept it.
Thanks to Robert Elz for reporting
- Bourne Shell: Added a new conformance test for the for loop
- Bourne Shell: The call "bosh -version" now prints 2020...
- Bourne Shell Missing features for POSIX compliance:
- Support for $'...' quoting (this is not needed for the current
version of POSIX but for the next POSIX
version that will be named SUSv8).
The development of SUSv8 will start in
late 2016.
We are now expecting the Bourne Shell to be fully POSIX compliant.
- libschily: new man pages starthandlecond.3 and unhandlecond.3
- libschily: handlecond.3 and raisecond.3 now correctly mention
handlecond() & raisecond() instead of handle()/raise(). The old names
from 1980 had to be renamed because os an unfriendly actt from the
C standard commitee.
Thanks to Eric Ackermann for reporting
as a side effect of a code review for SchilliX-ON
- libschily: various small fixes in various man pages from libschily.
Thanks to Eric Ackermann for reporting
as a side effect of a code review for SchilliX-ON
[...]
- Bourne Shell further TODO list:
- Finish loadable builtin support.
- POSIX does not allow us to implement ". -h", so we will
add a "source" builtin to be able to implement "source -h"
- The following builtins (that are available in bsh) are still missing in
the Bourne Shell:
err echo with output going to stderr
glob echo with '\0' instead of ' ' between args
env a builtin version of /usr/bin/env
The following bsh intrinsics are still missing in the Bourne Shell:
- the restricted bsh has restriction features that
are missing in the Bourne shell.
- source -h read file into history but do not execute
and probably more features not yet identified to be bsh unique.
Changelog:
Changes between 5.7 and 5.8
Incompatibilities
The history expansion !:1:t2 used to be interpreted such that
the 2 was a separate character added after the history expansion.
Now it is an argument to the :t modifier. The behaviour of :h
has similarly changed.
The vcs_info function VCS_INFO_quilt-dirfind now returns a
string value by setting $REPLY. Previously it printed the value
to standard output.
The cd and chdir builtins no longer interpret operands like -1
and +2 as stack entries when POSIX_CD is enabled.
Dropping privileges with `unsetopt privileged` may fail (with
an error message) on some older and uncommon platforms due to
library dependency changes made in the course of fixing
CVE-2019-20044 (see below). Please report this to the zsh-workers
mailing list if your system is affected.
Changes
CVE-2019-20044: When unsetting the PRIVILEGED option, the shell
sets its effective user and group IDs to match their respective
real IDs. On some platforms (including Linux and macOS, but
not FreeBSD), when the RUID and EUID were both non-zero, it
was possible to regain the shell's former privileges by e.g.
assigning to the EUID or EGID parameter. In the course of
investigating this issue, it was also found that the setopt
built-in did not correctly report errors when unsetting the
option, which prevented users from handling them as the
documentation recommended. setopt now returns non-zero if it
is unable to safely drop privileges. [ Reported by Sam Foxman.]
The zsh/zutil module's zparseopts builtin learnt an -F option
to abort parsing when an unrecognised option-like parameter is
encountered.
The zsh/files module gained a chmod builtin.
Several changes have been made to the way completion functions
track 'precommands' (such as `command` and `env`) and determine
whether the command being completed for is a shell builtin.
Developers of completion functions may wish to familiarise
themselves with `_normal -p` and `_pick_variant -b`.
The option CD_SILENT was added to suppress all output from cd
(whether explicit or implicit with AUTO_CD). It is disabled by
default.
The compadd builtin's -o option now takes an optional argument
to specify the order of completion matches. This affects the
display of candidate matches and the order in which they are
selected when cycling between them using menu completion.
The :h and :t modifiers in parameter expansion (if braces are
present), glob qualifiers and history expansion may take
following decimal digit arguments in order to keep that many
leading or trailing path components instead of the defaults of
all but one (:h) and one (:t). In an absolute path the leading
'/' counts as one component.
The functions builtin gained a -c option to efficiently copy
functions.
The zshmisc(1) manual page incorrectly stated that when 'exit'
is used in a `try' block inside a function, the corresponding
`always' block will be executed. The manual page has been
corrected. The shell's behaviour has not changed.
From Jonathan Schleifer in PR pkg/54965,
lightly changed by myself for netbsd support.
fish 3.1.0 (released February 12, 2020)
Compared to the beta release of fish 3.1b1, fish version 3.1.0:
* fixes a regression where spaces after a brace were removed despite
brace expansion not occurring (#6564)
* fixes a number of problems in compiling and testing on Cygwin (#6549)
and Solaris-derived systems such as Illumos (#6553, #6554, #6555,
#6556, and #6558);
* fixes the process for building macOS packages;
* fixes a regression where excessive error messages are printed if
Unicode characters are emitted in non-Unicode-capable locales
(#6584); and
* contains some improvements to the documentation and a small number of
completions.
If you are upgrading from version 3.0.0 or before, please also review
the release notes for 3.1b1 (included below).
Release notes for fish 3.1b1 (released January 26, 2020)
Notable improvements and fixes
* A new $pipestatus variable contains a list of exit statuses of the
previous job, for each of the separate commands in a pipeline
(#5632).
* fish no longer buffers pipes to the last function in a pipeline,
improving many cases where pipes appeared to block or hang (#1396).
* An overhaul of error messages for builtin commands, including a
removal of the overwhelming usage summary, more readable stack traces
(#3404, #5434), and stack traces for test (aka [) (#5771).
* fish's debugging arguments have been significantly improved. The
--debug-level option has been removed, and a new --debug option
replaces it. This option accepts various categories, which may be listed
via fish --print-debug-categories (#5879). A new --debug-output option
allows for redirection of debug output.
* string has a new collect subcommand for use in command substitutions,
producing a single output instead of splitting on new lines (similar
to "$(cmd)" in other shells) (#159).
* The fish manual, tutorial and FAQ are now available in man format as
fish-doc, fish-tutorial and fish-faq respectively (#5521).
* Like other shells, cd now always looks for its argument in the
current directory as a last resort, even if the CDPATH variable does
not include it or "." (#4484).
* fish now correctly handles CDPATH entries that start with .. (#6220)
or contain ./ (#5887).
* The fish_trace variable may be set to trace execution (#3427). This
performs a similar role as set -x in other shells.
* fish uses the temporary directory determined by the system, rather
than relying on /tmp (#3845).
* The fish Web configuration tool (fish_config) prints a list of
commands it is executing, to help understanding and debugging
(#5584).
* Major performance improvements when pasting (#5866), executing lots
of commands (#5905), importing history from bash (#6295), and when
completing variables that might match $history (#6288).
Syntax changes and new commands
* A new builtin command, time, which allows timing of fish functions
and builtins as well as external commands (#117).
* Brace expansion now only takes place if the braces include a "," or a
variable expansion, meaning common commands such as git reset
HEAD@{0} do not require escaping (#5869).
* New redirections &> and &| may be used to redirect or pipe stdout,
and also redirect stderr to stdout (#6192).
* switch now allows arguments that expand to nothing, like empty
variables (#5677).
* The VAR=val cmd syntax can now be used to run a command in a modified
environment (#6287).
* and is no longer recognised as a command, so that nonsensical
constructs like and and and produce a syntax error (#6089).
* math's exponent operator, '^', was previously left-associative, but
now uses the more commonly-used right-associative behaviour (#6280).
This means that math '3^0.5^2' was previously calculated as
'(3^0.5)^2', but is now calculated as '3^(0.5^2)'.
* In fish 3.0, the variable used with for loops inside command
substitutions could leak into enclosing scopes; this was an
inadvertent behaviour change and has been reverted (#6480).
Scripting improvements
* string split0 now returns 0 if it split something (#5701).
* In the interest of consistency, builtin -q and command -q can now be
used to query if a builtin or command exists (#5631).
* math now accepts --scale=max for the maximum scale (#5579).
* builtin $var now works correctly, allowing a variable as the builtin
name (#5639).
* cd understands the -- argument to make it possible to change to
directories starting with a hyphen (#6071).
* complete --do-complete now also does fuzzy matches (#5467).
* complete --do-complete can be used inside completions, allowing
limited recursion (#3474).
* count now also counts lines fed on standard input (#5744).
* eval produces an exit status of 0 when given no arguments, like other
shells (#5692).
* printf prints what it can when input hasn't been fully converted to a
number, but still prints an error (#5532).
* complete -C foo now works as expected, rather than requiring complete
-Cfoo.
* complete has a new --force-files option, to re-enable file
completions. This allows sudo -E and pacman -Qo to complete correctly
(#5646).
* argparse now defaults to showing the current function name (instead
of argparse) in its errors, making --name often superfluous (#5835).
* argparse has a new --ignore-unknown option to keep unrecognized
options, allowing multiple argparse passes to parse options (#5367).
* argparse correctly handles flag value validation of options that only
have short names (#5864).
* read -S (short option of --shell) is recognised correctly (#5660).
* read understands --list, which acts like --array in reading all
arguments into a list inside a single variable, but is better named
(#5846).
* read has a new option, --tokenize, which splits a string into
variables according to the shell's tokenization rules, considering
quoting, escaping, and so on (#3823).
* read interacts more correctly with the deprecated $IFS variable, in
particular removing multiple separators when splitting a variable
into a list (#6406), matching other shells.
* fish_indent now handles semicolons better, including leaving them in
place for ; and and ; or instead of breaking the line (#5859).
* fish_indent --write now supports multiple file arguments, indenting
them in turn.
* The default read limit has been increased to 100MiB (#5267).
* math now also understands x for multiplication, provided it is
followed by whitespace (#5906).
* math reports the right error when incorrect syntax is used inside
parentheses (#6063), and warns when unsupported logical operations
are used (#6096).
* functions --erase now also prevents fish from autoloading a function
for the first time (#5951).
* jobs --last returns 0 to indicate success when a job is found
(#6104).
* commandline -p and commandline -j now split on && and || in addition
to ; and & (#6214).
* A bug where string split would drop empty strings if the output was
only empty strings has been fixed (#5987).
* eval no long creates a new local variable scope, but affects
variables in the scope it is called from (#4443). source still
creates a new local scope.
* abbr has a new --query option to check for the existence of an
abbreviation.
* Local values for fish_complete_path and fish_function_path are now
ignored; only their global values are respected.
* Syntax error reports now display a marker in the correct position
(#5812).
* Empty universal variables may now be exported (#5992).
* Exported universal variables are no longer imported into the global
scope, preventing shadowing. This makes it easier to change such
variables for all fish sessions and avoids breakage when the value is
a list of multiple elements (#5258).
* A bug where for could use invalid variable names has been fixed
(#5800).
* A bug where local variables would not be exported to functions has
been fixed (#6153).
* The null command (:) now always exits successfully, rather than
passing through the previous exit status (#6022).
* The output of functions FUNCTION matches the declaration of the
function, correctly including comments or blank lines (#5285), and
correctly includes any --wraps flags (#1625).
* type supports a new option, --short, which suppress function
expansion (#6403).
* type --path with a function argument will now output the path to the
file containing the definition of that function, if it exists.
* type --force-path with an argument that cannot be found now correctly
outputs nothing, as documented (#6411).
* The $hostname variable is no longer truncated to 32 characters
(#5758).
* Line numbers in function backtraces are calculated correctly (#6350).
* A new fish_cancel event is emitted when the command line is
cancelled, which is useful for terminal integration (#5973).
Interactive improvements
* New Base16 color options are available through the Web-based
configuration (#6504).
* fish only parses /etc/paths on macOS in login shells, matching the
bash implementation (#5637) and avoiding changes to path ordering in
child shells (#5456). It now ignores blank lines like the bash
implementation (#5809).
* The locale is now reloaded when the LOCPATH variable is changed
(#5815).
* read no longer keeps a history, making it suitable for operations
that shouldn't end up there, like password entry (#5904).
* dirh outputs its stack in the correct order (#5477), and behaves as
documented when universal variables are used for its stack (#5797).
* funced and the edit-commandline-in-buffer bindings did not work in
fish 3.0 when the $EDITOR variable contained spaces; this has been
corrected (#5625).
* Builtins now pipe their help output to a pager automatically (#6227).
* set_color now colors the --print-colors output in the matching colors
if it is going to a terminal.
* fish now underlines every valid entered path instead of just the last
one (#5872).
* When syntax highlighting a string with an unclosed quote, only the
quote itself will be shown as an error, instead of the whole
argument.
* Syntax highlighting works correctly with variables as commands
(#5658) and redirections to close file descriptors (#6092).
* help works properly on Windows Subsytem for Linux (#5759, #6338).
* A bug where disown could crash the shell has been fixed (#5720).
* fish will not autosuggest files ending with ~ unless there are no
other candidates, as these are generally backup files (#985).
* Escape in the pager works correctly (#5818).
* Key bindings that call fg no longer leave the terminal in a broken
state (#2114).
* Brackets (#5831) and filenames containing $ (#6060) are completed
with appropriate escaping.
* The output of complete and functions is now colorized in interactive
terminals.
* The Web-based configuration handles aliases that include single
quotes correctly (#6120), and launches correctly under Termux (#6248)
and OpenBSD (#6522).
* function now correctly validates parameters for --argument-names as
valid variable names (#6147) and correctly parses options following
--argument-names, as in "--argument-names foo --description bar"
(#6186).
* History newly imported from bash includes command lines using && or
||.
* The automatic generation of completions from manual pages is better
described in job and process listings, and no longer produces a
warning when exiting fish (#6269).
* In private mode, setting $fish_greeting to an empty string before
starting the private session will prevent the warning about history
not being saved from being printed (#6299).
* In the interactive editor, a line break (Enter) inside unclosed
brackets will insert a new line, rather than executing the command
and producing an error (#6316).
* Ctrl-C always repaints the prompt (#6394).
* When run interactively from another program (such as Python), fish
will correctly start a new process group, like other shells (#5909).
* Job identifiers (for example, for background jobs) are assigned more
logically (#6053).
* A bug where history would appear truncated if an empty command was
executed was fixed (#6032).
New or improved bindings
* Pasting strips leading spaces to avoid pasted commands being omitted
from the history (#4327).
* Shift-Left and Shift-Right now default to moving backwards and
forwards by one bigword (words separated by whitespace) (#1505).
* The default escape delay (to differentiate between the escape key and
an alt-combination) has been reduced to 30ms, down from 300ms for the
default mode and 100ms for Vi mode (#3904).
* The forward-bigword binding now interacts correctly with
autosuggestions (#5336).
* The fish_clipboard_* functions support Wayland by using
[wl-clipboard](https://github.com/bugaevc/wl-clipboard) (#5450).
* The nextd and prevd functions no longer print "Hit end of history",
instead using a bell. They correctly store working directories
containing symbolic links (#6395).
* If a fish_mode_prompt function exists, Vi mode will only execute it
on mode-switch instead of the entire prompt. This should make it much
more responsive with slow prompts (#5783).
* The path-component bindings (like Ctrl-w) now also stop at ":" and
"@", because those are used to denote user and host in commands such
as ssh (#5841).
* The NULL character can now be bound via bind -k nul. Terminals often
generate this character via control-space. (#3189).
* A new readline command expand-abbr can be used to trigger
abbreviation expansion (#5762).
* A new readline command, delete-or-exit, removes a character to the
right of the cursor or exits the shell if the command line is empty
(moving this functionality out of the delete-or-exit function).
* The self-insert readline command will now insert the binding
sequence, if not empty.
* A new binding to prepend sudo, bound to Alt-S by default (#6140).
* The Alt-W binding to describe a command should now work better with
multiline prompts (#6110)
* The Alt-H binding to open a command's man page now tries to ignore
sudo (#6122).
* A new pair of bind functions, history-prefix-search-backward (and
forward), was introduced (#6143).
* Vi mode now supports R to enter replace mode (#6342), and d0 to
delete the current line (#6292).
* In Vi mode, hitting Enter in replace-one mode no longer erases the
prompt (#6298).
* Selections in Vi mode are inclusive, matching the actual behaviour of
Vi (#5770).
Improved prompts
* The Git prompt in informative mode now shows the number of stashes if
enabled.
* The Git prompt now has an option
($__fish_git_prompt_use_informative_chars) to use the (more modern)
informative characters without enabling informative mode.
* The default prompt now also features VCS integration and will color
the host if running via SSH (#6375).
* The default and example prompts print the pipe status if an earlier
command in the pipe fails.
* The default and example prompts try to resolve exit statuses to
signal names when appropriate.
Improved terminal output
* New fish_pager_color_ options have been added to control more
elements of the pager's colors (#5524).
* Better detection and support for using fish from various system
consoles, where limited colors and special characters are supported
(#5552).
* fish now tries to guess if the system supports Unicode 9 (and
displays emoji as wide), eliminating the need to set
$fish_emoji_width in most cases (#5722).
* Improvements to the display of wide characters, particularly Korean
characters and emoji (#5583, #5729).
* The Vi mode cursor is correctly redrawn when regaining focus under
terminals that report focus (eg tmux) (#4788).
* Variables that control background colors (such as
fish_pager_color_search_match) can now use --reverse.
Completions
* Added completions for
* aws
* bat (#6052)
* bosh (#5700)
* btrfs
* camcontrol
* cf (#5700)
* chronyc (#6496)
* code (#6205)
* cryptsetup (#6488)
* csc and csi (#6016)
* cwebp (#6034)
* cygpath and cygstart (#6239)
* epkginfo (#5829)
* ffmpeg, ffplay, and ffprobe (#5922)
* fsharpc and fsharpi (#6016)
* fzf (#6178)
* g++ (#6217)
* gpg1 (#6139)
* gpg2 (#6062)
* grub-mkrescue (#6182)
* hledger (#6043)
* hwinfo (#6496)
* irb (#6260)
* iw (#6232)
* kak
* keepassxc-cli (#6505)
* keybase (#6410)
* loginctl (#6501)
* lz4, lz4c and lz4cat (#6364)
* mariner (#5718)
* nethack (#6240)
* patool (#6083)
* phpunit (#6197)
* plutil (#6301)
* pzstd (#6364)
* qubes-gpg-client (#6067)
* resolvectl (#6501)
* rg
* rustup
* sfdx (#6149)
* speedtest and speedtest-cli (#5840)
* src (#6026)
* tokei (#6085)
* tsc (#6016)
* unlz4 (#6364)
* unzstd (#6364)
* vbc (#6016)
* zpaq (#6245)
* zstd, zstdcat, zstdgrep, zstdless and zstdmt (#6364)
* Lots of improvements to completions.
* Selecting short options which also have a long name from the
completion pager is possible (#5634).
* Tab completion will no longer add trailing spaces if they already
exist (#6107).
* Completion of subcommands to builtins like and or not now works
correctly (#6249).
* Completion of arguments to short options works correctly when
multiple short options are used together (#332).
* Activating completion in the middle of an invalid completion does not
move the cursor any more, making it easier to fix a mistake (#4124).
* Completion in empty commandlines now lists all available commands.
* Functions listed as completions could previously leak parts of the
function as other completions; this has been fixed.
Deprecations and removed features
* The vcs-prompt functions have been promoted to names without
double-underscore, so __fish_git_prompt is now fish_git_prompt,
__fish_vcs_prompt is now fish_vcs_prompt, __fish_hg_prompt is now
fish_hg_prompt and __fish_svn_prompt is now fish_svn_prompt. Shims at
the old names have been added, and the variables have kept their old
names (#5586).
* string replace has an additional round of escaping in the replacement
expression, so escaping backslashes requires many escapes (eg string
replace -ra '([ab])' '\\\\\\\$1' a). The new feature flag
regex-easyesc can be used to disable this, so that the same effect
can be achieved with string replace -ra '([ab])' '\\\\$1' a (#5556).
As a reminder, the intention behind feature flags is that this will
eventually become the default and then only option, so scripts should
be updated.
* The fish_vi_mode function, deprecated in fish 2.3, has been removed.
Use fish_vi_key_bindings instead (#6372).
For distributors and developers
* fish 3.0 introduced a CMake-based build system. In fish 3.1, both the
Autotools-based build and legacy Xcode build system have been
removed, leaving only the CMake build system. All distributors and
developers must install CMake.
* fish now depends on the common tee external command, for the psub
process substitution function.
* The documentation is now built with Sphinx. The old Doxygen-based
documentation system has been removed. Developers, and distributors
who wish to rebuild the documentation, must install Sphinx.
* The INTERNAL_WCWIDTH build option has been removed, as fish now
always uses an internal wcwidth function. It has a number of
configuration options that make it more suitable for general use
(#5777).
* mandoc can now be used to format the output from --help if nroff is
not installed, reducing the number of external dependencies on
systems with mandoc installed (#5489).
* Some bugs preventing building on Solaris-derived systems such as
Illumos were fixed (#5458, #5461, #5611).
* Completions for npm, bower and yarn no longer require the jq utility
for full functionality, but will use Python instead if it is
available.
* The paths for completions, functions and configuration snippets have
been extended. On systems that define XDG_DATA_DIRS, each of the
directories in this variable are searched in the subdirectories
fish/vendor_completions.d, fish/vendor_functions.d, and
fish/vendor_conf.d respectively. On systems that do not define this
variable in the environment, the vendor directories are searched for
in both the installation prefix and the default "extra" directory,
which now defaults to /usr/local (#5029).
New patches:
12: avoid moving back from oldest history entry to invalid data
13: bug fix for reading history entries with timestamps
14: fix emacs C-xC-e binding so it doesn't edit previous line
if the current one is empty
15: weird aliasing bug with aliases in bash -c command line fixed.
16: earlier clean up of /dev/fd fds used in process substitutions.
Read the patch files for (slightly) expanded information.
pkglint -r --network --only "migrate"
As a side-effect of migrating the homepages, pkglint also fixed a few
indentations in unrelated lines. These and the new homepages have been
checked manually.
pkglint --only "https instead of http" -r -F
With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.
This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.
## v0.6.4
- Fix `vi-forward-char` triggering a bell when using it to accept a suggestion (#488)
- New configuration option to skip completion suggestions when buffer matches a pattern (#487)
- New configuration option to ignore history entries matching a pattern (#456)
Based on Schily Tools Release 2019-12-05.
AN-2019-11-11:
- libschily: the new functions wcastoi wcastol wcastolb that have been
added with the previous release have been forgotten in the linker map
file.
AN-2019-12-05:
- include/schily/stdio.h: We no longer define getc_unlocked() on Solaris
in case that it is defined already. This was needed since Oracle
Solaris 11.4 compiles 64 bit by default and made stdio less opaque
than before - this result in the same bahavior as for 32 bit programs.
This means, we no longer need to use tricks to get fast access to
stdio.
Thanks to Rolf Dietze for reporting.
- libschily: the function getargs() and similar (from the option parser
group) fixed a bug that prevented the usability of the official method
to include the char '+' inside option names by quoting the character
in the option name used in the format string.
This bug has been fixed in order to be able to support "star -dump+ ..."
- libshedit: because of the changes in Oracle Solaris 11.4, we need to
#undef FAST_GETC_PUTC in order to avoid to use getc_unlocked().
Thanks to Rolf Dietze for reporting.
- Bourne Shell/bsh: */hashcmd.c did not handle a malloc()ed string
correctly and could cause a memory leak with hash commands that
do not add new aliases.
We now create a copy using make()/makestr() before calling ab_push()
or ab_insert() and always free "name" at the end of the function
hashcmd()
- Bourne Shell: The man page now documents that the command
"set -o hashcmds"
inside the file $HOME/.shrc makes a # on the fist column of that
file and followed by a non-space character, no longer a comment..
It is thus recommended to have "set -o hashcmds" close to the.
bottom of the file $HOME/.shrc
Based on Schily Tools Release 2019-12-05.
AN-2019-11-11:
- libschily: the new functions wcastoi wcastol wcastolb that have been
added with the previous release have been forgotten in the linker map
file.
AN-2019-12-05:
- include/schily/stdio.h: We no longer define getc_unlocked() on Solaris
in case that it is defined already. This was needed since Oracle
Solaris 11.4 compiles 64 bit by default and made stdio less opaque
than before - this result in the same bahavior as for 32 bit programs.
This means, we no longer need to use tricks to get fast access to
stdio.
Thanks to Rolf Dietze for reporting.
- libschily: the function getargs() and similar (from the option parser
group) fixed a bug that prevented the usability of the official method
to include the char '+' inside option names by quoting the character
in the option name used in the format string.
This bug has been fixed in order to be able to support "star -dump+ ..."
- libshedit: because of the changes in Oracle Solaris 11.4, we need to
#undef FAST_GETC_PUTC in order to avoid to use getc_unlocked().
Thanks to Rolf Dietze for reporting.
- Bourne Shell/bsh: */hashcmd.c did not handle a malloc()ed string
correctly and could cause a memory leak with hash commands that
do not add new aliases.
We now create a copy using make()/makestr() before calling ab_push()
or ab_insert() and always free "name" at the end of the function
hashcmd()
- Bourne Shell: The man page now documents that the command
"set -o hashcmds"
inside the file $HOME/.shrc makes a # on the fist column of that
file and followed by a non-space character, no longer a comment..
It is thus recommended to have "set -o hashcmds" close to the.
bottom of the file $HOME/.shrc
Changes:
6.22.02 - 20191204
------------------
Fix version in configure.ac
6.22.01 - 20191201
------------------
undo PR/88: Preserve empty arguments in :q, since it breaks
$ set x=""
$ alias test "echo "\""$x:q"\"" is working."
$ alias test
echo "
pkgsrc changes:
- Remove no longer needed patches (both backport from upstream to 6.21.00)
Changes:
V6.22.00 - 20191128
-------------------
- PR/113: Sobomax: avoid infinite loops for -c commands when stdout is
not a tty.
- Avoid infinite loops during history loads when merging, print a better
error for errors during history load.
- PR/88: Preserve empty arguments in :q
- PR/94: Small apple issues (SAVESIGVEC, HOSTTYPE)
- PR/81: Fix range matching issue where we were comparing with the
range character instead of the start of range. [l-z]* would match foo
## v0.6.3
- Fixed bug moving cursor to end of buffer after accepting suggestion (#453)
## v0.6.2
- Fixed bug deleting the last character in the buffer in vi mode (#450)
- Degrade gracefully when user doesn't have `zsh/system` module installed (#447)
## v0.6.1
- Fixed bug occurring when `_complete` had been aliased (#443)
## v0.6.0
- Added `completion` suggestion strategy powered by completion system (#111)
- Allow setting `ZSH_AUTOSUGGEST_BUFFER_MAX_SIZE` to an empty string (#422)
- Don't fetch suggestions after copy-earlier-word (#439)
- Allow users to unignore zle-\* widgets (e.g. zle-line-init) (#432)
Gash is a POSIX-compatible shell written in Guile Scheme. It provides
both the shell interface, as well as a Guile library for parsing shell
scripts. Gash is designed to bootstrap Bash as part of the Guix
bootstrap process. There are plans to develop Gash into a
general-purpose shell and tool for building interfaces between Scheme
and the shell.
Features of the shell
* Sophisticated enough to be used to build Bash.
* Has a nice colorized prompt.
* Includes all of the POSIX-specified "special" built-ins except for
`times'.
* Includes about half of the POSIX-specified "regular" built-ins
(see `gash/built-ins.scm' for details).
Features of the programming interface
* Parses Shell scripts into an AST.
* Provides a rudimentary interface for writing Shell-like Scheme
scripts.
# fish 3.0.2 (released February 19, 2019)
This release of fish fixes an issue discovered in fish 3.0.1.
### Fixes and improvements
- The PWD environment variable is now ignored if it does not resolve to the true working directory, fixing strange behaviour in terminals started by editors and IDEs (#5647).
If you are upgrading from version 2.7.1 or before, please also review the release notes for 3.0.1, 3.0.0 and 3.0b1 (included below).
---
# fish 3.0.1 (released February 11, 2019)
This release of fish fixes a number of major issues discovered in fish 3.0.0.
### Fixes and improvements
- `exec` does not complain about running foreground jobs when called (#5449).
- while loops now evaluate to the last executed command in the loop body (or zero if the body was empty), matching POSIX semantics (#4982).
- `read --silent` no longer echoes to the tty when run from a non-interactive script (#5519).
- On macOS, path entries with spaces in `/etc/paths` and `/etc/paths.d` now correctly set path entries with spaces. Likewise, `MANPATH` is correctly set from `/etc/manpaths` and `/etc/manpaths.d` (#5481).
- fish starts correctly under Cygwin/MSYS2 (#5426).
- The `pager-toggle-search` binding (Ctrl-S by default) will now activate the search field, even when the pager is not focused.
- The error when a command is not found is now printed a single time, instead of once per argument (#5588).
- Fixes and improvements to the git completions, including printing correct paths with older git versions, fuzzy matching again, reducing unnecessary offers of root paths (starting with `:/`) (#5578, #5574, #5476), and ignoring shell aliases, so enterprising users can set up the wrapping command (via `set -g __fish_git_alias_$command $whatitwraps`) (#5412).
- Significant performance improvements to core shell functions (#5447) and to the `kill` completions (#5541).
- Starting in symbolically-linked working directories works correctly (#5525).
- The default `fish_title` function no longer contains extra spaces (#5517).
- The `nim` prompt now works correctly when chosen in the Web-based configuration (#5490).
- `string` now prints help to stdout, like other builtins (#5495).
- Killing the terminal while fish is in vi normal mode will no longer send it spinning and eating CPU. (#5528)
- A number of crashes have been fixed (#5550, #5548, #5479, #5453).
- Improvements to the documentation and certain completions.
### Known issues
There is one significant known issue that was not corrected before the release:
- fish does not run correctly under Windows Services for Linux before Windows 10 version 1809/17763, and the message warning of this may not be displayed (#5619).
If you are upgrading from version 2.7.1 or before, please also review the release notes for 3.0.0 and 3.0b1 (included below).
Based on schilytools release from 2019-10-25.
Changelog
=========
- include/schily/wchar.h: Some fallback definitions for
mbsinit() mbrtowc() wcrtomb() have been moved to make them always
visible and not only in case that <wchar.h> exists.
- include/schily/wchar.h: Before, we checked for HAVE_ISWPRINT to catch
the HP-UX-10.20 case where wchar_t is in stdlib.h. Now we check
(SIZEOF_WCHAR == 0 || SIZEOF_WCHAR_T == 0) as this works on Ultrix as
well.
- libgetopt: The getopt() function now supports options in the form:
+o, ++long-option or +long-option
if the optstring starts with a '+'. A new exported variable
"optflags" has the bit "OPT_PLUS" set, in case that an actual option
starts with '+'.
If more than one of the flag characters ':', '+' or "()" are used,
"()" must be last.
- Bourne Shell: The testsuite no longer tries to check ISO-8859-1 strings
as we cannot set this up reliably on all platforms and as Mac OS does
not allow to create the related filenames.
- Bourne Shell: The getopts(1) builtin command now supports options in.
the form:
+o, ++long-option or +long-option
if the optstring starts with a '+'. The shell variable "$NAME" has
a leading '+' in case that an actual option starts with '+'.
Note that this makes getopts(1) in the Bourne Shell compatible at
shell script level to the extensions in the getopts(1) implementation
in ksh93 for:
-o/+o Short options with either a leading - or +
--long GNU style long options as aliases to short -o options
++long GNU style long options as aliases to short +o options
Our enhancements to support:
-long UNIX style long options as aliases to short -o options
+long UNIX style long options as aliases to short +o options
- Long options the have no related short option
Are not supported by ksh93.
Based on schilytools release from 2019-10-25.
Changelog
=========
- include/schily/wchar.h: Some fallback definitions for
mbsinit() mbrtowc() wcrtomb() have been moved to make them always
visible and not only in case that <wchar.h> exists.
- include/schily/wchar.h: Before, we checked for HAVE_ISWPRINT to catch
the HP-UX-10.20 case where wchar_t is in stdlib.h. Now we check
(SIZEOF_WCHAR == 0 || SIZEOF_WCHAR_T == 0) as this works on Ultrix as
well.
- libgetopt: The getopt() function now supports options in the form:
+o, ++long-option or +long-option
if the optstring starts with a '+'. A new exported variable
"optflags" has the bit "OPT_PLUS" set, in case that an actual option
starts with '+'.
If more than one of the flag characters ':', '+' or "()" are used,
"()" must be last.
- Bourne Shell: The testsuite no longer tries to check ISO-8859-1 strings
as we cannot set this up reliably on all platforms and as Mac OS does
not allow to create the related filenames.
- Bourne Shell: The getopts(1) builtin command now supports options in.
the form:
+o, ++long-option or +long-option
if the optstring starts with a '+'. The shell variable "$NAME" has
a leading '+' in case that an actual option starts with '+'.
Note that this makes getopts(1) in the Bourne Shell compatible at
shell script level to the extensions in the getopts(1) implementation
in ksh93 for:
-o/+o Short options with either a leading - or +
--long GNU style long options as aliases to short -o options
++long GNU style long options as aliases to short +o options
Our enhancements to support:
-long UNIX style long options as aliases to short -o options
+long UNIX style long options as aliases to short +o options
- Long options the have no related short option
Are not supported by ksh93.
Based on SchilyTools Release from 2019-10-07.
Changelog
=========
- configure: Some shells report a syntax error with "< file (cmd)"
and need the redirection statement to be *after* the command. Our
changes to support the V7 shell by adding round braces caused ash
variants like "dash" to fail.
Thanks to Harald van Dijk for reporting
- cont/cc-config.sh: canged some :>some-file statements into
(:)>some-file. they have meen missed when introducing work arounds
for the V7 Shell on Ultrix that does not support I/O redirection
for builtin commands.
Thanks to Robert Clausecker for reporting
- libschily/comerr.c: If the environment COMERR_EXCODE has been set to
a value that starts with '0', the normal exit code mapping is switched
off, but all potential exit code values != 0 that follow the rule
(excode % 256) == 0
are mapped to -64. This helps to avoid unexpected behavior with
historic shells that still use the old waitpid() and modern
shells (using waitid() but in a backward compatible default mode)
where a program that terminates with
exit(256);
is evaluated in conditional statements as if the exit code was 0.
- Bourne Shell: Missing Makefile.dot added.
- Bourne Shell / bsh / ved: The dotdiles TAR archives are now again named
*/dotfiles.tar.bz2 as the change in the previous release caused
problems.
Thanks for Gabriele Balducci balducci@units.it and Robert Clausecker
for reporting
- Bourne Shell: Cstyle changes (long lines removed) in io.c & expand.c
- Bourne Shell: Fixed a bug that prevented to forward the special exit
cause (NOTFOUND or NOEXEC) to the vfork() parent process via.
struct siginfo.si_code in some cases. These values are added beyond
the POSIX CLD_* values in siginfo.si_code from the POSIX standard.
They are passed back from the vfork()ed child to the parent via the
shared memory from the vfork() implementation.
- Bourne Shell: introduced shared memory to be able to forward the
special exit cause (NOTFOUND or NOEXEC) to the parent even in case it
used fork() instead of vfork().
- Bourne Shell: Added support for a new automatic parameter "$/" to
complement the existing parameter "$?".
This is a result from a discussion in a POSIX teleconference from
April 2016.
This new parameter returns *decimal numbers* for a normal command
termination and *text* for abnormal command termination:
number<>Exit code from normal termination. This is a signed 32 bit
value from the exit() parameter on POSIX systems and a 8 bit
value on pre-POSIX systems like Linux.
signame>A signal name (see kill -l) if the command has been terminated
by a signal. This is the signal name with the leading "SIG"
stripped off.
NOEXEC<>The command was found but could not be executed, e.g. as
a result of missing permissions or because the name points
to a directory.
NOTFOUND The command could not be found.
Note that currently, the strings "NOEXEC" and "NOTFOUND" are passed
back reliably from vfork(2) childs or when the related state is already
known by the cache. In other cases, the reliability of $/ with respect
to "NOEXEC" and "NOTFOUND" has not yet been verified. It thus may
return 126 or 127 as with $?. The string values "NOEXEC" and "NOTFOUND"
cannot be passed back from a subshell, using only the waitid()
mechanism. To circumvent that problem, from fork()ed subshells,.
shared memory or non-fork()ed virtual subshells would work.
If you detect a complex command where you get 126 or 127 instead of
the exoected "NOEXEC" or "NOTFOUND", please send a report.
We for now choose to use shared memory as this is easier to implement.
Later versions will mosy likely implement virtual fork()less
subshells.
- Bourne Shell: minor Cstyle changes on word.c and macro.c
- Bourne Shell: New version date
Based on SchilyTools Release from 2019-10-07.
Changelog
=========
- configure: Some shells report a syntax error with "< file (cmd)"
and need the redirection statement to be *after* the command. Our
changes to support the V7 shell by adding round braces caused ash
variants like "dash" to fail.
Thanks to Harald van Dijk for reporting
- cont/cc-config.sh: canged some :>some-file statements into
(:)>some-file. they have meen missed when introducing work arounds
for the V7 Shell on Ultrix that does not support I/O redirection
for builtin commands.
Thanks to Robert Clausecker for reporting
- libschily/comerr.c: If the environment COMERR_EXCODE has been set to
a value that starts with '0', the normal exit code mapping is switched
off, but all potential exit code values != 0 that follow the rule
(excode % 256) == 0
are mapped to -64. This helps to avoid unexpected behavior with
historic shells that still use the old waitpid() and modern
shells (using waitid() but in a backward compatible default mode)
where a program that terminates with
exit(256);
is evaluated in conditional statements as if the exit code was 0.
- Bourne Shell: Missing Makefile.dot added.
- Bourne Shell / bsh / ved: The dotdiles TAR archives are now again named
*/dotfiles.tar.bz2 as the change in the previous release caused
problems.
Thanks for Gabriele Balducci balducci@units.it and Robert Clausecker
for reporting
- Bourne Shell: Cstyle changes (long lines removed) in io.c & expand.c
- Bourne Shell: Fixed a bug that prevented to forward the special exit
cause (NOTFOUND or NOEXEC) to the vfork() parent process via.
struct siginfo.si_code in some cases. These values are added beyond
the POSIX CLD_* values in siginfo.si_code from the POSIX standard.
They are passed back from the vfork()ed child to the parent via the
shared memory from the vfork() implementation.
- Bourne Shell: introduced shared memory to be able to forward the
special exit cause (NOTFOUND or NOEXEC) to the parent even in case it
used fork() instead of vfork().
- Bourne Shell: Added support for a new automatic parameter "$/" to
complement the existing parameter "$?".
This is a result from a discussion in a POSIX teleconference from
April 2016.
This new parameter returns *decimal numbers* for a normal command
termination and *text* for abnormal command termination:
number<>Exit code from normal termination. This is a signed 32 bit
value from the exit() parameter on POSIX systems and a 8 bit
value on pre-POSIX systems like Linux.
signame>A signal name (see kill -l) if the command has been terminated
by a signal. This is the signal name with the leading "SIG"
stripped off.
NOEXEC<>The command was found but could not be executed, e.g. as
a result of missing permissions or because the name points
to a directory.
NOTFOUND The command could not be found.
Note that currently, the strings "NOEXEC" and "NOTFOUND" are passed
back reliably from vfork(2) childs or when the related state is already
known by the cache. In other cases, the reliability of $/ with respect
to "NOEXEC" and "NOTFOUND" has not yet been verified. It thus may
return 126 or 127 as with $?. The string values "NOEXEC" and "NOTFOUND"
cannot be passed back from a subshell, using only the waitid()
mechanism. To circumvent that problem, from fork()ed subshells,.
shared memory or non-fork()ed virtual subshells would work.
If you detect a complex command where you get 126 or 127 instead of
the exoected "NOEXEC" or "NOTFOUND", please send a report.
We for now choose to use shared memory as this is easier to implement.
Later versions will mosy likely implement virtual fork()less
subshells.
- Bourne Shell: minor Cstyle changes on word.c and macro.c
- Bourne Shell: New version date
Changelog
=========
Release 2019-03-29:
- Bourne Shell: local(1), export(1) and readonly(1) now all support to.
expand the '~' character in environment variables like e.g. PATH.
- Bourne Shell: Added unit tests for the tilde expansion and the related
changes.
Release 2019-04-29:
- libshedit/bsh/Bourne Shell: The TAB file name expansion now uses a new
expansion funtion that is not based on pattern matching but on strstr()
and thus is no longer fooled by file names that contain pattern matching
meta characters.
- Bourne Shell: "trap -- ..." now correctly handles "--" even if the next
argument is "-".
- Bourne Shell: trap now supports a new option -p that allows to restore
the whole trap state using the following commands:
old_traps=$(trap -p)
trap "some commands" INT QUIT
...
eval "$old_traps"
This is possible because "trap -p" outputs the state for all signals
and not only for those signals that are not in the default state.
The new trap interfase was agreed on in the 2019-04-11 POSIX
teleconference.
Bourne Shell: The exception for "while true; do date; done | uniq -c"
in job control handling that has been introduced in November 2015 has
been refined to prevent it from causing "(bosh)" to stop from SIGTTIN.
Thanks to Robert Elz <kre@munnari.OZ.AU> for reporting.
- Bourne Shell: A new #define JOB_DEBUG has been added.
- Bourne Shell: The command:
(trap '' SEGV; $SHELL -c 'kill -s SEGV $$; echo survived')
caused the shell not to print "survived" because a previous exception
for SIGSEGV from the 1977 Bourne Shell version had not been removed
for the POSIX variant of the shell. The problem occured because it
was possible to unignore an ignored (at startup) SIGSEGV.
Thanks to Robert Elz <kre@munnari.OZ.AU> for reporting.
- Bourne Shell: The code now uses SIG2STR_MAX for the size of the
sig2str() output buffer.
- Bourne Shell: the behavior related to SIGINT on the command line
in the case that the history editor is enabled has been changed to
match the behavior of ksh. The Bourne Shell now calls trap commands
for SIGINT when ^C is typed on the command line.
Note that the classical Bourne Shell behavior (which is still active
in case the history editor has been disabled via "set +o ved") is that
the trap command is called after ^C is followed by a CR if both are
typed on a PS1 prompt.
Note: The behavior for "trap" in this area is currently not specified
in POSIX.
- Bourne Shell: After jobcontrol has been introduced into the Bourne
Shell: When in jobcontrol mode, the shell could no longer get
signals at the same time as foreground jobs because when using
jobcontrol, the shell is in a different process group than the
foreground job.
The Bourne Shell now derives the information about a delivered signal
from the waitid() return data and thus is now able to work the same
way as it has been designed in 1977. This is the same way as ksh works.
If a foreground program catches such signals, the shell is still not
able to detect the signal, but it is now closer to the original
behavior from 1977.
- Bourne Shell: new version date 2019-04-17
Release 2019-05-28:
- Bourne Shell: Similar to what ksh88 does, scripts are now checked
before they are run. If there is a nul byte before a newline
in the first 256 bytes, a file is rejected as alien binary
instead of trying to interpret it as a script.
Release 2019-06-13:
- Bourne Shell: A new option "set -o globskipdot" has been added.
If set, the entries "." and ".." are skipped and not shown in globbing
results. If not set, the entries "." and ".." are always returned,
even when they are not part of the readdir(3) results.
- Bourne Shell: The option "set -o globskipdot" has been made the
new dfault behavior for "bosh", but not for "pbosh"
Note that this new shell option has been introduced as a result
of a related BUG discussion in the Austin Group telephone conference.
The background is to permit shell scripts to check whether a shell
grants to hide the "." and ".." for all filesystems.
Release 2019-07-15:
- Bourne Shell: If OPTIND is set to a new value, the getopt() internal
variable "_sp" is now reset to 1. This is needed in order to make sure
that a combined option string can be parsed correctly.
- Bourne Shell/libshedit/bsh: The TAB expander now again gives .. as a.
result if the pattern is ..
This is needed in order to let ..TAB result in ../ on the command
line editor.
Release 2019-09-22:
- Bourne Shell: The new function isbinary() that has been introduced
in May and that should prevent the shell from interpreting binary
files as shell scripts had a problem:
In case that a disconnected TCP/IP based remote login caused a SIGTERM
followed by the read() function on stdin returning EIO, the shell
could go into a complex endless loop as the failing read() with
"trapnote" set caused a longjmp() before the next prompt without first
clearing "trapnote". As a result, the shell did hang endlessly around
while just consuming CPU time.
The shell now avoids to call the read() routine inside isbinary()
when "trapnote" is set and this way is able to avoid the longjmp() on
error.
- Bourne Shell: Fixed some typos in comment
Thanks to Robert Clausecker for reporting
- Bourne Shell: print.c: Changed err++ for a BOOL typed variable
into err = TRUE.
Thanks to Robert Clausecker for reporting
- Bourne Shell, with obosh compilation type: Avoid an "unused" warning
with word.c
- Bourne Shell: defs.h now includes an "extern int optopt;" in order
to support Ultrix where this delcaration is missing in unistd.h.
Thanks to Robert Clausecker for reporting
- bsh/Bourne Shell: test.c Now using a
#if defined(S_IFPORT) && S_IFPORT != S_IFIFO
to work around a strange definition on Ultrix
Thanks to Robert Clausecker for reporting
- Bourne Shell: New version date
Changelog
=========
Release 2019-03-29:
- Bourne Shell: local(1), export(1) and readonly(1) now all support to.
expand the '~' character in environment variables like e.g. PATH.
- Bourne Shell: Added unit tests for the tilde expansion and the related
changes.
Release 2019-04-29:
- libshedit/bsh/Bourne Shell: The TAB file name expansion now uses a new
expansion funtion that is not based on pattern matching but on strstr()
and thus is no longer fooled by file names that contain pattern matching
meta characters.
- Bourne Shell: "trap -- ..." now correctly handles "--" even if the next
argument is "-".
- Bourne Shell: trap now supports a new option -p that allows to restore
the whole trap state using the following commands:
old_traps=$(trap -p)
trap "some commands" INT QUIT
...
eval "$old_traps"
This is possible because "trap -p" outputs the state for all signals
and not only for those signals that are not in the default state.
The new trap interfase was agreed on in the 2019-04-11 POSIX
teleconference.
Bourne Shell: The exception for "while true; do date; done | uniq -c"
in job control handling that has been introduced in November 2015 has
been refined to prevent it from causing "(bosh)" to stop from SIGTTIN.
Thanks to Robert Elz <kre@munnari.OZ.AU> for reporting.
- Bourne Shell: A new #define JOB_DEBUG has been added.
- Bourne Shell: The command:
(trap '' SEGV; $SHELL -c 'kill -s SEGV $$; echo survived')
caused the shell not to print "survived" because a previous exception
for SIGSEGV from the 1977 Bourne Shell version had not been removed
for the POSIX variant of the shell. The problem occured because it
was possible to unignore an ignored (at startup) SIGSEGV.
Thanks to Robert Elz <kre@munnari.OZ.AU> for reporting.
- Bourne Shell: The code now uses SIG2STR_MAX for the size of the
sig2str() output buffer.
- Bourne Shell: the behavior related to SIGINT on the command line
in the case that the history editor is enabled has been changed to
match the behavior of ksh. The Bourne Shell now calls trap commands
for SIGINT when ^C is typed on the command line.
Note that the classical Bourne Shell behavior (which is still active
in case the history editor has been disabled via "set +o ved") is that
the trap command is called after ^C is followed by a CR if both are
typed on a PS1 prompt.
Note: The behavior for "trap" in this area is currently not specified
in POSIX.
- Bourne Shell: After jobcontrol has been introduced into the Bourne
Shell: When in jobcontrol mode, the shell could no longer get
signals at the same time as foreground jobs because when using
jobcontrol, the shell is in a different process group than the
foreground job.
The Bourne Shell now derives the information about a delivered signal
from the waitid() return data and thus is now able to work the same
way as it has been designed in 1977. This is the same way as ksh works.
If a foreground program catches such signals, the shell is still not
able to detect the signal, but it is now closer to the original
behavior from 1977.
- Bourne Shell: new version date 2019-04-17
Release 2019-05-28:
- Bourne Shell: Similar to what ksh88 does, scripts are now checked
before they are run. If there is a nul byte before a newline
in the first 256 bytes, a file is rejected as alien binary
instead of trying to interpret it as a script.
Release 2019-06-13:
- Bourne Shell: A new option "set -o globskipdot" has been added.
If set, the entries "." and ".." are skipped and not shown in globbing
results. If not set, the entries "." and ".." are always returned,
even when they are not part of the readdir(3) results.
- Bourne Shell: The option "set -o globskipdot" has been made the
new dfault behavior for "bosh", but not for "pbosh"
Note that this new shell option has been introduced as a result
of a related BUG discussion in the Austin Group telephone conference.
The background is to permit shell scripts to check whether a shell
grants to hide the "." and ".." for all filesystems.
Release 2019-07-15:
- Bourne Shell: If OPTIND is set to a new value, the getopt() internal
variable "_sp" is now reset to 1. This is needed in order to make sure
that a combined option string can be parsed correctly.
- Bourne Shell/libshedit/bsh: The TAB expander now again gives .. as a.
result if the pattern is ..
This is needed in order to let ..TAB result in ../ on the command
line editor.
Release 2019-09-22:
- Bourne Shell: The new function isbinary() that has been introduced
in May and that should prevent the shell from interpreting binary
files as shell scripts had a problem:
In case that a disconnected TCP/IP based remote login caused a SIGTERM
followed by the read() function on stdin returning EIO, the shell
could go into a complex endless loop as the failing read() with
"trapnote" set caused a longjmp() before the next prompt without first
clearing "trapnote". As a result, the shell did hang endlessly around
while just consuming CPU time.
The shell now avoids to call the read() routine inside isbinary()
when "trapnote" is set and this way is able to avoid the longjmp() on
error.
- Bourne Shell: Fixed some typos in comment
Thanks to Robert Clausecker for reporting
- Bourne Shell: print.c: Changed err++ for a BOOL typed variable
into err = TRUE.
Thanks to Robert Clausecker for reporting
- Bourne Shell, with obosh compilation type: Avoid an "unused" warning
with word.c
- Bourne Shell: defs.h now includes an "extern int optopt;" in order
to support Ultrix where this delcaration is missing in unistd.h.
Thanks to Robert Clausecker for reporting
- bsh/Bourne Shell: test.c Now using a
#if defined(S_IFPORT) && S_IFPORT != S_IFIFO
to work around a strange definition on Ultrix
Thanks to Robert Clausecker for reporting
- Bourne Shell: New version date
10: fix var-assigns before special builtins & fn calls in posix mode
11: fixed missing quoted nul removal (in one odd case).
See the patch files (once fetched) for more details of what was altered.
Note release version goes backwards. Version now follows openbsd version
numbering.
No changes available.
Patched to eliminate compilation warnings on netbsd.
When $HOME environment variable is set, e.g. in pkgrsc where a fake
homedir is injected, ~ is expanded to $HOME while ~user is expanded
to the passwd(5) home_dir field leading to inconsistency in the test.
No PKGREVISION bump since that change only affects tests.
pkgsrc changes:
- Add patch-nls_Makefile.in to avoid +x bit in *.cat files
- Remove no longer needed patches (all applied upstream):
patch-ed.chared.c, patch-ed.inputl.c, patch-nls-catgen, patch-sh.func.c,
patch-tw.init.c
Changes:
V6.21.00 - 20190508
-------------------
- Abort history loading on words and lines too long
https://bugzilla.redhat.com/show_bug.cgi?id=1598502
- PR/37: Introduce GetCmdChar() to avoid open coding array access.
make closem() not close sockets so as not to affect nss_ldap.
tcsh never creates sockets so that's ok (Miloslav Trmac)
- PR/597: Make rmstar work with aliased rm
- convert match() from recursive to backtracking.
- Handle 8 bit characters in bindkey (Werner Fink)
- Look for tgetent in libtinfo as well (Werner Fink)
- Don't play pointer tricks that are undefined in modern c (Brooks Davis)
- Fix out of bounds read (Brooks Davis)
- Fix type of read in prompt confirmation (eg. rmstar) (David Kaspar)
- PR/471: Delay arginp parsing
ok <kim>, thanks!
