zsh-workers
 help / color / mirror / code / Atom feed
From: "Wang, Yichao" <w.yichao@wustl.edu>
To: "Andreas Kähäri" <andreas.kahari@abc.se>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: A bug on cat command for zsh
Date: Mon, 4 Dec 2023 08:30:38 +0000	[thread overview]
Message-ID: <F23D74DF-FD48-4F32-85E9-9DCD98C9542E@wustl.edu> (raw)
In-Reply-To: <ZW2HVRU3x-icS0SA@harpo.local>

Hi Andreas,

Thanks for pointing that out. 

Yep, I see such different behavior (just by chance when playing around with command line) from MacOS(which is BSD system) and Linux (which follows GNU). I think you’re right they have different implementations of `cat`.

Have a nice day!


> On Dec 4, 2023, at 12:01 AM, Andreas Kähäri <andreas.kahari@abc.se> wrote:
> 
> On Mon, Dec 04, 2023 at 07:01:42AM +0000, Wang, Yichao wrote:
>> Hi there,
>> 
>> I am using zsh 5.9 (x86_64-apple-darwin23.0) on MacOS.
>> 
>> The following command in zsh will cause severe damage by running forever into a dead loop.
>> - when you accidentally mess up the redirection flows
>> 
>> ```bash
>> touch 1.txt
>> echo "anything" > 1.txt
>> cat < 1.txt >> 1.txt
>> ```
>> 
>> However, on Linux bash, this behavior is prohibited and hinted.
>> 
>> ```bash
>> cat < 1.txt >> 1.txt
>> cat: -: input file is output file
>> ```
>> 
>> Best,
>> Unknown name
> 
> Allowing the programmer to shoot themselves in the foot does not
> seem like a bug to me.  Note that bash release 5.2.15 does not
> seem to babysit the user in the way that you describe by default.
> Rather, it's the coreutils implementation of cat that does this.
> 
> You may have two implementaions of cat on your system (it's possibly
> a BSD system, or at least non-GNU system, with coreutils installed
> alongside the native utilities).  Check with "type cat" in both shells
> to see what cat is being picked up.
> 
> 
> -- 
> Andreas (Kusalananda) Kähäri
> Uppsala, Sweden
> 
> .


      reply	other threads:[~2023-12-04  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04  7:01 Wang, Yichao
2023-12-04  8:01 ` Andreas Kähäri
2023-12-04  8:30   ` Wang, Yichao [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=F23D74DF-FD48-4F32-85E9-9DCD98C9542E@wustl.edu \
    --to=w.yichao@wustl.edu \
    --cc=andreas.kahari@abc.se \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).