Labels: area/cli kind/feature lifecycle/stale priority/awaiting-more-evidence triage/needs-information
When adding a bridge interactively (using git bug bridge configure), using keyboard arrows add odd characters (^[[D for left arrow) instead of moving in the string.
For exemple using left arrow in base url:
Gitlab base url:
[0]: https://gitlab.com
[1]: enter your own base url
Select option: 1
Base url: https://git.unsi^[[D
The terminal used is Yakuake (based on KDE Konsole).
Doing that seems to require some complex shenanigan like switching the terminal into raw mode (see https://stackoverflow.com/questions/30689640/cursor-key-terminal-input-in-go). It might even need OS specific code and tricky code to support unicode properly.
Support arrow key movement when adding bridges interatively to CLI text input doesn't have a proper cursor
This bot triages untriaged issues and PRs according to the following rules:
lifecycle/stale label is appliedlifecycle/stale was applied, the issue is closedTo remove the stale status, you can:
lifecycle/stale label
sudoforge removed label enhancement
sudoforge removed label lifecycle/stale
sudoforge added label kind/bug
sudoforge added label priority/awaiting-more-evidence
sudoforge added label triage/needs-information
sudoforge removed label kind/bug
sudoforge added label kind/feature
sudoforge changed the title from CLI text input doesn't have a proper cursor to Support arrow key movement when adding bridges interatively
This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:
lifecycle/stale is appliedlifecycle/stale was applied,
lifecycle/rotten is appliedThis bot will not automatically close stale issues.
To remove the stale status, you can:
To avoid automatic lifecycle management of this issue, add
lifecycle/frozen.