| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
Like in 3828a1f, this variable actually does get set before use, but not
in a place ShellCheck could be reasonably expected to find
|
| |
|
|
|
|
| |
End the prompt subshell with a : to reset $?
|
| |
|
|
|
|
|
| |
ret actually is assigned, just not in any place ShellCheck could
reasonably be expected to find
|
|
|
|
| |
And also the PROMPT_RETURN fudge in Bash/Zsh
|
|
|
|
| |
Found a way to do this that seems to work in all the KSHes I've tried
|
| |
|
|
|
|
|
| |
FreeBSD pdksh doesn't even have complete typeset -p output, nor printf
%q, which I think makes this impractical.
|
| |
|
|
|
|
| |
Mostly works.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is supposed to be the equivalent of \[ \] in Bash PS1...
>Note that since the command line editors try to figure out how long the
>prompt is (so they know how far it is to edge of the screen), escape
>codes in the prompt tend to mess things up. You can tell the shell not
>to count certain sequences (such as escape codes) by prefixing your
>prompt with a non-printing char- acter (such as control-A) followed by
>a carriage return and then delimiting the escape codes with this
>non-printing character. If you don't have any non-printing characters,
>you're out of luck... BTW, don't blame me for this hack; it's in the
>original ksh.
<http://blog.0xpebbles.org/ksh-prompt-coloring-example>
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Turns out that `typeset` only makes a variable local if the function was
declared with this syntax. This actually makes a fair bit of sense if I
think about it. Wouldn't do this in Bash though.
|
| |
|
|
|
|
| |
mksh can't into it
|
|
|
|
| |
Not needed really
|
|
|
|
| |
Turns out ksh93 at least does actually do it
|
| |
|
| |
|
|
As part of a foray into more active use of ksh and derivatives.
|