| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
They're nicer to read this way.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Include username/hostname if no SSH variables
|
|
|
|
|
|
|
| |
The manual page for mksh hints that the escaped initial character should
in fact be a carriage return, not a newline. That seems to work really
well. The newline variable was an empty string before this commit anyway
because it was stripped by the subshell expansion.
|
|
|
|
|
|
|
| |
That is, include e.g. "ksh:" as a prefix to the prompt if the user
appears to have Bash or Zsh (or anything else) as their login shell.
This is probably imperfect, but it's a start.
|
|
|
|
|
| |
e.g. for a namespaced branch "foo/bar/bar", don't strip the leading part
off
|
|
|
|
|
| |
Causes a bit too much curliness in configuration; may need a more
comprehensive approach.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Already works in ksh93 and mksh. Trapping C-l in ksh93 interferes with
the builtin SIGWINCH handling, clearing the screen every time the window
resizes, and I can't find a good way to work around it. Probably best
not to fight this.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
<http://unix.stackexchange.com/questions/272591/how-to-make-ctrl-l-to-clear-screen-in-ksh-under-red-hat-linux/272720#272720>
|
|
|
|
|
|
| |
Just starting with what I know and seeing if I can make ^L work the same
way it does in Bash. Once I understand this a bit better I intend to
have a crack at writing some dynamic completion for ksh93.
|
| |
|
| |
|
|
|
|
|
| |
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.
|