X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=XOdTec9fjzrSTT9OROqvG1YAL3VI9Rg9GQuTcJyUfv+
	P5hVkcaSUSJKxo2aOploSn9H8jD9/sEw1cRoXet9DjHudvvv9btWs0b1V26oSGXH
	+whcEPIjjiymwx41pW/pZshAJ0n2z9tFReMWU4GcLvq4ePdFHjmE+T3PLdRS9cn0
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=+Oyug5nHSm4Vwpz+IPXkwhSdTrA=; b=wUzG4ry4vSg/IyWaU
	7Ed8b1LhEWJySXIDDLxD+HVGrkiin7B7Il9RRwiwqaRZRLgmWlhn2QRz7F9At4d/
	eoYczHd86Wr0CeTJzxwFpOmKX9hCEJogi1kdYXl5tTcHVmItdgKNyp6KJbyfBaBK
	Anw3KxQaj6lUVDuP9yCstDew0A=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_FROM_URIBL_PCCC,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-yk0-f171.google.com
X-Received: by 10.170.59.131 with SMTP id b125mr10491264ykb.38.1423842235517;        Fri, 13 Feb 2015 07:43:55 -0800 (PST)
From: "cyg Simple" <cygsimple AT gmail DOT com>
To: <cygwin AT cygwin DOT com>
References: <20150212134550 DOT GC20741 AT dinwoodie DOT org> <20150212170342 DOT GB7818 AT calimero DOT vinschen DOT de> <925263616 DOT 20150213005102 AT yandex DOT ru> <20150213092339 DOT GB17624 AT calimero DOT vinschen DOT de> <1083078655 DOT 20150213130932 AT yandex DOT ru> <20150213105917 DOT GE20741 AT dinwoodie DOT org> <02f801d0479f$e93c9c20$bbb5d460$@gmail.com> <20150213152551 DOT GF20741 AT dinwoodie DOT org>
In-Reply-To: <20150213152551.GF20741@dinwoodie.org>
Subject: RE: Writing to /dev/clipboard from multiple processes in Bash gives inconsistent behaviour
Date: Fri, 13 Feb 2015 10:43:57 -0500
Message-ID: <043801d047a3$e253abc0$a6fb0340$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

> From: Adam Dinwoodie
> On Fri, Feb 13, 2015 at 10:15:30AM -0500, cyg Simple wrote:
> > > From: Adam Dinwoodie
> > >
> > > In which case, I wonder if it's worth adding something to the
> > > FAQ/BLODA
> > about
> > > this?  I guess not, at least until someone independently encounters
> > > this behaviour so it warrants the "F" as well as the "AQ".
> > >
> >
> > I find it strange that someone would be using /dev/clipboard for a
> > temporary buffer of data for a batch process anyway.  Too many
> > opportunities for that data to be corrupted by other actions of the
> > user.  So in other words, just don't do that; it isn't portable and it
> > is prone to error.  The proper use would be for a user to store
> > content in /dev/clipboard that the user would then use immediately to
> > paste elsewhere.  It should never be used for programmatic operation
> > where the operation is dependent on the result later; it wasn't designed
for
> that.
> 
> I'm not sure what gave you the impression anyone was trying to use the
> clipboard as a buffer for a batch process.  I can't see anyone using batch
at all,
> for that matter.  (Or do you mean "shell" instead of "batch"?  The two are
> different things.)
> 

A shell command line can batch commands; a batched process doesn't require a
file.

> My original use case (as mentioned in my original email) was a `find`
command
> that `-exec`'d multiple times to produce output.  That went to the
clipboard, for
> me to paste into a Windows application.
> 

I would put the output to a /tmp/deleted.lst file and when I'm ready to
paste it into the mail I would cat /tmp/deleted.lst > /dev/clipboard.

> The shell code I posted was a simple test case to show the problem, not
actually
> what I'm trying to achieve.  Posting simplified example code that
demonstrates
> a problem is a common way to get help because it means others only need to
> understand the simple example, not the full problem:
> https://cygwin.com/acronyms/#STC

By the design and purpose of the Windows Clipboard your use of
/dev/clipboard is flawed.  You need to change your methods in order to fix
the issue.

--
cyg Simple


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