From: Eliot Moss <moss@cs.umass.edu>
To: "KAVALAGIOS Panagiotis (EEAS-EXT)"
<Panagiotis.KAVALAGIOS@ext.eeas.europa.eu>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: cut and paste doesn't work
Date: Thu, 21 Jan 2021 11:15:49 -0500 [thread overview]
Message-ID: <8d868731-044e-0b29-203b-f3ec257bcfb2@cs.umass.edu> (raw)
In-Reply-To: <57432e1c8a2142978a77e6b118427391@BELBRU-EXMP101.eeas.europa.eu>
On 1/21/2021 2:34 AM, 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
I observe that it is possible to get a list of what is installed and do a more automated install of
the same things again. The techniques were posted recently in other threads, I believe. I agree
that this would be more reliable than trying to copy the file structure,
unless you really really know what you're doing.
Regards - Eliot Moss
next prev parent reply other threads:[~2021-01-21 16:15 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
2021-01-21 12:16 ` Hamish McIntyre-Bhatty
2021-01-21 12:40 ` Fergus Daly
2021-01-21 16:15 ` Eliot Moss [this message]
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=8d868731-044e-0b29-203b-f3ec257bcfb2@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=Panagiotis.KAVALAGIOS@ext.eeas.europa.eu \
--cc=cygwin@cygwin.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.
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).