Revision tags: release/13.5.0, release/14.2.0-p2, release/14.1.0-p8, release/13.4.0-p4, release/14.1.0-p7, release/14.2.0-p1, release/13.4.0-p3, release/14.2.0, release/13.4.0, release/14.1.0 |
|
#
7bd8da72 |
| 03-May-2024 |
Michael Osipov <michaelo@FreeBSD.org> |
sh(1): Replace recommendation of use of -e with a note
This partially reverts b14cfdf665bb8b7b2898a4ee5b073ab87f8ea3d0 and has been discussed in D42719.
Reviewed by: jrm (mentor), otis (mentor), ma
sh(1): Replace recommendation of use of -e with a note
This partially reverts b14cfdf665bb8b7b2898a4ee5b073ab87f8ea3d0 and has been discussed in D42719.
Reviewed by: jrm (mentor), otis (mentor), mandree, ziaee (manpages) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D45073
show more ...
|
#
2980318b |
| 22-Feb-2025 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
sh.1: extend the section about getopts
Provide more details about the influence of optargs' first character on the shell's behavior in regard to invalid arguments. Also do some minor word-smithing.
sh.1: extend the section about getopts
Provide more details about the influence of optargs' first character on the shell's behavior in regard to invalid arguments. Also do some minor word-smithing.
Original submission by rea@
Differential Revision: https://reviews.freebsd.org/D49106
show more ...
|
#
f4727eca |
| 09-Jan-2025 |
Alexander Ziaee <ziaee@FreeBSD.org> |
sh.1: document optional arguments to `:`
TIL the `:` command accepts and discards arguments, and this is occasionally used to embed comments in interesting places. While here, fix another `...` argu
sh.1: document optional arguments to `:`
TIL the `:` command accepts and discards arguments, and this is occasionally used to embed comments in interesting places. While here, fix another `...` argument that was not marked up.
MFC after: 3 days Thanks: Community Discord Approved by: carlavilla, mhorne (mentors) Differential Revision: https://reviews.freebsd.org/D48398
show more ...
|
#
e2a72442 |
| 29-Sep-2024 |
Alexander Ziaee <concussious@runbox.com> |
sh.1: update history + spdx + linter error
+ increase history consistency by adding "first appeared" + remove a skipped new paragraph macro to quiet linter + tag spdx
MFC after: 3 days History sour
sh.1: update history + spdx + linter error
+ increase history consistency by adding "first appeared" + remove a skipped new paragraph macro to quiet linter + tag spdx
MFC after: 3 days History source: www.in-ulm.de/~mascheck/various/ash/#bsd
Reviewed by: mhorne,imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1440
show more ...
|
#
65f5dd42 |
| 20-Nov-2024 |
Baptiste Daroussin <bapt@FreeBSD.org> |
sh(1): add -l option
-l is required by LSB for login shell, all other shells: bash, zsh, oksh, mksh, ... implements it.
with -l sh will act as a login shell and read the profile.
MFC After: 1 wee
sh(1): add -l option
-l is required by LSB for login shell, all other shells: bash, zsh, oksh, mksh, ... implements it.
with -l sh will act as a login shell and read the profile.
MFC After: 1 week Obtained From: dash (3b7c8442bfe7c2fd0a6b0415df6ddf66a399fd55) Reviewed by: kib, lme Differential Revision: https://reviews.freebsd.org/D47681
show more ...
|
#
c013ca2c |
| 24-Sep-2024 |
Graham Percival <gperciva@tarsnap.com> |
manuals: Fix typos in -offset for .Bd and .Bl
The intended value is: -offset indent If there's any typo such that the value doesn't match the pre-defined strings, then the offset is the same wid
manuals: Fix typos in -offset for .Bd and .Bl
The intended value is: -offset indent If there's any typo such that the value doesn't match the pre-defined strings, then the offset is the same width as the value. So by chance, "-offset -ident" ended up being a standard-width indent (since the default indent is 6 chars, and "-ident" also has 6 chars), whereas "-offset -indent" had a longer indent, and "-offset ident" had a shorter one.
Signed-off-by: Graham Percival <gperciva@tarsnap.com> Reviewed by: mhorne, Alexander Ziaee <concussious.bugzilla@runbox.com> MFC after: 3 days Sponsored by: Tarsnap Backup Inc. Pull Request: https://github.com/freebsd/freebsd-src/pull/1436
show more ...
|
Revision tags: release/13.3.0 |
|
#
90aea514 |
| 23-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
bin: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a perl s
bin: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a perl script.
Sponsored by: Netflix
show more ...
|
Revision tags: release/14.0.0, release/13.2.0 |
|
#
a675eaec |
| 01-Jan-2023 |
Piotr Pawel Stefaniak <pstef@FreeBSD.org> |
sh: implement PS1 \D to print current time
\D{format} yields the result of calling strftime(3) with the provided format and the current time.
When PS4 can use this, it will enable us to easily gene
sh: implement PS1 \D to print current time
\D{format} yields the result of calling strftime(3) with the provided format and the current time.
When PS4 can use this, it will enable us to easily generate timestamps when tracing script execution.
Differential Revision: https://reviews.freebsd.org/D35840
show more ...
|
#
b2c76c41 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line nroff pattern
Remove /^\.\\"\s*\$FreeBSD\$$\n/
|
#
3cf65f8a |
| 08-Dec-2022 |
Juraj Lutter <otis@FreeBSD.org> |
sh(1): Allow non-printing characters in prompt strings
Introduce new prompt format characters:
- '\[' starts the sequence of non-printing chatacters - '\]' ends the sequence of non-printing charact
sh(1): Allow non-printing characters in prompt strings
Introduce new prompt format characters:
- '\[' starts the sequence of non-printing chatacters - '\]' ends the sequence of non-printing characters
Within these sequences, the following characters are now supported:
- '\a' emits ASCII BEL (0x07, 007) character - '\e' emits ASCII ESC (0x1b, 033) character - '\r' emits ASCII CR (0x0d, 015) character - '\n' emits ASCII CRLF sequence
These can be used to embed ANSI sequences into prompt strings.
Example in .shrc:
PS1="\[\e[7m\]\u@\h\[\e[0m\]:\w \\$ "
This tries to maintain some degree of compatibility with GNU bash, that uses GNU readline library (which behaves slightly different from BSD editline): It has two "non-printing boundary" characters:
- RL_PROMPT_START_IGNORE (\001) - RL_PROMPT_END_IGNORE (\002)
while BSD editline only has one (when using EL_PROMPT_ESC setting), so for this purpose, ASCII \001 was chosen and both \[ and \] emits this character.
And while here, enlarge PROMPTLEN from 128 to 192 characters.
Reviewed by: jilles Approved by: jilles Differential Revision: https://reviews.freebsd.org/D37701
show more ...
|
Revision tags: release/12.4.0 |
|
#
825225e5 |
| 14-Aug-2022 |
Jens Schweikhardt <schweikh@FreeBSD.org> |
For man page references found in ports, indicate the respective port.
|
#
b131efe3 |
| 31-Jul-2022 |
Gordon Bergling <gbe@FreeBSD.org> |
sh.1: Fix a mandoc warning
- new sentence, new line
MFC after: 3 days
|
Revision tags: release/13.1.0, release/12.3.0 |
|
#
d2c23317 |
| 23-Sep-2021 |
Stephane Rochoy <stephane.rochoy@stormshield.eu> |
sh: Add -o verify to use O_VERIFY when sourcing scripts
Add -o verify to sh to make it use O_VERIFY when sourcing scripts and reading profiles.
Useful in conjunction with mac_veriexec to help prote
sh: Add -o verify to use O_VERIFY when sourcing scripts
Add -o verify to sh to make it use O_VERIFY when sourcing scripts and reading profiles.
Useful in conjunction with mac_veriexec to help protect at least some parts of the boot sequence, e.g., /etc/rc*.
Differential revision: https://reviews.freebsd.org/D30464 Reviewed by: jilles, sjg Obtained from: Stormshield
show more ...
|
Revision tags: release/13.0.0 |
|
#
988b1bb0 |
| 30-Mar-2021 |
Baptiste Daroussin <bapt@FreeBSD.org> |
sh: implement persistent history storage
Implement persistent history storage: the strategy is simple at start: loads the existing .sh_history file at exit dump it.
The implementation respects the
sh: implement persistent history storage
Implement persistent history storage: the strategy is simple at start: loads the existing .sh_history file at exit dump it.
The implementation respects the HISTFILE variable and its POSIX definition: ~/.sh_history is used if HISTFILE is not set.
to avoid sh to create the history file, set HISTSIZE to 0 or HISTFILE to en empty value
Co-authored-by: pstef Reviewed by: jilles Differential Revision: https://reviews.freebsd.org/D29493
show more ...
|
Revision tags: release/12.2.0 |
|
#
2c566d31 |
| 06-Jul-2020 |
Mateusz Piotrowski <0mp@FreeBSD.org> |
Fix description of the "\$" sequence for PS1
The manual page documents "\$" to expand to either "$" or "#" followed by a single space. In reality, the single space character is not appended.
PR: 2
Fix description of the "\$" sequence for PS1
The manual page documents "\$" to expand to either "$" or "#" followed by a single space. In reality, the single space character is not appended.
PR: 247791 Submitted by: kd-dev@pm.me MFC after: 7 days
show more ...
|
Revision tags: release/11.4.0, release/12.1.0, release/11.3.0 |
|
#
18b18078 |
| 25-Feb-2019 |
Enji Cooper <ngie@FreeBSD.org> |
MFhead@r344527
|
#
a8fe8db4 |
| 25-Feb-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r344178 through r344512.
|
#
484160a9 |
| 24-Feb-2019 |
Jilles Tjoelker <jilles@FreeBSD.org> |
sh: Add set -o pipefail
The pipefail option allows checking the exit status of all commands in a pipeline more easily, at a limited cost of complexity in sh itself. It works similarly to the option
sh: Add set -o pipefail
The pipefail option allows checking the exit status of all commands in a pipeline more easily, at a limited cost of complexity in sh itself. It works similarly to the option in bash, ksh93 and mksh.
Like ksh93 and unlike bash and mksh, the state of the option is saved when a pipeline is started. Therefore, even in the case of commands like A | B & a later change of the option does not change the exit status, the same way (A | B) & works.
Since SIGPIPE is not handled specially, more work in the script is required for a proper exit status for pipelines containing commands such as head that may terminate successfully without reading all input. This can be something like
( cmd1 r=$? if [ "$r" -gt 128 ] && [ "$(kill -l "$r")" = PIPE ]; then exit 0 else exit "$r" fi ) | head
PR: 224270 Relnotes: yes
show more ...
|
#
7e565c55 |
| 30-Jan-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r343320 through r343570.
|
#
d81ca439 |
| 24-Jan-2019 |
Edward Tomasz Napierala <trasz@FreeBSD.org> |
Make sh(1) support \u in PS1. This removes one fork/exec on interactive shell startup.
Reviewed by: 0mp (man page), jilles MFC after: 2 weeks Sponsored by: DARPA, AFRL Differential Revision: https:
Make sh(1) support \u in PS1. This removes one fork/exec on interactive shell startup.
Reviewed by: 0mp (man page), jilles MFC after: 2 weeks Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D18790
show more ...
|
#
67350cb5 |
| 09-Dec-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r340918 through r341763.
|
#
1becbc64 |
| 08-Dec-2018 |
Jilles Tjoelker <jilles@FreeBSD.org> |
sh(1): Remove -c string from set builtin documentation
Altering the -c string at run time does not make sense and is not possible.
MFC after: 1 week
|
Revision tags: release/12.0.0 |
|
#
77da4a95 |
| 27-Nov-2018 |
Jilles Tjoelker <jilles@FreeBSD.org> |
sh: Use 126 and 127 exit status for failures opening a script
This affects scripts named on the command line, named with a '.' special builtin and found via the PATH %func autoloading mechanism.
PR
sh: Use 126 and 127 exit status for failures opening a script
This affects scripts named on the command line, named with a '.' special builtin and found via the PATH %func autoloading mechanism.
PR: 231986
show more ...
|
#
17e98da8 |
| 19-Jul-2018 |
Mateusz Piotrowski <0mp@FreeBSD.org> |
Describe how to prevent *.core files from being created using ulimit.
While here, pet mandoc.
Reviewed by: eadler (previous revision), jilles (previous revision), mat (mentor) Approved by: manpages
Describe how to prevent *.core files from being created using ulimit.
While here, pet mandoc.
Reviewed by: eadler (previous revision), jilles (previous revision), mat (mentor) Approved by: manpages (jilles), mat (mentor) Differential Revision: https://reviews.freebsd.org/D15609
show more ...
|
Revision tags: release/11.2.0 |
|
#
54b4b13c |
| 24-Dec-2017 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r326936 through r327149.
|