aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Move issues into their own file.Tom Ryder2016-07-302-4/+8
|
* 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-304-30/+42
|
* Add install-bin to default install targetTom Ryder2016-07-302-4/+5
|
* Move sprunge() Bash function to spr(1)Tom Ryder2016-07-304-6/+28
|
* Add two missing periodsTom Ryder2016-07-301-2/+2
|
* Change pa and paz bash funcs to sh scriptsTom Ryder2016-07-307-13/+40
|
* Use terser syntax for .d loop sourcesTom Ryder2016-07-302-24/+15
|
* Create separate install-bash-completion targetTom Ryder2016-07-301-2/+6
|
* Rename vis completion to edsTom Ryder2016-07-301-7/+7
|
* Move bash completion setup into separate dirTom Ryder2016-07-3034-218/+221
|
* Change ca from Bash func to sh scriptTom Ryder2016-07-305-24/+17
|
* Change mkmv/mkcp from Bash funcs to sh scriptsTom Ryder2016-07-307-10/+52
|
* Add rule for kvlt(6) to change numbers to 666Tom Ryder2016-07-281-0/+3
|
* Quote heredoc string in edda(1)Tom Ryder2016-07-271-1/+1
|
* Remove md.bashTom Ryder2016-07-241-4/+0
| | | | Not really justified
* Rename vis(1) to eds(1)Tom Ryder2016-07-234-23/+23
| | | | vis(1) is in OpenBSD >=4.4 base
* Remove custom length limit on login fortunesTom Ryder2016-07-231-1/+1
| | | | OpenBSD doesn't have -n
* Increase context for syntax highlightingTom Ryder2016-07-191-1/+2
|
* Specify encoding of .vimrcTom Ryder2016-07-191-0/+3
|
* Switch back to Pale MoonTom Ryder2016-07-181-2/+2
| | | | Trying again
* Replace use of ${var:?} with explicit errorsTom Ryder2016-07-154-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 Ryder2016-07-152-14/+85
|
* Use less(1) as PAGER if availableTom Ryder2016-07-151-0/+7
|
* Use - rather than /dev/stdinTom Ryder2016-07-151-1/+1
| | | | less(1) gets upset if it's not a regular file, because reasons.
* 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
|
* Remove -d option from edda(1) mktemp(1) callTom Ryder2016-07-151-1/+1
|
* Add ax(1)Tom Ryder2016-07-143-0/+60
|
* Use escape for pagebreak char in rfct(1)Tom Ryder2016-07-131-1/+1
|
* Add rfcf(1), rfcr(1), and rfct(1)Tom Ryder2016-07-137-0/+86
|
* Add pit(1)Tom Ryder2016-07-133-0/+41
|
* Add wrdl to gamesTom Ryder2016-07-081-0/+10
| | | | No manual page yet
* Incremental improvement to syl heuristicTom Ryder2016-07-081-1/+1
|
* Allow providing wordlist to hkuTom Ryder2016-07-081-2/+3
|
* Add wrds to gamesTom Ryder2016-07-081-0/+3
| | | | No manual page yet
* Add hku and syl to gamesTom Ryder2016-07-082-0/+34
| | | | Very ugly, and no manual pages yet.
* Make murl(1) into plain POSIX sh scriptTom Ryder2016-07-071-4/+1
|
* WAR->KRIEG in kvlt(6)Tom Ryder2016-07-061-0/+3
|
* Remove substitution from kvlt(6)Tom Ryder2016-07-061-3/+0
|
* Correct a word subtitution in kvlt(6)Tom Ryder2016-07-061-1/+1
|
* New word for kvlt(6)Tom Ryder2016-07-061-0/+1
|
* Truncate very long seedsTom Ryder2016-07-061-0/+3
|
* Another world for kvlt(6)Tom Ryder2016-07-061-0/+1
|
* Another word for kvlt(6)Tom Ryder2016-07-061-0/+1
|
* Add a few more words to kvlt(6)Tom Ryder2016-07-061-0/+6
|
* Run another kvlt(6) revampTom Ryder2016-07-061-8/+36
| | | | I'm having a lot of fun with this.
* Don't change ch- to kh-Tom Ryder2016-07-061-2/+2
|
* Move translations to endTom Ryder2016-07-061-3/+3
|
* Rewrite of kvlt(6)Tom Ryder2016-07-061-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.