summary refs log tree commit diff
path: root/bin/1sh (follow)
Commit message (Collapse)AuthorAge
* Replace __DECONST with regular castsJune McEnroe2020-06-08
| | | | sed -E 's/__DECONST[(]([^,]+), ([^)]+)[)]/(\1)(\2)/'
* Replace __printflike with __attribute__((format(printf, ...)))June McEnroe2020-06-08
| | | | sed -E 's/__printf0?like[(]([^,]+), ([^)]+)[)]/__attribute__((format(printf, \1, \2)))/'
* Replace __dead2 with __attribute__((noreturn))June McEnroe2020-06-08
| | | | sed 's/__dead2/__attribute__((noreturn))/'
* Replace __FBSDID macros with commentsJune McEnroe2020-06-08
| | | | sed -E 's|__FBSDID[(]"([^"]+)"[)];|/* \1 */|'
* Remove reference to FreeBSD-specific libedit hackJune McEnroe2020-06-08
| | | | | | | | Newer versions of libedit have sane tab-complete now without FreeBSD's hacks, and in fact the hack is gone in FreeBSD-CURRENT. I'm still a little confused why binding this weird function is necessary at all, but at least it exists everywhere, I guess.
* Remove mktemp options from mkbuiltins, mktokensJune McEnroe2020-06-07
| | | | Why even?
* Add HISTFILE history savingJune McEnroe2020-03-09
|
* Source .editrc before applying -v or -eJune McEnroe2020-03-09
| | | | | Otherwise a bind -v in .editrc will take precedence and overwrite the ^I binding for sh-complete.
* Add \? exit status prompt expansionJune McEnroe2020-03-09
|
* Shorten $HOME to ~ in prompt expansionJune McEnroe2020-03-09
|
* Add PS0 pre-prompt stringJune McEnroe2020-03-09
|
* Add RPS1 and RPS2 right promptsJune McEnroe2020-03-09
|
* Fix copyright and rcsidJune McEnroe2020-03-09
|
* Replace strchrnul with strchrJune McEnroe2020-03-09
|
* Replace eaccess with faccessatJune McEnroe2020-03-09
|
* Replace st_mtim with st_mtimespecJune McEnroe2020-03-09
|
* Replace sys_nsig with NSIGJune McEnroe2020-03-09
|
* Replace 1sh MakefileJune McEnroe2020-03-09
|
* Rename manual pages to 1shJune McEnroe2020-03-09
|
* Move bltin out of subdirectoryJune McEnroe2020-03-09
|
* Import /usr/src/usr.bin/printf from FreeBSD 12.1-RELEASEJune McEnroe2020-03-09
|
* Import /usr/src/bin/test from FreeBSD 12.1-RELEASEJune McEnroe2020-03-09
|
* Import /usr/src/bin/kill from FreeBSD 12.1-RELEASEJune McEnroe2020-03-09
|
* Remove extraneous files from sh sourcesJune McEnroe2020-03-09
|
* Import /usr/src/bin/sh from FreeBSD 12.1-RELEASEJune McEnroe2020-03-09
|
* Remove 1sh sourcesJune McEnroe2020-03-09
| | | | I'm going to recreate it from fresh sh sources for clean git history.
* Source .editrc before applying -v or -eJune McEnroe2019-12-20
| | | | | Otherwise a bind -v in .editrc will take precedence and overwrite the ^I binding for sh-complete.
* Fix \? prompt expansion for more than one digitJune McEnroe2019-12-02
|
* Document HISTFILEJune McEnroe2019-11-26
|
* Remove default ENV from manualJune McEnroe2019-11-21
|
* Do not apply expansion to HISTFILEJune McEnroe2019-11-21
|
* Revert "Set default ENV to ~/.config/cash/cashrc"June McEnroe2019-11-21
| | | | This reverts commit 2d722bdd93ba2ddd9d7e4394a845eeea9951ab5f.
* Remove HISTFILE default valueJune McEnroe2019-11-21
|
* Remove vendored libeditJune McEnroe2019-11-21
|
* Revert "Use local libedit"June McEnroe2019-11-21
| | | | This reverts commit a8cd87a52b91f41d3bec81b1a36fa224501f3af7.
* Just use H_LOAD and H_SAVEJune McEnroe2019-11-21
|
* Use braces in 1sh MakefileJune McEnroe2019-11-21
|
* Add \? exit status prompt expansionJune McEnroe2019-11-20
|
* Remove PSlitJune McEnroe2019-11-20
|
* Rename catsh to 1shJune McEnroe2019-06-28
Yes it's another rename because I felt like catsh was too long. 1sh is short and unique.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2026-08-09 01:56:07 +0000
by default. It appears to be working now, however, we have to change our code to detect the no-match case correctly. In particular, we need to test for GLOB_NOMAGIC | GLOB_NOCHECK instead of GLOB_MAGCHAR. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix buffer overflow in expandmetaHerbert Xu The native version of expandmeta allocates a buffer that may be overrun for two reasons. First of all the size is 1 byte too small but this is normally hidden because the minimum size is rounded up to 2048 bytes. Secondly, if the directory level is deep enough, any buffer can be overrun. This patch fixes both problems by calling realloc when necessary. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02builtin: Move echo space/nl handling into print_escape_strHerbert Xu Currently echocmd uses print_escape_str to do everything apart from printing the spaces/newlines separating its arguments. This patch moves the actual printing into print_escape_str as well using the format parameter. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02builtin: Fix echo performance regressionHerbert Xu The commit d6c0e1e2ffbf7913ab69d51cc794d48d41c8fcb1 ("[BUILTIN] Handle embedded NULs correctly in printf") caused a performance regression in the echo built-in because every echo call now goes through the printf %b slow path where the string is always printed twice to ensure the space padding is correct in the presence of NUL characters. In fact this regression applies to printf %b as well. This is easily fixed by making printf %b take the fast path when no precision/field width modifiers are present. This patch also changes the second strchurnul call to strspn which generates slightly better code. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix ghost fields with unquoted $@/$*Herbert Xu Harald van Dijk <harald@gigawatt.nl> wrote: > On 22/03/2018 22:38, Martijn Dekker wrote: >> Op 22-03-18 om 20:28 schreef Harald van Dijk: >>> On 22/03/2018 03:40, Martijn Dekker wrote: >>>> This patch fixes the bug that, given no positional parameters, unquoted >>>> $@ and $* incorrectly generate one empty field (they should generate no >>>> fields). Apparently that was a side effect of the above. >>> >>> This seems weird though. If you want to remove the recording of empty >>> regions because they are pointless, then how does removing them fix a >>> bug? Doesn't this show that empty regions do have an effect? Perhaps >>> they're not supposed to have any effect, perhaps it's a specific >>> combination of empty regions and something else that triggers some bug, >>> and perhaps that combination can no longer occur with your patch. >> >> The latter is my guess, but I haven't had time to investigate it. > > Looking into it again: > > When IFS is set to an empty string, sepc is set to '\0' in varvalue(). > This then causes *quotedp to be set to true, meaning evalvar()'s quoted > variable is turned on. quoted is then passed to recordregion() as the > nulonly parameter. > > ifsp->nulonly has a bigger effect than merely selecting whether to use > $IFS or whether to only split on null bytes: in ifsbreakup(), nulonly > also causes string termination to be suppressed. That's correct: that > special treatment is required to preserve empty fields in "$@" > expansion. But it should *only* be used when $@ is quoted: ifsbreakup() > takes nulonly from the last IFS region, even if it's empty, so having an > additional zero-length region with nulonly enabled causes confusion. > > Passing quoted by value to varvalue() and not attempting to modify it > should therefore, and in my quick testing does, also work to fix the > original $@ bug. You're right. The proper fix to this is to ensure that nulonly is not set in varvalue for $*. It should only be set for $@ when it's inside double quotes. In fact there is another bug while we're playing with $@/$*. When IFS is set to a non-whitespace character such as :, $* outside quotes won't remove empty fields as it should. This patch fixes both problems. Reported-by: Martijn Dekker <martijn@inlv.org> Suggested-by: Harald van Dijk <harald@gigawatt.nl> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02parser: Allow newlines within parameter substitutionHerbert Xu On Fri, Mar 16, 2018 at 11:27:22AM +0800, Herbert Xu wrote: > On Thu, Mar 15, 2018 at 10:49:15PM +0100, Harald van Dijk wrote: > > > > Okay, it can be trivially modified to something that does work in other > > shells (even if it were actually executed), but gets rejected at parse time > > by dash: > > > > if false; then > > : ${$+ > > } > > fi > > That's just a bug in dash's parser with ${} in general, because > it bombs out without the if clause too: > > : ${$+ > } This patch fixes the parsing of newlines with parameter substitution. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix bugs with words connected to the right of $@Herbert Xu On Sun, Mar 04, 2018 at 12:44:59PM +0100, Harald van Dijk wrote: > > command: set -- a ""; space=" "; printf "<%s>" "$@"$space > bash: <a><> > dash 0.5.8: <a>< > > dash 0.5.9.1: <a>< > > dash patched: <a><> This is actually composed of two bugs. First of all our tracking of quotemark is wrong so anything after "$@" becomes quoted. Once we fix that then the problem is that the first space character after "$@" is not recognised as an IFS. This patch fixes both. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-03-25Revert "[BUILTIN] Remove unnecessary restoration of format string in printf"Herbert Xu This reverts commit 7bb413255368e94395237d789f522891093c5774. The commit breaks printf with more than argument. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-03-22parser: Fix backquote support in here-document EOF markHerbert Xu