Since: 20211204-082213-a66c61ee9

Controls whether pasted text will have newlines normalized.

If bracketed paste mode is enabled by the application, the effective value of this configuration option is "None".

The following values are accepted:

truesame as "CarriageReturnAndLineFeed"Since: 20211204-082213-a66c61ee9
falsesame as "None"Since: 20211204-082213-a66c61ee9
"None"The text is passed through unchangedSince: 20220319-142410-0fcdea07
"LineFeed"Newlines of any style are rewritten as LFSince: 20220319-142410-0fcdea07
"CarriageReturn"Newlines of any style are rewritten as CRSince: 20220319-142410-0fcdea07
"CarriageReturnAndLineFeed"Newlines of any style are rewritten as CRLFSince: 20220319-142410-0fcdea07

Note that the string forms of these values are accepted in 20220319-142410-0fcdea07, however, true in all prior versions behaves the same way as "CarriageReturnAndLineFeed" behaves in the nightly build.

The default value has changed in different versions of wezterm:

20211204-082213-a66c61ee9NOT Windows"None"
20220319-142410-0fcdea07NOT Windows"CarriageReturn"

On Windows we're in a bit of a frustrating situation: pasting into Windows console programs requires CRLF otherwise there is no newline at all, but when in WSL, pasting with CRLF gives excess blank lines.

In practice, the default setting means that unix shells and vim will get the unix newlines in their pastes (which is the UX most users will want) and cmd.exe will get CRLF.