kas lock without colour?

[Jörg Sommer]

Hello,

is it possible to get the output of `./kas-container lock --update --sort
.kas/upstream.yaml` without colours? I want to redirect it into a file, but
this contains the escape sequences for colours. Is there a variable like
NO_COLOR I can set?


Thanks. Have a nice day. Jörg

--
Navimatix GmbH T: 03641 - 327 99 0
Tatzendpromenade 2 F: 03641 - 526 306
07745 Jena www.navimatix.de

Geschäftsführer: Steffen Späthe, Jan Rommeley
Registergericht: Amtsgericht Jena, HRB 501480

[Jan Kiszka]

On 10.07.26 07:55, 'Jörg Sommer' via kas-devel wrote:
> Hello,
>
> is it possible to get the output of `./kas-container lock --update --sort
> .kas/upstream.yaml` without colours? I want to redirect it into a file, but
> this contains the escape sequences for colours. Is there a variable like
> NO_COLOR I can set?
>

You are referring to the diff's color, right? That can be controlled for
the diff plugin directly, but I guess we lack wiring to have --no-color
for lock as well.

But in the light of https://groups.google.com/g/kas-devel/c/OK_qvVyjYsI,
maybe we should introduce --no-color at the top-level, allowing to have
monochrome warnings and errors as well?

Jan

--
Siemens AG, Foundational Technologies
Linux Expert Center

[Jörg Sommer]

Jan Kiszka schrieb am Fr 10. Jul, 16:00 (+0200):

> On 10.07.26 07:55, 'Jörg Sommer' via kas-devel wrote:
> > Hello,
> >
> > is it possible to get the output of `./kas-container lock --update --sort
> > .kas/upstream.yaml` without colours? I want to redirect it into a file, but
> > this contains the escape sequences for colours. Is there a variable like
> > NO_COLOR I can set?
> >
>
> You are referring to the diff's color, right?

Yes, the diff output like

```
@@ openembedded-core commits diff @@
cddc75d glib-2.0: add back Signed-off-by in CVE-2026-58016 patch
b470a74 python3: add back Co-authored-by in CVE-2026-11972 patch
```

> That can be controlled for the diff plugin directly, but I guess we lack
> wiring to have --no-color for lock as well.

Maybe it's possible to support NO_COLOR?
https://joaomagfreitas.link/reads/nocolor-disabling-ansi-color-output-in-various-unix-commands/
because https://no-color.org/ does not work, currently.

> But in the light of https://groups.google.com/g/kas-devel/c/OK_qvVyjYsI,
> maybe we should introduce --no-color at the top-level, allowing to have
> monochrome warnings and errors as well?

This sounds helpful. COLORS make it cumbersome to parse the output.