I also have the problem in bash, as the history is not written until the shell exits (having it write history command-for-command results in interleaving histor

I also have the problem in bash, as the history is not written until the shell exits (having it write history command-for-command results in interleaving history with commands from other sessions, which doesn't work well for me). But in bash, backgrounding works, so it's not an issue.