To reproduce, either on a macOS or FreeBSD system,

$ ls | wc # or any other piped commands

will result a setpgid error, while most of time will give correct result.

Default bash in macos is 3.2.57(1)-release.

User should be able to back up this directory.

Currently goal is backing up to a cloud. E.g. box.com supports WebDAV, which is very friendly to command line interface such as libcurl.

Intuitive example command:
$ nidus backup --name my_site_name
$ nidus restore --name my_site_name

https://superuser.com/questions/366930/how-do-i-get-the-git-pager-to-clean-up-screen-output-after-exit

User will feel easier modifying the hooks than creating them.

To reproduce:

$ VAR=value echo hello

comparing to

$ echo hello

In some cases, remote connections depend on local bashrc to source the remote /etc/bashrc. In non-interactive remote connections, /etc/bashrc should still be sourced.
As a result, sourcing /etc/bashrc should be moved ahead of the early exit by [ -z "$PS1" ] && return

... and also think of adding the current configs (tmux, git aliases) as a nice plugin.

Currently after command cd, an automatic ls is executed. Shortcomings:

1. the command ls is not always desired for everyone.
2. user should be able to EASILY disable the auto ls.
3. to maximize compatibility (most over BSD/Darwin and Linux), only very limited POSIX ls command can be used; in contrast, by using a hook, user is able to easily define a fancy ls that's best for the underlying OS/distribution.

See also: commit 66661c0

This makes people less want to try nidus.