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.

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

deck will not respond to <ctrl>+<c> when reading from stdin #1077

Closed
Tieske opened this issue Nov 2, 2023 · 2 comments · Fixed by #1107
Closed

deck will not respond to <ctrl>+<c> when reading from stdin #1077

Tieske opened this issue Nov 2, 2023 · 2 comments · Fixed by #1107

Comments

@Tieske
Copy link
Member

Tieske commented Nov 2, 2023

Version: 1.28 consistently, but also inconsistently seen in 0.27.

Workaround:

  • enter some invalid data
  • press <ctrl>+<d> (twice if not on a new line)

This will result in an error about the invalid data, but the command will exit.

@Tieske
Copy link
Member Author

Tieske commented Nov 10, 2023

Findings so far:

  • This issue started in decK with the inclusion of the lint command in feat(linting): Add support for linting decK files #981
  • It looks like it only happens on Mac with Intel.
  • Since the lint command is based on vacuum, I checked that as well. Releases before 0.4.0 of vacuum suffer from the same problem (note that vacuum doesn't read from stdin, but if you modify it to do so, the same problem was present)
  • In vacuum it was resolved somewhere around this commit daveshanley/vacuum@6d37179

@Tieske
Copy link
Member Author

Tieske commented Nov 10, 2023

So here is the underlying issue it seems: pterm/pterm#562

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant