romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-08-25 06:13:31 +03:00
Code Issues Projects Releases Packages Wiki Activity

stop using the word 'just'

Browse source 
Everywhere. In documentation and code comments.

It is almost never a good word and almost always a filler that should be
avoided.

Closes #20793
This commit is contained in:
Daniel Stenberg 2026-03-02 23:41:35 +01:00
parent 4b583b7585
commit b4dba346cd
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
213 changed files with 727 additions and 772 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/libcurl/libcurl-errors.md
View file

@ -29,11 +29,10 @@ Why they occur and possibly what you can do to fix the problem are also included
# CURLcode
Almost all "easy" interface functions return a CURLcode error code. No matter
what, using the curl_easy_setopt(3) option CURLOPT_ERRORBUFFER(3)
is a good idea as it gives you a human readable error string that may offer
more details about the cause of the error than just the error code.
curl_easy_strerror(3) can be called to get an error string from a given
CURLcode number.
what, using the curl_easy_setopt(3) option CURLOPT_ERRORBUFFER(3) is a good
idea as it gives you a human readable error string that may offer more details
about the cause of the error than the error code alone. curl_easy_strerror(3)
can be called to get an error string from a given CURLcode number.
CURLcode is one of the following:
@ -45,8 +44,7 @@ All fine. Proceed as usual.
The URL you passed to libcurl used a protocol that this libcurl does not
support. The support might be a compile-time option that you did not use, it
can be a misspelled protocol string or just a protocol libcurl has no code
for.
can be a misspelled protocol string or a protocol libcurl has no code for.
## CURLE_FAILED_INIT (2)