Move stderr of stty to pipe #13
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If stderr is left as its default value, any error messages arising from stty are output to the stderr of the program calling `size`, causing strange messages if stty fails.
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this pull request
Jan 24, 2023
0.3.3 * Fixed ioctl foreign import. (biegunka/terminal-size#16) * #alignment is a hsc2hs built-in since some unspecified GHC 7.x. (biegunka/terminal-size#12) * Captured possible stty stderr output with a pipe. (biegunka/terminal-size#13)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In certain scenarios,
sttycan error out; as thestd_errconfiguration value of the relevant process is unset, any error messages fromsttyare output to the console. This usually does not occur, but if a program usingterminal-sizeis run in e.g. an emacs shell buffer, these errors are output, assttycan’t run in this environment. This is not normally a problem, but I would argue it comes under the heading of ‘unexpected behaviour’ and so should probably be fixed. This problem also causes bug commercialhaskell/stack#4901 instack, which stops many people from using the Intero development environment.