aboutsummaryrefslogtreecommitdiff
path: root/pdksh
Commit message (Collapse)AuthorAgeFilesLines
* Add prompt return behaviour to pdkshTom Ryder2016-12-091-1/+7
| | | | | Turns out this simple approach does actually work, though I admit I do not fully understand why
* Fix accuracy of commentTom Ryder2016-12-091-2/+2
|
* Fork bash prompt changes to pdkshTom Ryder2016-09-201-105/+104
|
* Tidy pdksh prompt colors, switch to yellowTom Ryder2016-09-181-31/+26
| | | | I'm using blue prompts for work machines
* Fix an issue (silencing Git prompt errors)Tom Ryder2016-09-081-1/+1
|
* Restore old code for describing Git prompt commitTom Ryder2016-09-071-1/+2
| | | | | | | | | | | | | | | I'm really confused. I could have sworn this was working correctly (i.e. the --always option spat out a short reference to the commit as a fallback), but I must have been wrong. Maybe I hadn't installed the appropriate file when I was testing it. At first I thought this was a bug introduced in Git 2.10, but the short-circuit disregarding --always if --exact-match or --candidates=0 is set seems to have been in the `describe` builtin for ages. I must have just tested poorly; I can't see any other explanation in the source. No matter; this isn't much slower.
* Restore git symbolic-ref as first attemptTom Ryder2016-08-311-2/+4
| | | | | Otherwise if two branches point to the same commit, you can't be sure which one will show up.
* Port Git prompt improvements to pdkshTom Ryder2016-08-311-19/+33
|
* Fix a pdksh warningTom Ryder2016-08-241-1/+1
|
* If HEAD not set, suppress errorTom Ryder2016-08-231-1/+1
|
* Correct test written in previous commitTom Ryder2016-08-231-1/+2
|
* Check SSH_CLIENT *and* SSH_CONNECTION for promptTom Ryder2016-08-231-1/+1
|
* Port Bash prompt updates to pdkshTom Ryder2016-08-231-25/+30
|
* Port Bash Git prompt changes to pdkshTom Ryder2016-08-211-3/+19
|
* Add bash prompt Git fixes into pdkshTom Ryder2016-08-211-11/+9
|
* Drastically limit amount of history keptTom Ryder2016-08-181-1/+1
| | | | | | Reading really large files seems to be slow in Bash in general, but it's particularly bad in 4.4rc1. I keep encrypted snapshots of my HISTFILE on my home machine, so it's just a little extra step to search them.
* Use consistent syntax for sh source loopsTom Ryder2016-08-181-2/+1
|
* Move simple Bash/pdksh functions into POSIX shTom Ryder2016-08-1713-125/+0
| | | | | | | Have only translated the scripts that translate readily into POSIX sh for now. More complex stuff like that bd/pd/sd/ud navigation for Bash doesn't port as easily, mostly because there isn't an analogue for the "local" keyword in POSIX.
* Correct wrapping for a commentTom Ryder2016-08-151-1/+2
|
* Don't use git: prompt prefix if PROMPT_VCS unsetTom Ryder2016-08-151-2/+2
| | | | | All of my personal stuff is in Git, so this is only really applicable at work
* Remove square brackets around promptTom Ryder2016-08-151-1/+1
| | | | Just noise
* Port Git prompt function from Bash to pdkshTom Ryder2016-08-141-0/+49
|
* Port easy bashrc.d scripts to pdkshrc.dTom Ryder2016-08-1013-0/+125
| | | | | Have left out anything that requires non-trivial fixes, mostly due to variable scope or missing features.
* Name/point pdksh files specificallyTom Ryder2016-08-103-14/+14
| | | | | This frees up space to implement actual ksh88/ksh93 files specifically in future, as pdksh's feature set differs considerably
* Limit prompt setup to OpenBSD pdkshTom Ryder2016-08-092-3/+3
| | | | FreeBSD's one doesn't seem to support \u \w etc at all
* Adjust color for pdksh promptTom Ryder2016-08-091-1/+1
|
* Remove call to `prompt ret` from pdksh PS1Tom Ryder2016-08-091-1/+0
|
* Add kshrc.d/* sourcing to kshrcTom Ryder2016-08-091-0/+7
|
* Use sed(1) to count jobsTom Ryder2016-08-091-3/+1
| | | | | pdksh doesn't have <(process substitution). Ideally all of these functions will only use shell builtins, but sed will do OK for now.
* Use blue prompt for pdkshTom Ryder2016-08-091-2/+2
| | | | Nice quick way to distinguish which shell I'm using
* Remove PROMPT_RETURN from pdksh promptTom Ryder2016-08-091-11/+0
| | | | | | Realised that the absence of PROMPT_COMMAND in pdksh makes the strategy used for this impossible; will have to figure out something else. Hopefully I will not have to resort to putting it into a file.
* Remove bash-specific $FUNCNAME from pdksh promptTom Ryder2016-08-091-1/+1
| | | | | I can't find any equivalent in the pdksh manual; a fixed string will be fine for now.
* Change "local" to "typeset" for ksh promptTom Ryder2016-08-091-4/+4
|
* Make prompt printing call pdksh-compatibleTom Ryder2016-08-091-1/+1
| | | | | I don't think pdksh has a `declare -p (varname)` syntax from what I can tell. typeset -p prints all the variables though.
* Make declaration of PROMPT_RETURN pdksh-compatibleTom Ryder2016-08-091-2/+2
|
* Remove Bash-specific PROMPT_COMMANDTom Ryder2016-08-091-4/+1
|
* Remove bash-specific stuff from PS4Tom Ryder2016-08-091-1/+1
|
* Remove bash-specific PROMPT_DIRTRIMTom Ryder2016-08-091-6/+1
|
* Remove VCS display from prompt for nowTom Ryder2016-08-091-159/+0
| | | | | Requires porting; one major obstacle is the lack of a -d option for the read command, but this may not even be needed.
* Copy prompt.bash to kshrc.dTom Ryder2016-08-091-0/+284
| | | | Not ported yet
* Add bash-style prompt to pdkshTom Ryder2016-08-061-0/+3
| | | | Let's start with what we know
* Starting an attempt at pdksh configurationTom Ryder2016-08-061-0/+7
Not really sure how I'll approach this yet.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-24 22:05:43 +0000