all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 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 09:22:12 +0300	[thread overview]
Message-ID: <83r3m1a5bf.fsf@gnu.org> (raw)
In-Reply-To: <ad82df82-fa76-4fcf-bd11-0b15de8dcb3a@default>

> Date: Sun, 13 Sep 2015 13:58:57 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 21471@debbugs.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".





  reply	other threads:[~2015-09-14  6:22 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 [this message]
     [not found]   ` <<ad82df82-fa76-4fcf-bd11-0b15de8dcb3a@default>
     [not found]     ` <<83r3m1a5bf.fsf@gnu.org>
2015-09-14 13:47       ` Drew Adams
     [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

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

  git send-email \
    --in-reply-to=83r3m1a5bf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21471@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.