From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 21471@debbugs.gnu.org
Subject: bug#21471: 25.0.50; REGRESSION: bug report with text from Info has spurious escape chars
Date: Mon, 14 Sep 2015 06:47:12 -0700 (PDT) [thread overview]
Message-ID: <80cd3503-4afd-45e3-a70b-d7f3ff676aea@default> (raw)
In-Reply-To: <<83r3m1a5bf.fsf@gnu.org>>
> > Is there some reason not to proceed that way? Am I missing
> > something?
>
> Reliability. The command to report a bug must be 100% reliable, and
> it must work out of the box in "emacs -Q".
We already let users configure how bug reporting interacts
with their mail environment. Why not provide a user option
that handles this correctly?
Even in `emacs -Q', I should be able to copy+paste non-ASCII
text, assuming my mail client can handle it.
I'm sorry to say it, but your response about this really
sounds like a cop-out. This might not be the most urgent
bug, but I cannot see that this is something that should
be foisted on the user as being her problem (just don't
use `C-c C-c' and instead create a mail-client message
by hand and paste copied non-ASCII text into it manually).
That is not a reasonable answer, IMHO. But whatever.
next prev parent reply other threads:[~2015-09-14 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<cde9bbc9-378e-4656-8d10-caf2b8e208b7@default>
[not found] ` <<83wpvu9jf1.fsf@gnu.org>
2015-09-13 20:58 ` bug#21471: 25.0.50; REGRESSION: bug report with text from Info has spurious escape chars Drew Adams
2015-09-14 6:22 ` Eli Zaretskii
[not found] ` <<ad82df82-fa76-4fcf-bd11-0b15de8dcb3a@default>
[not found] ` <<83r3m1a5bf.fsf@gnu.org>
2015-09-14 13:47 ` Drew Adams [this message]
[not found] <<55F5CBA0.90406@cs.ucla.edu>
[not found] ` <<065d972a-464a-4d55-9b67-29b3827caeb9@default>
[not found] ` <<83si6ha5dd.fsf@gnu.org>
2015-09-14 13:41 ` bug#21471: 25.0.50; " Drew Adams
2015-09-14 16:38 ` Paul Eggert
2015-09-14 18:20 ` Eli Zaretskii
2015-09-14 21:10 ` Paul Eggert
2015-09-15 6:56 ` Eli Zaretskii
2015-09-13 15:07 bug#21471: 25.0.50; REGRESSION: " Drew Adams
2015-09-13 19:16 ` bug#21471: 25.0.50; " Paul Eggert
2015-09-13 20:55 ` Drew Adams
2015-09-14 6:21 ` Eli Zaretskii
2015-09-13 20:02 ` bug#21471: 25.0.50; REGRESSION: " 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=80cd3503-4afd-45e3-a70b-d7f3ff676aea@default \
--to=drew.adams@oracle.com \
--cc=21471@debbugs.gnu.org \
--cc=eliz@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 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).