public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: [PATCH] Cygwin: Make native clipboard layout same for 32- and 64-bit
Date: Wed, 27 Oct 2021 11:52:10 +0200	[thread overview]
Message-ID: <YXkhSr5WFf2rNk2b@calimero.vinschen.de> (raw)
In-Reply-To: <6403170a-9e5d-4b98-7ef9-3d11fb31c2c4@towo.net>

On Oct 27 11:01, Thomas Wolff wrote:
> Am 23.10.2021 um 07:35 schrieb Mark Geisert:
> > [...]
> > I'll try to get the v2 patch out over this weekend.  Same end-result for
> > same environments as the v1 patch, but incorporating all the comments I
> > received.
> > 
> > To that end, does Jon's suggestion of /usr/include/sys/cygwin.h seem
> > like the best location to define struct cygcb_t for use by both Cygwin
> > and cygutils package?
> > Thanks much,
> > 
> > ..mark
> 
> Mintty uses the Windows clipboard directly, so it does not face this problem
> so far. However, that results in a timestamp of 1st Dec 2006 for
> /dev/clipboard. In order to avoid a complete reimplementation of mintty
> clipboard handling ("never touch a running system"), would it be possible to
> set the cygwin timestamp only, without affecting the clipboard contents,
> maybe using a new cygwin API function? Like `touch /dev/clipboard` which
> does not work however.

The timestamp is only stored in the clipboard itself.  I don't see any other
way than to store the data twice, once in windows and once in Cygwin format.
What you could do is to wait for Cygwin 3.3.0, then you can include
<sys/clipboard.h> and just store the data additionally in Cygwin format
with timestamp.

However, is the clipboard timestamp really that important?  It sounds
fun, but as soon as *any* non-Cygwin application implemants a copy to
clipboard, the timestamp of /dev/clipboard is reset to 2006.


Corinna

      reply	other threads:[~2021-10-27  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211007052237.7139-1-mark@maxrnd.com>
     [not found] ` <20211008185210.cac713f28dea727a1467cf94@nifty.ne.jp>
     [not found]   ` <29514de9-0d19-0d22-b8e1-3bfbce11589b@cornell.edu>
     [not found]     ` <7dd31f61-43a1-4e4d-2e1a-dc79606263d5@dronecode.org.uk>
     [not found]       ` <037a8027-8969-df1e-ccb5-6a736578cec5@cornell.edu>
     [not found]         ` <6de24f8c-bd21-cd4f-18ff-ece3fef85b89@maxrnd.com>
     [not found]           ` <ee8b46bd-f8f4-85da-be25-233c3cb60c71@cornell.edu>
     [not found]             ` <YXLUkU6Nc3qAXLyp@calimero.vinschen.de>
     [not found]               ` <12fea3e3-92ae-2a33-81ea-808bdcc20f2a@maxrnd.com>
2021-10-27  9:01                 ` Thomas Wolff
2021-10-27  9:52                   ` Corinna Vinschen [this message]

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=YXkhSr5WFf2rNk2b@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-developers@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).