Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixed syntax errors on line 85 and 103 - RE closed PR 374 #376

Merged
merged 1 commit into from
Dec 26, 2023
Merged

fixed syntax errors on line 85 and 103 - RE closed PR 374 #376

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions cmdline/configfile.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ The user agent string example we have used above has no white spaces, so the quo

user-agent = Everything-is-an-agent

See ["When to use quotes"](#when-to-use-quotes) for more info on when quotes should be used.
See ["When to use quotes"](#when-to-use-quotes) for more info on when quotes should be used.

### URLs

Expand All @@ -99,8 +99,7 @@ When entering URLs at the command line, everything that is not an option is assu
You'll need to use double quotes when:

* the parameter contains white space, or starts with the characters `:` or `=`.
* you need to use escape sequences
* (available options: `\\`, `\"`, `\t`, `\n`, `\r` and `\v`. A backslash preceding any other letter is ignored).
* you need to use escape sequences (available options: `\\`, `\"`, `\t`, `\n`, `\r` and `\v`. A backslash preceding any other letter is ignored).

If a parameter containing white space is not enclosed in double quotes, curl will treat the next space or newline as the end of the argument.

Expand Down
Loading