mirror of
https://github.com/UpsilonNumworks/Upsilon.git
synced 2026-05-09 08:25:44 +02:00
[GH-ISSUE #198] [apps/python] Key selector is showed in autocompletion #73
Labels
No labels
bug
duplicate
easy
enhancement
enhancement
fixed
fixed
good first issue
hard
invalid
pull-request
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Upsilon#73
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Yaya-Cout on GitHub (Apr 3, 2022).
Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/198
Originally assigned to: @Yaya-Cout on GitHub.
Describe the bug
When you type “K” with the
ionmodule imported, the autocompletion show “Key selector” as suggestionTo Reproduce
Steps to reproduce the behaviour:
Expected behaviour
Key selector shouldn't appear in the autocompletion
Screenshots

Device:
a770ee9@ANTARCTUS commented on GitHub (Apr 3, 2022):
I don't think we should fix this bug, I use Upsilon very regularly, yet I persist in writing "KEY_" and waiting for autocompletion. With this "bug" it reminds me from the first letter how to write the keys, and in the end it saves me time.
Je ne pense pas que l'on devrait régler ce bug, j'utilise très régulièrement Upsilon, pourtant je persiste à écrire "KEY_" et à attendre l'autocomplétion. Avec ce "bug" cela me rappelle dès la première lettre comment écrire les touches, et au final, il me fait gagner du temps.
@Yaya-Cout commented on GitHub (Apr 4, 2022):
I think I will fix this bug, but I will add a submenu that will contain all the old
KEY_names to keep autocompletion.Je pense que je vais corriger ce bug, mais que je vais ajouter un sous menu qui va contenir les anciens
KEY_pour pouvoir les avoir dans l'autocomplétion.@ANTARCTUS commented on GitHub (Apr 4, 2022):
Why not.