prompt-toolkit / prompt-toolkit/python-prompt-toolkit
[bug] (apparently), keybinding for <any> filter is called endlessly without any key typed
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10.6k
- Forks
- 815
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
am not sure if this is a bug or feature, but the keybinding filtering function is called enndlesly.
I wanted to use it to have an overview of the keybindings and implement a plugin like the nvim "which-key" plugin.
@Condition
def unasigned_filter():
print("filter called")
return True #does not matter if I return True or False
@bindings.add("<any>", filter=unasigned_filter)
def _(event):
return
thanks
Z
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 tracing the @Condition filter used with bindings.add("", filter=unasigned_filter) and reproduce the repeated calls without keyboard input. Confirm the filter is invoked only when appropriate keybinding filtering occurs, while preserving the reported keybinding behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100