Dear Maintainer,

`reportbug` should catch SIGINT, save the current report in a temporary
location (maybe not DRAFTPATH because it might be `/tmp/`, but `/var/tmp/`) and
 inform the user about that location.

why? the only point where it matters, is the last step at the menu
asking to submit the report, and there is already an option to save
the current draft and exit. If you press Ctrl+c, then it's your fault.

you can customize this path; all these reports start to be kinda
annoying, mostly because you didnt spend *any* time reading the doc or
previous reports and you're wasting a big chunk of my time.

Am 30.11.2015 um 00:57 schrieb Sandro Tosi:
Same here. You're not even taking the time to understand what I'm
pointing at. Adjusting the path doesn't help if SIGINT isn't caught. I
just waisted a big chunk of my time being force to deal with a program
that doesn't have an intuitive interface and feedback and requires to
read a large pile of docs just to get a simple report filed. It's just
two sides of the same medal. I want to improve the experience of Debian
users - if that's time wasting for you, you took the wrong
responsibility as package maintainer. RTFM isn't a generic argument to
leave users with something that "just works" or that "a lot of people
are using without problems".

it is not intuitive *for you*, that doesnt mean that's an absolute
statement for all reportbug users.

no it's not: if you dont read the doc, how are you supposed to know
what the tool supports? just by having an 'intuitive interface'? sadly
that's not enough in every case.

great! start providing patches, else you are just trying to prove
you're right, while tons of other people dont agree/feel the same with
your statements and you're doing nothing concretely to improve that
experience you seem to care so much.

I guess we can discuss this back when you'll be a package maintainer.

Time was spent writing that documentation, so maybe you can be a
little less disrespectful of it and actually read it.

Again, I'm wasting a lot of time with all this replies (which are
really not helping making reportbug any better), time I am diverting
for actual debian work. So refrain for reply any further until you
have understood how reportbug works by reading its doc, and eventually
consult a user-support forum like debian-users mailing list for
followup clarifications.