public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: grep < fifo fails
Date: Wed, 03 Oct 2018 16:50:00 -0000	[thread overview]
Message-ID: <fabf7a9e-43a2-ddd7-ccda-4c32a000c21e@gmail.com> (raw)
In-Reply-To: <d56a12c77ecc441ca7dc2e8e1862145c@prosa.dk>

Am 03.10.2018 um 17:37 schrieb Ole Tange:
> This works:
>
> $ mkfifo fifo
> $ echo > fifo & grep .  fifo
> [1] 10232
> [1]+  Done                    echo > fifo
>
> But this fails:
>
> $ echo > fifo & grep . < fifo
> [1] 11756
> grep: (standard input): Invalid argument
> [1]+  Done                    echo > fifo
>
> I see the same behavior on MINGW, but I do not see the same behavior on GNU/Linux.
>
>
> Regards,
>
> Ole Tange

I assume it is a consequence of the same problem on files.
You can not use the same source for input and output.

$ echo "prova" > prova.txt

$ cat prova.txt
prova

$ cat prova.txt > prova.txt

$ cat prova.txt

the file was erased



---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


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

  reply	other threads:[~2018-10-03 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 15:37 Ole Tange
2018-10-03 16:50 ` Marco Atzeri [this message]
2018-10-03 18:46 ` Houder
2018-10-04 16:02   ` Houder
2018-10-05 15:32     ` Houder
2018-10-08  8:24       ` Houder
2018-10-08 15:03         ` Eric Blake
2018-10-10 11:22           ` Corinna Vinschen
2018-10-10  9:53         ` Houder

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=fabf7a9e-43a2-ddd7-ccda-4c32a000c21e@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).