aboutsummaryrefslogtreecommitdiff
path: root/ksh
Commit message (Collapse)AuthorAgeFilesLines
* Remove unneeded typeset callTom Ryder2016-12-301-1/+0
|
* Deal with the kshes' varying treatment of ! in PS1Tom Ryder2016-12-281-2/+22
|
* Quiet a shellcheck errorTom Ryder2016-12-281-0/+1
| | | | | Like in 3828a1f, this variable actually does get set before use, but not in a place ShellCheck could be reasonably expected to find
* Change quoting mechanismTom Ryder2016-12-271-1/+1
|
* Fix an issueTom Ryder2016-12-271-1/+1
| | | | End the prompt subshell with a : to reset $?
* Preserve job count quickly for kshTom Ryder2016-12-271-3/+1
|
* Tell ShellCheck to ignore an errorTom Ryder2016-12-271-0/+1
| | | | | ret actually is assigned, just not in any place ShellCheck could reasonably be expected to find
* Realised easy win avoiding subshellsTom Ryder2016-12-271-5/+1
| | | | And also the PROMPT_RETURN fudge in Bash/Zsh
* Put exit value of previous command in ksh PS1Tom Ryder2016-12-271-11/+7
| | | | Found a way to do this that seems to work in all the KSHes I've tried
* Use more compatible checkTom Ryder2016-12-221-1/+1
|
* Limit keep() to ksh93Tom Ryder2016-12-221-2/+9
| | | | | FreeBSD pdksh doesn't even have complete typeset -p output, nor printf %q, which I think makes this impractical.
* Use . not sourceTom Ryder2016-12-221-1/+1
|
* Fork keep() to kshTom Ryder2016-12-221-0/+152
| | | | Mostly works.
* Use clearer logic for prompt color settingTom Ryder2016-12-211-8/+7
|
* Attempt at properly escaping non-printing charsTom Ryder2016-12-191-1/+6
| | | | | | | | | | | | | | | | 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>
* Block a well-intended shellcheck errorTom Ryder2016-12-191-0/+1
|
* Request version with "ver" shortcut not promptTom Ryder2016-12-192-12/+6
|
* Attempt a much saner approach to managing SHLVLTom Ryder2016-12-191-7/+4
|
* Defer kshrc loading until after shrc all loadedTom Ryder2016-12-181-5/+2
|
* Add ksh version distinguisher to promptTom Ryder2016-12-181-2/+12
|
* Change tack; force ENV if the file existsTom Ryder2016-12-181-6/+0
|
* Change syntax of ksh prompt func declarationTom Ryder2016-12-181-1/+1
| | | | | | 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.
* Undo strange default for login ksh93 ENVTom Ryder2016-12-181-0/+6
| | | | I haven't yet figured out why it does this
* Still improving ksh-guessing heuristicsTom Ryder2016-12-171-7/+14
|
* Move ksh.sh shim into ksh subdirTom Ryder2016-12-171-0/+30
| | | | | So it doesn't get installed on systems where I don't use ksh, since it's mostly not needed
* Improve accuracy of commentTom Ryder2016-12-171-1/+2
|
* Remove for loop from ksh prompt defTom Ryder2016-12-171-1/+3
| | | | mksh can't into it
* Move HOSTNAME call into shrcTom Ryder2016-12-171-3/+0
|
* Knock out $HOST from kshrcTom Ryder2016-12-172-3/+2
| | | | Not needed really
* Add SHLVL handling for kshTom Ryder2016-12-171-0/+8
| | | | Turns out ksh93 at least does actually do it
* Resolve a few ksh version differencesTom Ryder2016-12-172-16/+24
|
* Correct a "local" to "typeset"Tom Ryder2016-12-171-1/+1
|
* Rename all pdksh stuff to kshTom Ryder2016-12-172-0/+214
As part of a foray into more active use of ksh and derivatives.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-27 05:32:45 +0000