Crazy behavior: "v" key results in new line 😕
See original GitHub issueI’m using pgcli 1.4.0 on Windows 10
Everything works fine, I can connect to my Postgres DB, but when I type the “v” letter I get a new line/carriage return, the same as if I press “Enter” !!?!
Please note that:
- same happens if I just past the “v” letter inside pgcli
- capital “V” works fine!!
Already tried with no success:
- run pgcli under cmd, Powershell, git bash, Windows 10 bash: “v” key works as expected inside any of these shells, but inside pgcli it turns into “Enter”.
- reboot workstation
- full reinstall of pgcli with
pip install --upgrade --force-reinstall -I --ignore-installed pgcli
Any ideas?!?? This is driving me crazy
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Defining OKRs for Your Product Management Team
Whether you're new to objectives and key results (OKRs) or just brushing up, this blog post aims to help you feel more confident...
Read more >60+ OKR Examples - How To Write Effective OKRs 2022
Looking for good OKR examples? This article covers over 60 practical OKRs, why they work, and tips for the writing process.
Read more >OKR examples and how to write them - What Matters
For how to write OKRs, the actual formula is simple: Objectives are goals and intents, while Key Results are time-bound and measurable milestones...
Read more >Use OKRs to Set Goals for Teams, Not Individuals
These quantifiable outcomes are called “key results,” and are used to measure how successful teams are with respect to their objectives. This ...
Read more >what does fake coke taste like - Caseificio de Nicola
The coca Rubbing the white powder along the gum line is also the way people ... Smoking crack cocaine smells results in a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This bug is somewhere in prompt_toolkit 1.0.10. @cristoforo you can do “pip install prompt_toolkit==1.0.9” to avoid “v” bug.
Thanks @jonathanslenders. That fixed the issue for me.