Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Move issues into their own file. | Tom Ryder | 2016-07-30 | 2 | -4/+8 |
| | |||||
* | Tidy completion files | Tom Ryder | 2016-07-30 | 10 | -7/+10 |
| | | | | Add comments, add short-circuit to vared() completion | ||||
* | Change cf() from Bash func to shell script | Tom Ryder | 2016-07-30 | 4 | -30/+42 |
| | |||||
* | Add install-bin to default install target | Tom Ryder | 2016-07-30 | 2 | -4/+5 |
| | |||||
* | Move sprunge() Bash function to spr(1) | Tom Ryder | 2016-07-30 | 4 | -6/+28 |
| | |||||
* | Add two missing periods | Tom Ryder | 2016-07-30 | 1 | -2/+2 |
| | |||||
* | Change pa and paz bash funcs to sh scripts | Tom Ryder | 2016-07-30 | 7 | -13/+40 |
| | |||||
* | Use terser syntax for .d loop sources | Tom Ryder | 2016-07-30 | 2 | -24/+15 |
| | |||||
* | Create separate install-bash-completion target | Tom Ryder | 2016-07-30 | 1 | -2/+6 |
| | |||||
* | Rename vis completion to eds | Tom Ryder | 2016-07-30 | 1 | -7/+7 |
| | |||||
* | Move bash completion setup into separate dir | Tom Ryder | 2016-07-30 | 34 | -218/+221 |
| | |||||
* | Change ca from Bash func to sh script | Tom Ryder | 2016-07-30 | 5 | -24/+17 |
| | |||||
* | Change mkmv/mkcp from Bash funcs to sh scripts | Tom Ryder | 2016-07-30 | 7 | -10/+52 |
| | |||||
* | Add rule for kvlt(6) to change numbers to 666 | Tom Ryder | 2016-07-28 | 1 | -0/+3 |
| | |||||
* | Quote heredoc string in edda(1) | Tom Ryder | 2016-07-27 | 1 | -1/+1 |
| | |||||
* | Remove md.bash | Tom Ryder | 2016-07-24 | 1 | -4/+0 |
| | | | | Not really justified | ||||
* | Rename vis(1) to eds(1) | Tom Ryder | 2016-07-23 | 4 | -23/+23 |
| | | | | vis(1) is in OpenBSD >=4.4 base | ||||
* | Remove custom length limit on login fortunes | Tom Ryder | 2016-07-23 | 1 | -1/+1 |
| | | | | OpenBSD doesn't have -n | ||||
* | Increase context for syntax highlighting | Tom Ryder | 2016-07-19 | 1 | -1/+2 |
| | |||||
* | Specify encoding of .vimrc | Tom Ryder | 2016-07-19 | 1 | -0/+3 |
| | |||||
* | Switch back to Pale Moon | Tom Ryder | 2016-07-18 | 1 | -2/+2 |
| | | | | Trying again | ||||
* | Replace use of ${var:?} with explicit errors | Tom Ryder | 2016-07-15 | 4 | -5/+27 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <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 | ||||
* | Clean up and document syl(6) | Tom Ryder | 2016-07-15 | 2 | -14/+85 |
| | |||||
* | Use less(1) as PAGER if available | Tom Ryder | 2016-07-15 | 1 | -0/+7 |
| | |||||
* | Use - rather than /dev/stdin | Tom Ryder | 2016-07-15 | 1 | -1/+1 |
| | | | | less(1) gets upset if it's not a regular file, because reasons. | ||||
* | Quote expansions within parameter expansions | Tom Ryder | 2016-07-15 | 13 | -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 ''` idiom | Tom Ryder | 2016-07-15 | 11 | -12/+12 |
| | |||||
* | Remove -d option from edda(1) mktemp(1) call | Tom Ryder | 2016-07-15 | 1 | -1/+1 |
| | |||||
* | Add ax(1) | Tom Ryder | 2016-07-14 | 3 | -0/+60 |
| | |||||
* | Use escape for pagebreak char in rfct(1) | Tom Ryder | 2016-07-13 | 1 | -1/+1 |
| | |||||
* | Add rfcf(1), rfcr(1), and rfct(1) | Tom Ryder | 2016-07-13 | 7 | -0/+86 |
| | |||||
* | Add pit(1) | Tom Ryder | 2016-07-13 | 3 | -0/+41 |
| | |||||
* | Add wrdl to games | Tom Ryder | 2016-07-08 | 1 | -0/+10 |
| | | | | No manual page yet | ||||
* | Incremental improvement to syl heuristic | Tom Ryder | 2016-07-08 | 1 | -1/+1 |
| | |||||
* | Allow providing wordlist to hku | Tom Ryder | 2016-07-08 | 1 | -2/+3 |
| | |||||
* | Add wrds to games | Tom Ryder | 2016-07-08 | 1 | -0/+3 |
| | | | | No manual page yet | ||||
* | Add hku and syl to games | Tom Ryder | 2016-07-08 | 2 | -0/+34 |
| | | | | Very ugly, and no manual pages yet. | ||||
* | Make murl(1) into plain POSIX sh script | Tom Ryder | 2016-07-07 | 1 | -4/+1 |
| | |||||
* | WAR->KRIEG in kvlt(6) | Tom Ryder | 2016-07-06 | 1 | -0/+3 |
| | |||||
* | Remove substitution from kvlt(6) | Tom Ryder | 2016-07-06 | 1 | -3/+0 |
| | |||||
* | Correct a word subtitution in kvlt(6) | Tom Ryder | 2016-07-06 | 1 | -1/+1 |
| | |||||
* | New word for kvlt(6) | Tom Ryder | 2016-07-06 | 1 | -0/+1 |
| | |||||
* | Truncate very long seeds | Tom Ryder | 2016-07-06 | 1 | -0/+3 |
| | |||||
* | Another world for kvlt(6) | Tom Ryder | 2016-07-06 | 1 | -0/+1 |
| | |||||
* | Another word for kvlt(6) | Tom Ryder | 2016-07-06 | 1 | -0/+1 |
| | |||||
* | Add a few more words to kvlt(6) | Tom Ryder | 2016-07-06 | 1 | -0/+6 |
| | |||||
* | Run another kvlt(6) revamp | Tom Ryder | 2016-07-06 | 1 | -8/+36 |
| | | | | I'm having a lot of fun with this. | ||||
* | Don't change ch- to kh- | Tom Ryder | 2016-07-06 | 1 | -2/+2 |
| | |||||
* | Move translations to end | Tom Ryder | 2016-07-06 | 1 | -3/+3 |
| | |||||
* | Rewrite of kvlt(6) | Tom Ryder | 2016-07-06 | 1 | -12/+33 |
| | | | | | | | | | | | | | | It turns out GNU sed doesn't support POSIX word boundaries [[:<:]],[[:>:]]. This leaves me with no compatible way to denote a word boundary. I shouldn't really be surprised. I've worked around this by padding the start and end of each line with a tilde, and then removing it again at the end of the script, which is not great but will have to do. It's preferable to having two-three versions of each of the word-boundary rules to support ^ and $ anchoring. This is probably the weirdest way anyone has ever learned sed. |