From: "Andy Hall" <fixpertise-consulting@comcast.net>
To: "'Thomas Wolff'" <towo@towo.net>, <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] Updated: mintty 2.9.4
Date: Tue, 13 Nov 2018 17:52:00 -0000 [thread overview]
Message-ID: <000e01d47b79$95f52fc0$c1df8f40$@comcast.net> (raw)
In-Reply-To: <559c8b3d-af18-626a-c2bb-14d546d288ac@towo.net>
> -----Original Message-----
> From: cygwin-owner@cygwin.com <cygwin-owner@cygwin.com> On Behalf Of Thomas Wolff
> Sent: Tuesday, November 13, 2018 12:08 AM
> To: cygwin@cygwin.com
> Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.4
>
> Am 12.11.2018 um 22:50 schrieb Andrey Repin:
> > Greetings, Thomas Wolff!
> >
> >> I have uploaded mintty 2.9.4 with the following changes:
> >> Terminal features
> >> * Copy as HTML (#811).
> > I should agree with Achim. This feature is utterly broken.
> > Copied fragments are inserted as HTML TABLES(of all the things!) with no formatting whatsoever.
> OK, it shall be made configurable. But please describe in which ways
> workflows are broken and how / in which application HTML tables (HTML
> source?) would appear.
> Of course plain text clipboard format is still supplied (multiple
> formats can be copied to the Windows clipboard at the same time,
> otherwise I wouldn't have enabled this by default), and the assumption
> was that an application pasting plain text from the Windows clipboard
> would still retrieve that.
>
For what it's worth, I tried some simple examples.
Copy and paste into notepad, notepad++ or another mintty window resulted in plain text being copied.
Paste into MS Word 2016 gives you three options: "Keep Source Formatting", "Merge Formatting" and "Keep Text Only". If I selected "Keep Source Formatting", the result is a single cell table containing the text copied. The other options resulted in plain text being copied. The former is actually useful if you happen to be writing documentation about how to do something at the command line level, but there are flaws. In my case, the inserted table had a black background and white test and it was not easy to change this.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-11-13 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 19:39 Thomas Wolff
2018-11-12 20:07 ` Achim Gratz
2018-11-12 22:05 ` Andrey Repin
2018-11-12 23:30 ` KARL BOTTS
2018-11-13 8:07 ` Thomas Wolff
2018-11-13 15:35 ` Andrey Repin
2018-11-13 22:55 ` Thomas Wolff
2018-11-13 23:05 ` Andrey Repin
2018-11-13 23:16 ` Thomas Wolff
2018-11-13 17:52 ` Andy Hall [this message]
2018-11-13 18:31 ` Achim Gratz
2018-11-13 18:37 ` Lemke, Michael ST/HZA-ZIC2
2018-11-13 21:16 ` Brian Inglis
[not found] ` <b5bd3e0f-4a28-2f60-a53c-e246ebd3fa40@towo.net>
2018-11-14 14:59 ` Brian Inglis
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='000e01d47b79$95f52fc0$c1df8f40$@comcast.net' \
--to=fixpertise-consulting@comcast.net \
--cc=cygwin@cygwin.com \
--cc=towo@towo.net \
/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.
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).