From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 31815@debbugs.gnu.org
Subject: bug#31815: 27.0; Inappropriate use of curly quotes in `info.el'
Date: Mon, 16 Jul 2018 14:12:07 +0000 (UTC) [thread overview]
Message-ID: <d6731719-e7d9-4b5c-8b78-40e88a945a15@default> (raw)
In-Reply-To: <CAM-tV-8ndM+rYQvbBLozO36eZz1-YXR_P2cMZHoMLZR3d8HZbw@mail.gmail.com>
> > The point of a bug report is to state the problem
>
> I wish you would follow this advice when making bug reports. For
> example, in this report, instead of proposing a partial fix and
> assuming that it's clear that you're asking for that restoration +
> some other fix, ask something like: "these characters cause X problems
> in scenario Y, is there an ASCII-only equivalent we can use?"
I agree. I try to do that, and will try harder. Sometimes
pointing toward what might be better can help make the problem
clearer. And sometimes that bleeds over into what can sound
like a description of a solution (or even the solution).
For the record and future reference: That's never my intention.
Except when I might actually propose a solution (e.g. a patch),
I just report bugs. And even when I might propose a solution
(e.g. patch) I don't insist on considerations that are purely
implementation, e.g., performance.
I might express an opinion about the effect on users of this
or that proposed solution, but I don't claim that code I offer
is the most performant etc. possible.
(I might also express a slight opinion about coding style,
names etc., readability etc., but again, such an opinion is
not so important. I care about getting a bug fixed, not so
much about how it is fixed internally, i.e., in ways that
are not user-observable. I do care to some extent about
the usability of the code itself, i.e., for users of the
code.)
next prev parent reply other threads:[~2018-07-16 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<4cce0ca1-f9d1-41cb-a2a2-e54464aa2626@default>
[not found] ` <<83po0t33r3.fsf@gnu.org>
2018-07-13 15:57 ` bug#31815: 27.0; Inappropriate use of curly quotes in `info.el' Drew Adams
2018-07-13 16:15 ` Noam Postavsky
2018-07-13 16:28 ` Drew Adams
2018-07-14 15:12 ` Noam Postavsky
2018-07-15 1:36 ` Drew Adams
2018-07-15 21:28 ` Noam Postavsky
2018-07-15 22:09 ` Drew Adams
2018-07-16 14:03 ` Noam Postavsky
2018-07-16 14:12 ` Drew Adams [this message]
2018-07-13 17:27 ` Eli Zaretskii
2018-07-13 17:51 ` Drew Adams
2018-07-13 18:44 ` Eli Zaretskii
2018-06-13 17:31 Drew Adams
2018-06-14 13:18 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6731719-e7d9-4b5c-8b78-40e88a945a15@default \
--to=drew.adams@oracle.com \
--cc=31815@debbugs.gnu.org \
--cc=npostavs@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).