X-Recipient: archive-cygwin@delorie.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:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=BxW9
	e22tnll89fqH1ulibxT/DzfnWgyMCgztlLMa6sS+yxRRra0WDUA4XPP9dAVE9heS
	gjyx0EUd805islWvho31ytLBBR6cIqX1Ou+epJAb1GCrATp5Vs1b3UQotBqXo3d/
	7tY5OeCrOQ45PSUHUv06vTPjycCutaj0BOMUy48=
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:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=KCojmuJkux
	uluL3HMUSCHpW7I7Q=; b=klDUOp+QQOreId6eJnzgpf8XXR9P4wkinW4RqdQAaa
	ioDYDcnKAkcI+VHoIt8iMWtSrqGN3zu+phtDEEDfiPTxf7jkO/R3ZAMYq9GyvjOG
	tqcMi/VhBekVf9KOC30kIl5oLAdMnTbli19X7MGmZppGTVKmIGBOgwKKYtJ3yrMq
	8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-we0-f170.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:date:from:to:subject:message-id:references         :mime-version:content-type:content-disposition:in-reply-to         :user-agent;        bh=hnjSxWaoa3pQTUbO44vWw9NC1QB+nMAvke9wS0YJ+oA=;        b=ReiqAdyTgPTZhJrYgrNwDcq5iAG0ABd3cSnF61oBWUpYfkNa0L6pTro6bLHLCljC1Q         sptc2Kar1PpBJfmsBz4tEhCZwo2tdY/XdVkBUnKgIaChI/gEG4r+HpMQt++HSMPAmdol         m5yMstDgPYXf9SWFO8alscMJ1J9RH73fpc0oI3nu7wmMwJB2AsOmDE5nuIgSIIXgp0bW         2qKnb8mB0ViMDFZ6jW/+m7V/Ny/UKWhK5/w50fUr5Hv2JbMd9yWRuKI3HYX42I0iH3Wc         I0YQflTlv7PJMw3+W49hy+UY7aKCGO5Wxemb+cPlKz3nEE63IeUEkAo0mcaGjYlh3C+N         BjdQ==
X-Gm-Message-State: ALoCoQlsQeUjJExnkqx12O5Rfkz0uAjnBAMlDOqh5FK44Wga54o9JZgZDDZWzA//7dkvTUQLS4pR
X-Received: by 10.194.104.196 with SMTP id gg4mr18832749wjb.31.1423841153342;        Fri, 13 Feb 2015 07:25:53 -0800 (PST)
Date: Fri, 13 Feb 2015 15:25:51 +0000
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Writing to /dev/clipboard from multiple processes in Bash gives inconsistent behaviour
Message-ID: <20150213152551.GF20741@dinwoodie.org>
References: <20150212134550.GC20741@dinwoodie.org> <20150212170342.GB7818@calimero.vinschen.de> <925263616.20150213005102@yandex.ru> <20150213092339.GB17624@calimero.vinschen.de> <1083078655.20150213130932@yandex.ru> <20150213105917.GE20741@dinwoodie.org> <02f801d0479f$e93c9c20$bbb5d460$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <02f801d0479f$e93c9c20$bbb5d460$@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-IsSubscribed: yes

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

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.

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

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

