From: Noam Postavsky <npostavs@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 31815@debbugs.gnu.org
Subject: bug#31815: 27.0; Inappropriate use of curly quotes in `info.el'
Date: Mon, 16 Jul 2018 10:03:17 -0400 [thread overview]
Message-ID: <CAM-tV-8ndM+rYQvbBLozO36eZz1-YXR_P2cMZHoMLZR3d8HZbw@mail.gmail.com> (raw)
In-Reply-To: <4f6094d3-9054-4ba2-a35e-c12c68bd9edf@default>
On 15 July 2018 at 18:09, Drew Adams <drew.adams@oracle.com> wrote:
>> I'm not sure
>> if you are just ignoring the effect of the change you propose, or you
>> have some additional changes in mind.
> It is clear from
> the context that I was not proposing that only restoring
> the exact same text in the Lisp code is an acceptable fix.
It wasn't clear to me.
> 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?"
next prev parent reply other threads:[~2018-07-16 14:03 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 [this message]
2018-07-16 14:12 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-8ndM+rYQvbBLozO36eZz1-YXR_P2cMZHoMLZR3d8HZbw@mail.gmail.com \
--to=npostavs@gmail.com \
--cc=31815@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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.