all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Glenn Morris'" <rgm@gnu.org>, <9074@debbugs.gnu.org>
Subject: bug#9074: 24.0.50; problems trying to mail bug report, again
Date: Wed, 13 Jul 2011 17:05:35 -0700	[thread overview]
Message-ID: <0B0D5E9653C044619A7E666BB31A90E3@us.oracle.com> (raw)
In-Reply-To: <19998.12336.856901.912384@fencepost.gnu.org>

> > THIS bug report is only about the RIDICULOUS obstacle-course dialog
> > we make users go through now, after asking them to please start each
> > bug report from emacs -Q.
> 
> I never know who "we" is supposed to be.

Emacs Dev and all other little elves such as myself who contribute to its
development.

> "We" don't ask people to submit bug reports from emacs -Q, that adds
> no value. What the instructions ask for is a *recipe starting from
> emacs -Q that shows the problem*.

Excuse my shorthand.  That is precisely what I meant.

> This is a way to get you to show how
> to reproduce the problem. Send the actual report from your normal,
> configured Emacs.

No.  For many people, including me, their normal, configured Emacs is far too
complex to be the basis of most bug reports.  We do not want to pick all of a
user's extra customizations, if we can help it.

I don't know where this mailer stuff is saved, but if it is saved in the user's
`custom-file' or init file then in order to start from emacs -Q and get to a
reasonable bug-report state s?he needs to answer this mail nonsense EACH time.

This is (should be considered) totally unacceptable.  It works against what _we_
want in terms of bug reporting.  Not to mention that it is simply not nice to
users.

At the very least we should be able to get rid of the backwardness: making users
who will ultimately hit `n' for SMTP configuration jump through lots of
irrelevant obstacles.  Ask the SMTP question first, if you absolutely must ask
it each time, and then DTRT for a `n' response.






  reply	other threads:[~2011-07-14  0:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 23:39 bug#9074: 24.0.50; problems trying to mail bug report, again Drew Adams
2011-07-13 23:54 ` Glenn Morris
2011-07-14  0:05   ` Drew Adams [this message]
2011-07-14  8:29     ` Lawrence Mitchell
2011-07-14 14:25       ` Drew Adams
2011-07-22 15:05         ` Drew Adams
2011-08-02  4:06           ` Stefan Monnier
2011-08-02 17:34             ` Drew Adams
2011-08-02 17:44               ` Lennart Borgman
2011-08-02 18:00                 ` Lars Magne Ingebrigtsen
2011-08-02 19:00                   ` Drew Adams
2011-08-02 19:12                     ` Lars Magne Ingebrigtsen
2011-08-02 21:07                       ` Drew Adams
2011-08-02 21:17                         ` Lars Magne Ingebrigtsen
2011-08-02 21:40                           ` Drew Adams
2011-08-02 22:11                             ` Lars Magne Ingebrigtsen
2011-08-04 14:03                             ` Jason Rumney
2011-08-04 15:38                               ` Drew Adams
2011-08-09 22:37                                 ` Drew Adams
2011-08-22 15:39                                   ` Drew Adams
2011-08-02 20:16                     ` Lars Magne Ingebrigtsen
2011-08-02 15:44 ` Lars Magne Ingebrigtsen
2011-08-02 16:24 ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0B0D5E9653C044619A7E666BB31A90E3@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=9074@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.