From: Andrey Repin <anrdaemon@yandex.ru>
To: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>, cygwin@cygwin.com
Subject: Re: cut and paste doesn't work
Date: Thu, 21 Jan 2021 13:09:23 +0300 [thread overview]
Message-ID: <1642602024.20210121130923@yandex.ru> (raw)
In-Reply-To: <DB7PR02MB39968D85AE3EACF96064C683E7A10@DB7PR02MB3996.eurprd02.prod.outlook.com>
Greetings, Hamish McIntyre-Bhatty!
> On 21/01/2021 07:34, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>>> -----Original Message-----
>>> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Thomas Wolff
>>> Sent: 21 January 2021 02:08
>>>
>>> Am 20.01.2021 um 21:31 schrieb Wojciech Puchar:
>>>> trying to mark text in cygwin windows by mouse doesn't work at all.
>>>> Windows 10.
>>>>
>>>> The same cygwin 64 installation on windows 7 works properly.
>>>>
>>>> It was installed to windows 10 host by simply copying whole c:\cygwin
>>>> directory.
>>>>
>>>> Everything works except cut&paste.
>>> What does `ls -l /dev/clipboard` say?
>>> Copying the filesystem rather than installing loses some special file
>>> properties, especially in the /dev folder.
>>> Not sure whether it's possible to fix that with `mknod`.
>> There might be other problems as well. Symlinks are also going to be affected. We couldn't find a reliable solution back in Win7 to simply copy Cygwin installation by preserving the symlinks in a zip archive.
>>
>> I would strongly advise to perform a normal installation and simply copy only the contents of your Cygwin home directory (C:\Cygwin\home\<username>). It will be quicker that trying to identify and fix all the possible issues.
>>
>> Panos
> NB: I don't think I have this problem, but I do seem to have an
> unrelated problem where as soon as I select any text in mintty it
> immediately replaced my clipboard contents which that selection.
This is standard behavior for a terminal for as long as I recall.
> This is very annoying, because when copying text to mintty I frequently click
> and drag a small amount of text by accident.
> Is this configurable somehow?
Of course it is configurable.
mintty - Options - Selection.
--
With best regards,
Andrey Repin
Thursday, January 21, 2021 13:07:38
Sorry for my terrible english...
next prev parent reply other threads:[~2021-01-21 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 20:31 Wojciech Puchar
2021-01-21 1:08 ` Thomas Wolff
2021-01-21 7:34 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-01-21 9:11 ` Hamish McIntyre-Bhatty
2021-01-21 10:09 ` Andrey Repin [this message]
2021-01-21 12:16 ` Hamish McIntyre-Bhatty
2021-01-21 12:40 ` Fergus Daly
2021-01-21 16:15 ` Eliot Moss
2021-03-04 10:14 ` Wojciech Puchar
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=1642602024.20210121130923@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=hamishmb@live.co.uk \
/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).