public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "KAVALAGIOS Panagiotis (EEAS-EXT)" <Panagiotis.KAVALAGIOS@ext.eeas.europa.eu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: cut and paste doesn't work
Date: Thu, 21 Jan 2021 07:34:55 +0000	[thread overview]
Message-ID: <57432e1c8a2142978a77e6b118427391@BELBRU-EXMP101.eeas.europa.eu> (raw)
In-Reply-To: <913c6bf6-a153-e162-36a3-cdd1d9dc240e@towo.net>

> -----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

Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017


  reply	other threads:[~2021-01-21  7:34 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) [this message]
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
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=57432e1c8a2142978a77e6b118427391@BELBRU-EXMP101.eeas.europa.eu \
    --to=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).