| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
`stty tab0` is not even in OpenBSD; these are way more trouble than
they're worth.
|
|
|
|
| |
Also prefix with `command -p`
|
| |
|
| |
|
| |
|
|
|
|
| |
So far I don't like SlackWare's shell setup very much at all
|
| |
|
| |
|
| |
|
|
|
|
| |
More trouble than it's worth
|
|
|
|
| |
Wrap it in curly brackets to make it a compound command
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NetBSD sh(1) and possible others don't tolerate a `return` short-circuit
for ENV, which means that because that implementation also sources ENV
if set regardless of whether the shell is interactive or not, all of the
interactive stuff in ~/.shrc and ~/.shrc.d gets uselessly sourced and
loaded up for non-interactive invocations of sh(1).
To work around this, I've set ENV to be a new ~/.shinit file instead,
which sources the ~/.shrc file only if the shell is interactive.
~/.shinit is the filename suggested in the man page for NetBSD sh(1) and
Debian dash(1) as well.
NetBSD's documented behaviour seems to be contrary to POSIX 2003:
> ENV: This variable, when and only when an interactive shell is
> invoked, shall be subjected to parameter expansion (see Parameter
> Expansion ) by the shell, and the resulting value shall be used as a
> pathname of a file containing shell commands to execute in the
> current environment.
No matter; this works fine, and makes non-interactive invocations of
sh(1) on NetBSD much faster.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's not available on default installs of any of the three major
open-source BSDs, and isn't specified by POSIX. I only noticed this
because the implement of sh(1) in NetBSD 7.0 seems to emit errors from
calls to `command -p` to the terminal, regardless of any redirection of
standard output and error:
$ uname -a
NetBSD faeroes 7.0.1_PATCH NetBSD 7.0.1_PATCH (GENERIC.201607220540Z) amd64
$ command -p setterm
setterm: not found
$ command -p setterm >/dev/null
setterm: not found
$ command -p setterm >/dev/null 2>&1
setterm: not found
|
|
|
|
| |
Turns out they're POSIX variables!
|
| |
|
| |
|
| |
|
|
|
|
| |
So that it's overridden in the correct order by pdksh
|
| |
|
|
|
|
|
|
| |
I don't fully understand why I have to do it this way yet, but if I
don't, calling SSH with a command raises "stdin: not a terminal" because
~/.bashrc was called.
|
|
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.
|