prompt-toolkit / prompt-toolkit/python-prompt-toolkit
How to make prompt-toolkit work on dumb terminals
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10.6k
- Forks
- 815
- PR merge metrics
- No merged PRs in 30d
Description
On dumb terminals (TERM=dumb or TERM=unkown) prompt-toolkit behaves strangely: Some message are not displayed, it expects arrow key support, etc.
I was wondering whether it is possible to swap the Vt100Input class for a class which offers genuinely less capabilities (i.e. no cursor movement, no arrow keys, etc).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with TERM=dumb and TERM=unknown, then inspect how prompt-toolkit selects and uses Vt100Input. Determine how messages and input should behave without cursor movement or arrow-key support, and verify that interactive applications work correctly on dumb terminals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100