starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Is there a way to setting Line Breaks to '\n' ? #17865

New Issue
Closed
opened 2026-01-31 05:56:42 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 05:56:42 +00:00
Owner
Copy Link

Originally created by @Tancen on GitHub (Jul 5, 2022).

My pseudo console receive commands from the Linux terminal real-time, It cannot process '\n' well on key 'Enter' pressed. So, I scanned each input character and replaced '\n' with '\r\n' on Linux for windows pseudo console works well. But, The solution isn't beautiful on some text pasted, Because characters '\r\n' will be replaced with '\r\r\n'.
Is there a way to setting Line Breaks to '\n' ? Thanks.

Originally created by @Tancen on GitHub (Jul 5, 2022). My pseudo console receive commands from the Linux terminal real-time, It cannot process '\n' well on key 'Enter' pressed. So, I scanned each input character and replaced '\n' with '\r\n' on Linux for windows pseudo console works well. But, The solution isn't beautiful on some text pasted, Because characters '\r\n' will be replaced with '\r\r\n'. Is there a way to setting Line Breaks to '\n' ? Thanks.
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 05:56:43 +00:00
claunia commented 2026-01-31 05:56:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 5, 2022):

I think we're gonna need more info on the specifics of your scenario here. How newlines are handled are usually dependent on the line discipline of the connected client application. This is likely different for a win32 console application vs a linux application running under WSL.

Can you give us some specific repro steps/?

@zadjii-msft commented on GitHub (Jul 5, 2022): I think we're gonna need more info on the specifics of your scenario here. How newlines are handled are usually dependent on the line discipline of the connected client application. This is likely different for a win32 console application vs a linux application running under WSL. Can you give us some specific repro steps/?
claunia commented 2026-01-31 05:56:44 +00:00
Author
Owner
Copy Link

@Tancen commented on GitHub (Jul 6, 2022):

I think we're gonna need more info on the specifics of your scenario here. How newlines are handled are usually dependent on the line discipline of the connected client application. This is likely different for a win32 console application vs a linux application running under WSL.

Can you give us some specific repro steps/?

Sorry, For example, the pseudo console launched 'cmd.exe' at first. key 'Enter' pressed after characters 'dir' typed on linux terminal, data 'dir\n' received on windows and be written in pseudo console, the pseudo console doesn't output result for the command 'dir'. it expects 'dir\r\n', not 'dir\n'.

@Tancen commented on GitHub (Jul 6, 2022): > I think we're gonna need more info on the specifics of your scenario here. How newlines are handled are usually dependent on the line discipline of the connected client application. This is likely different for a win32 console application vs a linux application running under WSL. > > Can you give us some specific repro steps/? Sorry, For example, the pseudo console launched 'cmd.exe' at first. key 'Enter' pressed after characters 'dir' typed on linux terminal, data 'dir\n' received on windows and be written in pseudo console, the pseudo console doesn't output result for the command 'dir'. it expects 'dir\r\n', not 'dir\n'.
claunia commented 2026-01-31 05:56:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 6, 2022):

Well, that makes perfect sense. There are two different streams here - input and output. \n works just fine as input to indicate an enter. On output, however, you'll want both the \r and the \n, because they do different things as output. \r takes the cursor back to the start of the row, while \n takes the cursor down a row. Technically, to go to the start of the next line, you need both an \r and an \n. In general, conpty actually does leverage that difference quite a bit, to make sure the cursor in the conpty stays in sync with the hosting terminal in an efficient manner.

@zadjii-msft commented on GitHub (Jul 6, 2022): Well, that makes perfect sense. There are two different streams here - input and output. `\n` works just fine as input to indicate an <kbd>enter</kbd>. On output, however, you'll want both the `\r` and the `\n`, because they do different things as output. `\r` takes the cursor back to the start of the row, while `\n` takes the cursor down a row. Technically, to go to the _start_ of the _next_ line, you need both an `\r` and an `\n`. In general, conpty actually does leverage that difference quite a bit, to make sure the cursor in the conpty stays in sync with the hosting terminal in an efficient manner.
claunia commented 2026-01-31 05:56:45 +00:00
Author
Owner
Copy Link

@Tancen commented on GitHub (Jul 6, 2022):

Well, that makes perfect sense. There are two different streams here - input and output. \n works just fine as input to indicate an enter. On output, however, you'll want both the \r and the \n, because they do different things as output. rtakes the cursor back to the start of the row, while\ntakes the cursor down a row. Technically, to go to the start of the next line, you need both an\rand an\n. In general, conpty actually does leverage that difference quite a bit, to make sure the cursor in the conpty stays in sync with the hosting terminal in an efficient manner.

Yes. So, please 'cmd.exe' to give settings(or another way) to make a command such as 'dir\n' work like 'dir\r\n'(If Windows terminal will be compatible with UNIX-like terminal).

@Tancen commented on GitHub (Jul 6, 2022): > Well, that makes perfect sense. There are two different streams here - input and output. `\n` works just fine as input to indicate an enter. On output, however, you'll want both the `\r` and the `\n`, because they do different things as output. `r`takes the cursor back to the start of the row, while`\n`takes the cursor down a row. Technically, to go to the _start_ of the _next_ line, you need both an`\r`and an`\n`. In general, conpty actually does leverage that difference quite a bit, to make sure the cursor in the conpty stays in sync with the hosting terminal in an efficient manner. Yes. So, please 'cmd.exe' to give settings(or another way) to make a command such as 'dir\n' work like 'dir\r\n'(If Windows terminal will be compatible with UNIX-like terminal).
claunia commented 2026-01-31 05:56:45 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Jul 6, 2022):

So, please 'cmd.exe' to give settings(or another way)

Use your favorite scripting or more serious programming language in order to convert UNIX and WINDOWS line breaks by the fly.
There is not any settings to change system wide line breaking. Cmd.exe is one of Windows shells, Windows Terminal is an application to launch it.

@237dmitry commented on GitHub (Jul 6, 2022): > So, please 'cmd.exe' to give settings(or another way) Use your favorite scripting or more serious programming language in order to convert UNIX and WINDOWS line breaks by the fly. There is not any settings to change system wide line breaking. Cmd.exe is one of Windows shells, Windows Terminal is an application to launch it.
claunia commented 2026-01-31 05:56:45 +00:00
Author
Owner
Copy Link

@Tancen commented on GitHub (Jul 6, 2022):

So, please 'cmd.exe' to give settings(or another way)

Use your favorite scripting or more serious programming language in order to convert UNIX and WINDOWS line breaks by the fly. There is not any settings to change system wide line breaking. Cmd.exe is one of Windows shells, Windows Terminal is an application to launch it.

As I described in my question, it's so hard to resolve the problem that pasting and typing compatibility (input stream).

@Tancen commented on GitHub (Jul 6, 2022): > > So, please 'cmd.exe' to give settings(or another way) > > Use your favorite scripting or more serious programming language in order to convert UNIX and WINDOWS line breaks by the fly. There is not any settings to change system wide line breaking. Cmd.exe is one of Windows shells, Windows Terminal is an application to launch it. As I described in my question, it's so hard to resolve the problem that pasting and typing compatibility (input stream).
claunia commented 2026-01-31 05:56:45 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Jul 6, 2022):

key 'Enter' pressed after characters 'dir' typed on linux terminal, data 'dir\n' received on windows and be written in pseudo console, the pseudo console doesn't output result for the command 'dir'. it expects 'dir\r\n', not 'dir\n'.

Just tried, connected with ssh from linux-computer to windows one. dir worked as expected.

@237dmitry commented on GitHub (Jul 6, 2022): > key 'Enter' pressed after characters 'dir' typed on linux terminal, data 'dir\n' received on windows and be written in pseudo console, the pseudo console doesn't output result for the command 'dir'. it expects 'dir\r\n', not 'dir\n'. Just tried, connected with ssh from linux-computer to windows one. `dir` worked as expected.
claunia commented 2026-01-31 05:56:46 +00:00
Author
Owner
Copy Link

@Tancen commented on GitHub (Jul 7, 2022):

key 'Enter' pressed after characters 'dir' typed on linux terminal, data 'dir\n' received on windows and be written in pseudo console, the pseudo console doesn't output result for the command 'dir'. it expects 'dir\r\n', not 'dir\n'.

Just tried, connected with ssh from linux-computer to windows one. dir worked as expected.

Thanks, I will consider it.

@Tancen commented on GitHub (Jul 7, 2022): > > key 'Enter' pressed after characters 'dir' typed on linux terminal, data 'dir\n' received on windows and be written in pseudo console, the pseudo console doesn't output result for the command 'dir'. it expects 'dir\r\n', not 'dir\n'. > > Just tried, connected with ssh from linux-computer to windows one. `dir` worked as expected. Thanks, I will consider it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17865
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?