We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When executing certain commands, at least jira init, jira issue create and jira epic create, raw escape sequences are visible.
jira init
jira issue create
jira epic create
E.g.
$ jira init ? Installation type: [Use arrows to move, type to filter, ? for more help] > Cloud Local
Arrow up/down is printed as ^[[A and ^[[B, then [[24;80R is printed after pressing return.
^[[A
^[[B
[[24;80R
It seems like something is putting the terminal into raw mode.
This happens with both @latest and
$ jira version (Version="v1.5.1", GitCommit="", CommitDate="", GoVersion="go1.22.1", Compiler="gc", Platform="openbsd/amd64")
on OpenBSD (-current), both in an xterm and in tmux.
Otherwise, the commands work as expected.
The text was updated successfully, but these errors were encountered:
The issue here is that jira-cli uses the unmaintained survey library (https://github.com/AlecAivazis/survey/). It seems like bubbletea is the recommended replacement.
jira-cli
There is an analogous bug report for gitlab-cli, to be found here: https://gitlab.com/gitlab-org/cli/-/issues/7351
Sorry, something went wrong.
I'm having the same issue, also on OpenBSD (-current).
No branches or pull requests
When executing certain commands, at least
jira init
,jira issue create
andjira epic create
, raw escape sequences are visible.E.g.
Arrow up/down is printed as
^[[A
and^[[B
, then[[24;80R
is printed after pressing return.It seems like something is putting the terminal into raw mode.
This happens with both @latest and
on OpenBSD (-current), both in an xterm and in tmux.
Otherwise, the commands work as expected.
The text was updated successfully, but these errors were encountered: