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

Programs not accepting input #122

New Issue
Closed
opened 2026-01-30 21:42:58 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 21:42:58 +00:00
Owner
Copy Link

Originally created by @bitcrazed on GitHub (Feb 16, 2018).

From @coreysharris on May 31, 2017 9:20

  • Your Windows build number: 10.0.16199.1000

  • What you're doing and what's happening:
    Starting a program in bash works, but input does not.
    This problem occurs for vim, emacs, sagemath
    but everything works in mc, w3m

  • What's wrong / what should be happening instead:
    After the program starts, it should accept input from the keyboard.

For SageMath, I reinstalled from source to try to fix this (before I realized it was a problem for other programs) and when it starts I get this error before the initial prompt: /home/corey/.local/lib/sage-7.6/local/lib/python2.7/site-packages/psutil/_pslinux.py:364: RuntimeWarning: 'sin' and 'sout' swap memory stats couldn't be determined and were set to 0 ([Errno 2] No such file or directory: '/proc/vmstat')
warnings.warn(msg, RuntimeWarning)

  • Strace of the failing command, if applicable: Example shown with "vim -u NONE" (the flag prevents loading of my .vimrc)
    strace.txt

Copied from original issue: Microsoft/WSL#2177

Originally created by @bitcrazed on GitHub (Feb 16, 2018). _From @coreysharris on May 31, 2017 9:20_ * Your Windows build number: 10.0.16199.1000 * What you're doing and what's happening: Starting a program in bash works, but input does not. This problem occurs for vim, emacs, sagemath but everything works in mc, w3m * What's wrong / what should be happening instead: After the program starts, it should accept input from the keyboard. For SageMath, I reinstalled from source to try to fix this (before I realized it was a problem for other programs) and when it starts I get this error before the initial prompt: /home/corey/.local/lib/sage-7.6/local/lib/python2.7/site-packages/psutil/_pslinux.py:364: RuntimeWarning: 'sin' and 'sout' swap memory stats couldn't be determined and were set to 0 ([Errno 2] No such file or directory: '/proc/vmstat') warnings.warn(msg, RuntimeWarning) * Strace of the failing command, if applicable: Example shown with "vim -u NONE" (the flag prevents loading of my .vimrc) [strace.txt](https://github.com/Microsoft/BashOnWindows/files/1040751/strace.txt) _Copied from original issue: Microsoft/WSL#2177_
claunia added the Product-ConhostIssue-BugArea-InputResolution-Won't-Fix labels 2026-01-30 21:42:58 +00:00
claunia commented 2026-01-30 21:42:59 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on May 31, 2017 20:56

Possibly #2092?

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on May 31, 2017 20:56_ Possibly #2092?
claunia commented 2026-01-30 21:42:59 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @coreysharris on June 1, 2017 8:54

Ok, the workaround given there fixes the problem for vim, but not for emacs or sage.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @coreysharris on June 1, 2017 8:54_ Ok, the workaround given there fixes the problem for vim, but not for emacs or sage.
claunia commented 2026-01-30 21:42:59 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on June 1, 2017 16:47

I'll take a look.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on June 1, 2017 16:47_ I'll take a look.
claunia commented 2026-01-30 21:42:59 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on June 5, 2017 21:10

@coreysharris have you done anything to modify your emacs configuration at all? I just installed a fresh 16199 build and emacs seems to run just fine, so there's probably some configuration that is breaking this.

Does changing your TERM setting (and launching bash in the same window again) change anything?

What about running emacs inside of screen or tmux?

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on June 5, 2017 21:10_ @coreysharris have you done anything to modify your emacs configuration at all? I just installed a fresh 16199 build and emacs seems to run just fine, so there's probably some configuration that is breaking this. Does changing your `TERM` setting (and launching bash in the same window again) change anything? What about running emacs inside of `screen` or `tmux`?
claunia commented 2026-01-30 21:43:00 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on July 13, 2017 20:55

I've been out for a few weeks, but I'd like to make sure this gets resolved or at least understood before the next release.

@coreysharris is this still happening for you in new insider's builds? Does any of the other suggestions make a difference? Does running the Ubuntu instance from the store make a difference?

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on July 13, 2017 20:55_ I've been out for a few weeks, but I'd like to make sure this gets resolved or at least understood before the next release. @coreysharris is this still happening for you in new insider's builds? Does any of the other suggestions make a difference? Does running the Ubuntu instance from the store make a difference?
claunia commented 2026-01-30 21:43:00 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 18, 2019):

This never received author feedback; closing Resolution-Won't Fix

@DHowett-MSFT commented on GitHub (May 18, 2019): This never received author feedback; closing `Resolution-Won't Fix`
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 Area-Input Issue-Bug Product-Conhost Resolution-Won't-Fix
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#122
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?