in reply to Re^2: Reporting a bug in Perl is tricky
in thread Reporting a bug in Perl is tricky

Thanks for all the tips.

Welcome

I just created the Bitcard accound and added the bug manually. I thought at first that "Bitcard" was some private company. It's all rather user unfriendly

Why not to just use the friendly interface you just thanked me for explaining?

I started perlbug from Ubuntu Linux, and how would I know whether it is misconfigured to send e-mails if it reports "OK" at the end?

perlbug (and other programs using your mail system) have no control over what your mail system does after they submit an email to it, and they no reasonable way to query it.

  • Comment on Re^3: Reporting a bug in Perl is tricky

Replies are listed 'Best First'.
Re^4: Reporting a bug in Perl is tricky
by soonix (Chancellor) on May 18, 2016 at 08:31 UTC
    I haven't used perlbug, but from the discussion (and from the source :-)) it might help to simply change the text from "Message sent" to "Message has been handed over to your mail system". For anyone who is capable of using perlbug in the first place, that should be sufficient. Rats! Now I have to find out how to make a pull request :-)

    Update: https://rt.perl.org/Public/Bug/Display.html?id=128180

[reply]

      it might help to simply change the text from "Message sent" to "Message has been handed over to your mail system"

      That's just a noisy way of saying the same thing. Sending an email is a chain of handoffs, and there's never a guarantee that a sent email will reach its target.

[reply]

        You know that, and therefore for you it is mere noise. Does the "average" person reporting perl bugs know it?

        I admit that finding bugs in perl that don't turn out to be bugs in one's own code, calls for a certain amount of expertise, and so anyone using perlbug might know this anyway, and perhaps the OP was an exception, but …
[reply]

In Section Seekers of Perl Wisdom