aboutsummaryrefslogtreecommitdiff
path: root/bin
Commit message (Collapse)AuthorAgeFilesLines
* Change cf() from Bash func to shell scriptTom Ryder2016-07-301-0/+27
|
* Move sprunge() Bash function to spr(1)Tom Ryder2016-07-301-0/+4
|
* Change pa and paz bash funcs to sh scriptsTom Ryder2016-07-302-0/+8
|
* Change ca from Bash func to sh scriptTom Ryder2016-07-301-0/+3
|
* Change mkmv/mkcp from Bash funcs to sh scriptsTom Ryder2016-07-302-0/+12
|
* Quote heredoc string in edda(1)Tom Ryder2016-07-271-1/+1
|
* Rename vis(1) to eds(1)Tom Ryder2016-07-231-6/+6
| | | | vis(1) is in OpenBSD >=4.4 base
* Replace use of ${var:?} with explicit errorsTom Ryder2016-07-153-4/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <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
* Use - rather than /dev/stdinTom Ryder2016-07-151-1/+1
| | | | less(1) gets upset if it's not a regular file, because reasons.
* Remove -d option from edda(1) mktemp(1) callTom Ryder2016-07-151-1/+1
|
* Add ax(1)Tom Ryder2016-07-141-0/+43
|
* 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-133-0/+31
|
* Add pit(1)Tom Ryder2016-07-131-0/+17
|
* Make murl(1) into plain POSIX sh scriptTom Ryder2016-07-071-4/+1
|
* Improve explanatory note about locales in hurl(1)Tom Ryder2016-07-051-1/+2
|
* Downgrade hurl(1) to a simple /bin/sh scriptTom Ryder2016-07-051-4/+1
| | | | | Not worth the extra dependency just for slightly nicer command presence checking
* Pretend to be Mozilla in urlc(1)Tom Ryder2016-07-051-2/+2
| | | | | | Because Amazon tells me to go away when I use the default user agent. I don't really feel sorry for it, because it throws a misleading 503 error too.
* Use -p opt to pup in hurl(1) for entity decodingTom Ryder2016-07-041-1/+1
|
* Remove C.UTF-8 LANG setting for plmu(1)Tom Ryder2016-07-041-4/+0
| | | | I'm using this script on a machine that doesn't have a C.UTF-8 locale.
* Use terser arg noodling in tl(1)Tom Ryder2016-07-021-4/+2
|
* Inline two lines in jfcd(1)Tom Ryder2016-07-021-2/+1
|
* Exit from gscr(1) subshell, not continueTom Ryder2016-07-021-5/+5
|
* Make fgscr POSIX sh/find compliantTom Ryder2016-07-011-2/+2
|
* Only find .git *directories*Tom Ryder2016-07-011-1/+1
|
* Add dub(1)Tom Ryder2016-07-011-0/+6
|
* Run gscr(1) in subshellTom Ryder2016-07-011-2/+2
|
* Correct glob for finding reposTom Ryder2016-07-011-1/+1
|
* Make gscr(1) default to current dirTom Ryder2016-07-011-1/+1
|
* Add gscr(1), fgscr(1)Tom Ryder2016-07-012-0/+19
|
* Add jfcd(1)Tom Ryder2016-06-301-0/+27
|
* Extend jfc(1) to check for changes before commitTom Ryder2016-06-301-3/+20
|
* Add jfc(1)Tom Ryder2016-06-291-0/+7
|
* Separate games out into own directory/targetsTom Ryder2016-06-241-5/+0
|
* Remove my CPAN mirror from plmu scriptTom Ryder2016-06-241-1/+1
| | | | | | | Defined as an environment variable instead, per-host: $ declare -xp PERL_CPANM_OPT declare -x PERL_CPANM_OPT="--mirror http://cpan.inspire.net.nz/"
* Rename binscripts more terselyTom Ryder2016-06-228-25/+25
|
* Remove unneeded line-break backslashesTom Ryder2016-06-212-2/+2
|
* Fix spelling mistakeTom Ryder2016-06-211-1/+1
|
* Add options terminatorTom Ryder2016-06-211-1/+1
|
* Add commentsTom Ryder2016-06-211-0/+11
|
* Move locale export to top of scriptTom Ryder2016-06-211-4/+6
|
* Test for required programsTom Ryder2016-06-201-0/+2
|
* Move LANG setting to topTom Ryder2016-06-201-3/+6
|
* Add newlineTom Ryder2016-06-201-0/+1
|
* Add plenv-modules-updateTom Ryder2016-06-201-0/+17
|
* Add getmailsTom Ryder2016-06-191-0/+36
|
* Fix comment tooTom Ryder2016-06-181-1/+1
|
* Swap pandoc(1) for markdown(1)Tom Ryder2016-06-181-2/+2
| | | | | | | | | | | | | | > <REDACTED> OPTIONS Use "--" to end switch parsing. > <REDACTED> are you using the wrong markdown > <tejr> yeah checking versions > <REDACTED> 1.0.1 is the one I quoted > <tejr> ah > <tejr> it's documented, but does not work :^) > <tejr> $ pandoc -f markdown -t html -- /home/tom/.dotfiles/README.markdown > <tejr> based pandoc(1) > <REDACTED> hahaha > <REDACTED> welp > <tejr> welp indeed
* markdown(1) can't into option terminatorsTom Ryder2016-06-181-1/+1
|
* Nice comments for URLs scriptsTom Ryder2016-06-183-1/+42
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-23 19:52:58 +0000