| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
| |
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)
|
| |
|
| |
|
|
|
|
|
| |
clrd(1) is POSIX sh, but clwr(1) ideally needs Readline, so I've left it
as #!/bin/bash for now.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Add comments, add short-circuit to vared() completion
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Not really justified
|
|
|
|
| |
OpenBSD doesn't have -n
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
<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
|
|
|
|
|
|
| |
I made the incorrect assumption that it was safe not to do this;
expansions that include glob characters, for example, can cause
problems.
|
| |
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
| |
Works better than the well-intended while-read loop
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Handy command:
$ find bin sh bash -type f -exec grep \
-e '|| \\$' \
-e '&& \\$' \
-e '^\s*||' \
-e '^\s*&&' \
{} +
|
|
|
|
| |
Forgot to narrow completions down to ones that match the current word
|
|
|
|
| |
I have "todo", "comp", and "writ".
|
|
|
|
| |
More compatible, want to display this in Cgit as well
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
On my work machines, I'll make a file ~/.bashrc.d/prompt.bash which
includes a PROMPT_VCS=(git svn) line.
I don't really use Mercurial at all, now that the Vim sources have moved
to Git; certainly not enough to check for it on every prompt load ...
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|