From: Michael Albinus <michael.albinus@gmx.de>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 26036@debbugs.gnu.org, tramp-devel@gnu.org
Subject: bug#26036: tramp (2.2.13.25.1); bug report form is so frustrating
Date: Thu, 09 Mar 2017 19:57:01 +0100 [thread overview]
Message-ID: <87zigujn2a.fsf__39851.768493145$1489085898$gmane$org@detlef> (raw)
In-Reply-To: <87ziguv9g1.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Thu, 09 Mar 2017 21:58:06 +0800")
積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
>>>>>> "MA" == Michael Albinus <michael.albinus@gmx.de> writes:
> MA> 積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
>
> MA> Hi Dan,
>
>>> Your bug report form is so frustrating.
>>>
>>> At its top is a line (setq tramp-verbose 9) which the user is not
>>> allowed to put his cursor nearby.
>
> MA> At the top of the bug report, the text is shown with the `display' text
> MA> property. This is because this text shall not be sent with the message.
>
> MA> This is a usual technique for bug reports.
>
> MA> Best regards, Michael.
>
> I'll CC bug-gnu-emacs to tell them that better would just be plain text
> with the words
> --text-below-won't-be-sent
> Bla bla bla
> --text-above-won't-be-sent
>
> 1. it is now clear that the magic region won't be sent.
> 2. The user can finally copy words on *his* screen (he bought the
> computer. He ought to be allowed to copy... without needing to try
> SHIFT etc.)
This is not a bug. Explanation text in the bug report is not intended to
be touched.
Best regards, Michael.
next prev parent reply other threads:[~2017-03-09 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8737enkr6y.fsf@jidanni.org>
2017-03-09 13:58 ` bug#26036: tramp (2.2.13.25.1); bug report form is so frustrating 積丹尼 Dan Jacobson
2017-03-09 18:57 ` Michael Albinus [this message]
2017-03-10 0:17 ` 積丹尼 Dan Jacobson
2017-03-10 7:57 ` Michael Albinus
2017-03-10 8:06 ` 積丹尼 Dan Jacobson
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='87zigujn2a.fsf__39851.768493145$1489085898$gmane$org@detlef' \
--to=michael.albinus@gmx.de \
--cc=26036@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=tramp-devel@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 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.