unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 31351@debbugs.gnu.org
Subject: bug#31351: 27.0; Cannot send bug report with Outlook if text includes backquoted sexps
Date: Thu, 3 May 2018 11:24:39 -0700 (PDT)	[thread overview]
Message-ID: <d4fa0a90-631b-444a-abe7-0beed40aecf1@default> (raw)
In-Reply-To: <<8336z8ppz3.fsf@gnu.org>>

> I see the problem, but I'm not sure it's the same problem, because it
> doesn't fit your description in two details: (a) the problem I see is
> not caused by anything in the message body -- in fact, I can reproduce
> the problem with a "bug report" whose body consists of just "foo", in
> addition to the details collected by the command about my system; and
> (b) sending that problematic bug report works just fine in Emacs 25
> and all older versions, and is broken only in Emacs 26 and later.
> 
> The problem I see is not caused by backticks in the body, it is caused
> by quotes ".." in the Subject of the bug.  (I don't see how the body
> could have any effect on launching Outlook, since we pass the body
> through the system clipboard, and Outlook doesn't see it until you
> paste the body into Outlook.  So it cannot possibly prevent Outlook
> from starting correctly.)
> 
> To fix the problem I see, I installed on the release branch a fix,
> which is reproduced below.  Please re-verify that you indeed see a
> different problem -- I expect the patch below not to solve the problem
> if so.
> 
> Thanks.

Great. Thanks for taking a closer look.

It's funny though.  Before I tried simplifying the body, I did
try simplifying the Subject line, by removing the backquote,
the single quote, and the double-quotes.  That didn't fix it
for me.  But perhaps I didn't do what I thought I did.

Anyway, if you've found a fix, that's great.

BTW, it wasn't about having an effect on launching Outlook.
I already had Outlook open.  It was only about not creating
a new Outlook message with the header filled and the body
ready to be pasted as the bug-report text.

(I don't want to try testing this, as that will likely create
a useless bug report.  If you feel this fixes the problem
that's good enough for me, until/unless I run into it again.)





       reply	other threads:[~2018-05-03 18:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<43b34fd6-291d-475d-8c8d-65c58dd0f316@default>
     [not found] ` <<8336z8ppz3.fsf@gnu.org>
2018-05-03 18:24   ` Drew Adams [this message]
2018-05-03 18:59     ` bug#31351: 27.0; Cannot send bug report with Outlook if text includes backquoted sexps Eli Zaretskii
     [not found] <<<<<43b34fd6-291d-475d-8c8d-65c58dd0f316@default>
     [not found] ` <<<<<8336z8ppz3.fsf@gnu.org>
     [not found]   ` <<<<d4fa0a90-631b-444a-abe7-0beed40aecf1@default>
     [not found]     ` <<<<83y3h0o9a7.fsf@gnu.org>
     [not found]       ` <<<1d1d9379-4d74-4171-baf6-cead40e47c1d@default>
     [not found]         ` <<<83tvroo6ea.fsf@gnu.org>
     [not found]           ` <<3b184f18-5afe-46fa-a4c7-4cc74d08be57@default>
     [not found]             ` <<83efirtx8q.fsf@gnu.org>
2018-05-04 15:30               ` Drew Adams
2018-05-04 17:35                 ` Eli Zaretskii
     [not found] <<<<43b34fd6-291d-475d-8c8d-65c58dd0f316@default>
     [not found] ` <<<<8336z8ppz3.fsf@gnu.org>
     [not found]   ` <<<d4fa0a90-631b-444a-abe7-0beed40aecf1@default>
     [not found]     ` <<<83y3h0o9a7.fsf@gnu.org>
     [not found]       ` <<1d1d9379-4d74-4171-baf6-cead40e47c1d@default>
     [not found]         ` <<83tvroo6ea.fsf@gnu.org>
2018-05-03 20:11           ` Drew Adams
2018-05-04 12:35             ` Eli Zaretskii
     [not found] <<<43b34fd6-291d-475d-8c8d-65c58dd0f316@default>
     [not found] ` <<<8336z8ppz3.fsf@gnu.org>
     [not found]   ` <<d4fa0a90-631b-444a-abe7-0beed40aecf1@default>
     [not found]     ` <<83y3h0o9a7.fsf@gnu.org>
2018-05-03 19:41       ` Drew Adams
2018-05-03 20:01         ` Eli Zaretskii
2018-05-03  0:55 Drew Adams
2018-05-03  1:02 ` Noam Postavsky
2018-05-03  1:18   ` Drew Adams
2018-05-03 18:13 ` 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=d4fa0a90-631b-444a-abe7-0beed40aecf1@default \
    --to=drew.adams@oracle.com \
    --cc=31351@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).