We got this question about adding support for the NETRC environment variable to #curl - because it currently does not support it.
Curious about the prevalence of this environment variable in existing tools I decided to, yeah, Google it...
⇧
Elias Probst
in reply to daniel:// stenberg:// • • •Lord Tom Klopf of CZ
in reply to daniel:// stenberg:// • • •railmeat
in reply to daniel:// stenberg:// • • •D*
in reply to daniel:// stenberg:// • • •woah impressive, so apparently AI knows more than you about curl - that's probably the future we've been sold all this time...
However, I wouldn't trust any development task to these AI though and you've been known to be dependable the last - let me check - oh yeah the last 29 years, so I guess thank you for everything and let's burn these AI to the ground!
Matt Hall
in reply to daniel:// stenberg:// • • •I dunno, man. AI says it's already implemented.
😆
It's a good thing we don't use search to find _truth_ any more.
Wilfried Klaebe
in reply to daniel:// stenberg:// • • •Óscar Morales Vivó
in reply to daniel:// stenberg:// • • •ReginaldExcellent
in reply to daniel:// stenberg:// • • •Jon
in reply to daniel:// stenberg:// • • •Programmer 832-529 🍅
in reply to daniel:// stenberg:// • • •1 (how getenv works) + 1 (how curl uses .netrc) = banana
Two rights make a wrong!
Fred DJ
in reply to daniel:// stenberg:// • • •Bojidar Marinov
in reply to daniel:// stenberg:// • • •IDK, it says "tools _like_ curl", so maybe it's time to admit that, well, curl is not a curl-like tool? xD
...that, or that the blue box is not knowledgeable-like. 🤔
Apollo
in reply to daniel:// stenberg:// • • •