Helmut K. C. Tessarek
Helmut K. C. Tessarek
@reneeotten I don't have merge access. someone from the macports team has to merge this
Oh, I see. Yes, LGTM and adding a variant makes sense. Thx.
IMO the current behavior (after the PR) is correct. Piping something into a program means that this something becomes the input (this is well defined unix philosophy). ``` echo "bla"...
I think you misunderstood my reasoning or what I was saying. I think we might be talking past each other. The PR was about the fact that `eza --stdin` did...
> I'm definitely misunderstanding you because it seems like you think that without the --stdin flag, eza will comsume but ignore stdin, but it in fact does not ignore it....
> I'm fine with that. I don't think you are, because you missed this crucial part: > or data is piped into the tool And you do not want this...
> The fact that there is stdin for eza to access is more a bash oddity (and GithHub Action's in that test... that one's odd) than eza's fault. It still...
All good. I am just waiting for the devs to chime in. I am more than happy to create another PR so that eza ignores piped-in data. I am not...
Let me make this once more perfectly clear: there is no bug in eza. The issue is that people, who are reporting this issue, are not running eza interactively (this...
@zperk13 in that case open a ticket with bash.