Explicitly check for the __ash_* functions before bailing.

[sjjf]

ASH_SESSION_ID seems to be set in some cases where the file hasn't
actually been sourced, so explicitly check for the functions being
defined before bailing.

Addresses issue #4

[barabo]

I'd be interested to know what leads to this situation for you.

Also, please use grep -q instead of grep -s, since the latter only suppresses error messages whereas the former suppresses all output.

Thanks!

[barabo]

Thanks for the PR. How does this look?
[[ -n "${ASH_SESSION_ID}" ]] && declare -F __ash_log | grep -q . && return

[sjjf]

I log in, run a single gnome-terminal via the GUI, then I run a bunch more gnome-terminals from a script run on the command line in the original terminal. The environment variables are exported, but not the functions, so the subsequent terminals /think/ they're running an existing session but they don't have access to the functions.

Why is the function export at the end of the file commented out? If you're exporting the session id and so forth (particularly the PROMPT_COMMAND) isn't exporting the functions essential? Re-sourcing the definitions is a workaround for the lack of function exports, but given they're /there/ but commented out I'm assuming there was a reason for the change . . .

[barabo]

Thanks!