Re: A feature request.

On Tue, Jun 10, 2025 at 03:34:02PM -0700, Collin Funk wrote: > There was a similar request a few weeks ago [1]. I did not like that, a lot of ugly stuff just to try to get backwards compatibility -- IMHO far better to have a --json-output option and accept that it will not work on old machines.

Re: A feature request.

Hi Mike, Mike Hoye writes: > Hello, coreutils people - > > I am wondering if there is any appetite for adding jsonlines as an output > format in the various core utilities. A common structured-output format in > low level tools would make tool chaining and constructive exploration > significantl

A feature request.

Hello, coreutils people - I am wondering if there is any appetite for adding jsonlines as an output format in the various core utilities. A common structured-output format in low level tools would make tool chaining and constructive exploration significantly easier. Thank you, - mhoye

Re: `cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead`

Hello there, Thank you for the investigation! Apologies it turned out "not to be you" 😅 With regards, Ntentos Stavros On Tue, 10 Jun 2025 at 14:03, Pádraig Brady wrote: > > On 10/06/2025 11:35, Pádraig Brady wrote: > > On 10/06/2025 08:56, Σταύρος Ντέντος wrote: > >> Hello there, > >> > >> I wa

Re: `cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead`

On 10/06/2025 11:35, Pádraig Brady wrote: On 10/06/2025 08:56, Σταύρος Ντέντος wrote: Hello there, I was wondering: Should the error message contain `-n/--no-clobber` and/or use the same flag as the one used in the invocation? Rationale: I try to write my dotfiles without shorthands - for futu

Re: `cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead`

On 10/06/2025 08:56, Σταύρος Ντέντος wrote: Hello there, I was wondering: Should the error message contain `-n/--no-clobber` and/or use the same flag as the one used in the invocation? Rationale: I try to write my dotfiles without shorthands - for future readability. So, "after a distro upgrade

`cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead`

Hello there, I was wondering: Should the error message contain `-n/--no-clobber` and/or use the same flag as the one used in the invocation? Rationale: I try to write my dotfiles without shorthands - for future readability. So, "after a distro upgrade (Ubuntu 24.04)", it was so weird to me to rea