Earlier quoted context omitted.
I agree that it's confusing. To get the expected result, the user would have to use either $ gpg --clearsign (makes it obvious that the message is part of the resulting message.txt.asc file) or $ gpg --detachsign (which creates a .txt.sig file) or $ gpg -a --detachsign (which creates a .txt.asc file).
I use pgp daily with my email. I value it. It's good software. But let's be honest, SSL and pgp are the best we can do to secure comms from http to smtp today? Key/cert management is an epic fail from a usability pov. Is it done? Yes, because there is NO other choice. But pgp will never ever be anything but a niche application for the paranoid. SSL? I don't think anyone is going to argue it doesn't need to be scrappe…
The UX is just horrendous, and none of the GUI tools improve on that.