aboutsummaryrefslogtreecommitdiff
path: root/bash
Commit message (Collapse)AuthorAgeFilesLines
* Move OLDPWD setting to POSIX sh dirTom Ryder2016-08-201-3/+0
| | | | With an attempt at correct trapping; may still require tweaking
* Change cd() into POSIX shell scriptTom Ryder2016-08-191-32/+0
|
* Add lhn()Tom Ryder2016-08-181-0/+7
|
* Drastically limit amount of history keptTom Ryder2016-08-181-4/+4
| | | | | | Reading really large files seems to be slow in Bash in general, but it's particularly bad in 4.4rc1. I keep encrypted snapshots of my HISTFILE on my home machine, so it's just a little extra step to search them.
* Don't do Git prompt work if not in working treeTom Ryder2016-08-181-0/+7
|
* Use explicit -n test within [[ ]]Tom Ryder2016-08-182-3/+3
| | | | | Bash doesn't require it, but there's no real advantage to it and it's a better habit for complying with e.g. pdksh, which does
* Use consistent syntax for sh source loopsTom Ryder2016-08-182-9/+5
|
* Port grep() and ls() to POSIX shTom Ryder2016-08-182-55/+0
| | | | | | Check capabilities of wrapped programs at runtime, not declaration time. Also do away with the silly GREP_COLORS and GREP_OPTS variables. Considering doing the same with LS_COLORS.
* Update bashrc/zshrc with POSIX funcs sourceTom Ryder2016-08-171-1/+1
|
* Simplify end-of-file loop in bashrcTom Ryder2016-08-171-24/+8
|
* Use terser loop syntax in ~/.bash_profileTom Ryder2016-08-171-3/+2
|
* Source ~/.shrc.d in Bash if not login shellTom Ryder2016-08-171-0/+12
|
* Move interactive tests back into *rc filesTom Ryder2016-08-172-4/+10
| | | | | | I don't fully understand why I have to do it this way yet, but if I don't, calling SSH with a command raises "stdin: not a terminal" because ~/.bashrc was called.
* Move -i test in Bash to end of ~/.bash_profileTom Ryder2016-08-172-9/+4
|
* Move simple Bash/pdksh functions into POSIX shTom Ryder2016-08-1716-171/+0
| | | | | | | Have only translated the scripts that translate readily into POSIX sh for now. More complex stuff like that bd/pd/sd/ud navigation for Bash doesn't port as easily, mostly because there isn't an analogue for the "local" keyword in POSIX.
* Keep grep(1) option metadata in cacheTom Ryder2016-08-151-9/+11
| | | | | | | | | It's stupid to run `grep --help` once per shell (twice for login shells!) when it's so unlikely to change, and way faster to check for the presence or absence of hint files rather than pattern-match the output with the shell. ls(1) will get the same treatment in a minute.
* Don't use git: prompt prefix if PROMPT_VCS unsetTom Ryder2016-08-151-2/+3
| | | | | All of my personal stuff is in Git, so this is only really applicable at work
* Remove square brackets around promptTom Ryder2016-08-151-1/+1
| | | | Just noise
* Quote a PS1 character to appease shellcheckTom Ryder2016-08-141-1/+1
|
* Two extra commentsTom Ryder2016-08-141-0/+2
|
* Rearrange prompt variable assignments a bitTom Ryder2016-08-141-10/+12
|
* Use --quiet flag for prompt git-rev-parse(1) callTom Ryder2016-08-141-1/+1
|
* Use porcelain commands for Git promptTom Ryder2016-08-131-27/+9
| | | | | | | | | | | | Checking the output of `git status -z` works, but to be correctly handled requires using a null delimiter for read. Because I want to port this to OpenBSD pdksh (which doesn't have the -d option for read), this seems to be a workable alternative. It also enables me to remove the process substitution (another thing pdksh doesn't support), and the array of flags. I haven't yet tested this for speed.
* Fix comment typoTom Ryder2016-08-111-1/+1
|
* Test bc(1) for non-POSIX -qTom Ryder2016-08-111-0/+3
|
* Add explicit -n to hgrep() $HISTFILE checkTom Ryder2016-08-101-1/+1
|
* Remove "hg" from possible completions for prompt()Tom Ryder2016-08-101-1/+1
|
* Remove Mercurial support from Bash promptTom Ryder2016-08-101-37/+0
| | | | | | Since Vim and Fanboy's list both moved to Git, I have no reason to use it anymore. Also added a note explaining why I've left the SVN stuff in there (I don't like SVN, but I do need to use it for work)
* Switch fnl()/scr() to use mktd(1)Tom Ryder2016-08-042-6/+3
|
* Remove error in expansion quotingTom Ryder2016-08-031-1/+1
|
* Move clrd()/clwr() to scriptsTom Ryder2016-08-022-13/+0
| | | | | clrd(1) is POSIX sh, but clwr(1) ideally needs Readline, so I've left it as #!/bin/bash for now.
* Strip trailing newline from clrd()Tom Ryder2016-08-021-1/+0
|
* Add clrd()Tom Ryder2016-08-021-0/+6
|
* Change apf() to a shell scriptTom Ryder2016-08-021-99/+0
|
* Change bell() to a POSIX sh scriptTom Ryder2016-08-011-4/+0
|
* Tidy completion filesTom Ryder2016-07-3010-7/+10
| | | | Add comments, add short-circuit to vared() completion
* Change cf() from Bash func to shell scriptTom Ryder2016-07-301-29/+0
|
* Move sprunge() Bash function to spr(1)Tom Ryder2016-07-301-5/+0
|
* Change pa and paz bash funcs to sh scriptsTom Ryder2016-07-302-11/+0
|
* Use terser syntax for .d loop sourcesTom Ryder2016-07-301-16/+10
|
* Rename vis completion to edsTom Ryder2016-07-301-7/+7
|
* Move bash completion setup into separate dirTom Ryder2016-07-3033-217/+218
|
* Change ca from Bash func to sh scriptTom Ryder2016-07-301-4/+0
|
* Change mkmv/mkcp from Bash funcs to sh scriptsTom Ryder2016-07-302-8/+0
|
* Remove md.bashTom Ryder2016-07-241-4/+0
| | | | Not really justified
* Remove custom length limit on login fortunesTom Ryder2016-07-231-1/+1
| | | | OpenBSD doesn't have -n
* Replace use of ${var:?} with explicit errorsTom Ryder2016-07-151-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <http://mywiki.wooledge.org/BashFAQ/100#Default_or_alternate_values> >Nobody ever uses ${var?word} or ${var:?word}. Please pretend they don't >exist, just like you pretend set -e and set -u don't exist. ><tejr> from FAQ 100: >Nobody ever uses ${var?word} or ${var:?word}. ><tejr> why is that? just because it's unwieldy, or are there other >technical reasons? ><ormaaj> tejr: Putting random fatal unhandlable errors into a script is >generally useless. ><tejr> ormaaj: is it less handleable than a more explicit check, like >`[[ $var ]] || exit 1` ? ><ormaaj> yes ><ormaaj> # : ; ${_[RANDOM%2]?:you win} ><shbot> ormaaj: no output ><ormaaj> didn't win ><tejr> i was thinking more as a terse means of perhaps asserting a >variable had a value, like a positional parameter; are you saying if >you really did just want to write to stderr and exit with failure, it's >still inappropriate? ><ormaaj> depends on the complexity I suppose but I'd not consider that >unless it's the global scope in a file you know isn't going to be >sourced and has no other explicit error handling. Even then it's ugly >because it bails out in the middle of evaluating parameters that >technically could have side-effects and such. ><tejr> ahh yes, kinda a separation of concerns ><tejr> that makes more sense now! thank you > * tejr combs his scripts to see if he's used it anywhere ><ormaaj> tejr: another reason is the type of error is a bash error >which usually indicates a problem with the script where bash itself >can't continue. An unset var isn't a " bash error", You can even make >it print counterintuitive error messages that look like bash internal >errors. ><tejr> ormaaj: also compelling ><tejr> i've found a few "{@:?}"s in here so i'm fixing them up now ><tejr> thanks for the analysis
* Quote expansions within parameter expansionsTom Ryder2016-07-1513-22/+21
| | | | | | I made the incorrect assumption that it was safe not to do this; expansions that include glob characters, for example, can cause problems.
* Terser `read -rd ''` idiomTom Ryder2016-07-1511-12/+12
|
* Use set rather than building arg arraysTom Ryder2016-07-025-32/+27
| | | | | | Allows for terser functions and avoids error-prone local variables; also nicer to have a single `command` call at the end of the function (although there are still two at the end of the ed(1) wrapper)
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-11 15:34:11 +0000