summary refs log tree commit diff
path: root/home (follow)
Commit message (Collapse)AuthorAge
* Add .editrc to set vi bindingsJune McEnroe2019-12-15
|
* Set ssh port for git.causal.agencyJune McEnroe2019-12-15
|
* Allow cd-ing into a fileJune McEnroe2019-12-05
|
* Only add existing directories to PATHJune McEnroe2019-11-29
|
* Clear PATH before populating it againJune McEnroe2019-11-27
| | | | Oops, this got lost.
* Add bman alias for FreeBSD man pagesJune McEnroe2019-11-22
|
* Remove Linux aliases from .shrcJune McEnroe2019-11-22
| | | | Let's be honest this is unlikely to ever run on Linux...
* Remove 1sh env.shJune McEnroe2019-11-21
|
* Use .profile, .shrc, .historyJune McEnroe2019-11-21
|
* Add \? to promptJune McEnroe2019-11-20
|
* Remove color from 1sh promptsJune McEnroe2019-11-20
| | | | | The weird PSlit behaviour just causes more weirdness than it's worth. The color I was using was barely different anyway.
* Add GPL header templateJune McEnroe2019-11-06
|
* Use initial in git authorJune McEnroe2019-11-01
|
* Mark ' for \aJune McEnroe2019-10-28
|
* Set the write variable for nvim man modeJune McEnroe2019-10-14
| | | | Embarrassing...
* Update neovim 0.4.2June McEnroe2019-10-02
| | | | | Finally a release with my man mode fix... Meanwhile neovim itself has probably gotten worse.
* Remove host thursdayJune McEnroe2019-08-27
| | | | RIP.
* Clean up home filesJune McEnroe2019-07-27
|
* Fix shell script style in ~/.local/binJune McEnroe2019-07-27
|
* Add wiki scriptJune McEnroe2019-07-24
|
* Use env.sh as 1sh todo listJune McEnroe2019-07-01
|
* Clean up 1sh prompt settingJune McEnroe2019-06-29
|
* 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.
* Set HISTSIZE in catshJune McEnroe2019-06-28
|
* Set LESS=FRXJune McEnroe2019-06-19
| | | | | | This is how git invokes less by default. I think I want this everywhere. This allows color, exits if the input fits on one screen, and doesn't clear the screen.
* Alias date=ddateJune McEnroe2019-06-16
| | | | Will I regret this?
* Clean up catsh configJune McEnroe2019-04-18
|
* Rename cash config to catshJune McEnroe2019-04-18
|
* Color python imports as StatementJune McEnroe2019-04-15
|
* Move /opt/pkg after /usr in PATHJune McEnroe2019-02-20
| | | | | Installing mandoc from pkgsrc also installs a man executable which is horribly broken. Keep using the system man.
* Set man_hard_wrap in nvimJune McEnroe2019-02-20
| | | | | Vendoring man.vim until <https://github.com/neovim/neovim/pull/9633> is merged and appears in a release.
* Color format specifiers light cyan in vimJune McEnroe2019-02-15
|
* Add nmap gpJune McEnroe2019-02-15
|
* Unify *up scripts into one up.shJune McEnroe2019-02-12
|
* Use italic for underline in nvim man modeJune McEnroe2019-02-10
| | | | | This doesn't yet work in Terminal.app: <https://github.com/neovim/neovim/issues/9598>.
* Set git commit.verboseJune McEnroe2019-02-10
|
* Add hupJune McEnroe2019-02-09
|
* Don't open folds when using {}June McEnroe2019-02-08
|
* Import autoload/man.vim from 71bb4fdJune McEnroe2019-02-07
| | | | | | | | This is the version of man.vim prior to <https://github.com/neovim/neovim/pull/9023>. I opened an issue for the degraded experience <https://github.com/neovim/neovim/issues/9583>.
* Set nvim Directory back to blueJune McEnroe2019-02-01
| | | | | nvim is going bad I tell ya. Man mode seems broken in the new version too.
* Add def scriptJune McEnroe2019-02-01
|
* Add back tux to ssh configJune McEnroe2019-01-26
|
* Set nvim UI colors back to the 8-color paletteJune McEnroe2019-01-25
| | | | | Neovim seems intent on replacing all the default colors with ghastly choices from the 256-color palette.
* Add !! alias in cashJune McEnroe2019-01-15
|
* Use \$ in cash PS1 and add # to RPS1June McEnroe2019-01-15
|
* Show full path in RPS1June McEnroe2019-01-13
|
* Set PS0 in cashJune McEnroe2019-01-13
|
* Change default ENV from cashrc to env.shJune McEnroe2019-01-13
|
* Use colours in cash promptsJune McEnroe2019-01-13
|
* Add cashrcJune McEnroe2019-01-11
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2026-06-01 01:38:10 +0000
018-04-19 18:19:29 +0800'>2018-04-19eval: Restore input files in evalcommandHerbert Xu When evalcommand invokes a command that modifies parsefile and then bails out without popping the file, we need to ensure the input file is restored so that the shell can continue to execute. Reported-by: Martijn Dekker <martijn@inlv.org> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-19eval: Reap zombies after built-in commands and functionsHerbert Xu Currently dash does not reap dead children after built-in commands or functions. This means that if you construct a loop consisting of solely built-in commands and functions, then zombies can hang around indefinitely. This patch fixes this by reaping when necessary after each built-in command and function. Reported-by: Denys Vlasenko <vda.linux@googlemail.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-19redir: Fix typo in noclobber codeHerbert Xu The noclobber code has a typo in it that causes it to fail. This patch fixes it. Reported-by: Denys Vlasenko <vda.linux@googlemail.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-19expand: Fix glibc glob(3) supportHerbert Xu It's been a while since we disabled glob(3) support 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