usually I start gnuplot from a terminal (Ubuntu 12.04) by loading a scriptfile and then continue to work in an interactive session:
gnuplot myscript.gp -
No problem here, even though the history is not loaded, which I would prefer, but this discussion belongs maybe elsewhere.
When I start gnuplot (current development version) like this (or with a -e command) and then trigger an error e.g. by typing an invalid command, i get
$ src/gnuplot -e "set xran [0:1]" -
gnuplot immediately closes and leaves me with an unusable terminal, probably due to broken pipes. I bisected this problem back to commit
08cd687 New test for whether a session is interactive or non-interactive
which introduced a new test by looking whether -e or a scriptfile was given in argv and then switched to interactive=false. When I comment out this test in the latest commit everything works fine.