You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using jiracli version 0.4.12 which uses ipython for the interactive shell, however ipython does not seem to respect my configuration in ~/.ipython/profile_default/ipython_config.py where I am setting vi editing more (which works in ipython.
I can switch the editing mode in the interactive shell by running:
ip= get_ipython()
ip.editing_mode='vi'
however, it would be nice not to have to do this every time.
Is there an existing issue for this?
I have searched the existing issues
Jira Instance type
Jira Cloud (Hosted by Atlassian)
Jira instance version
No response
jira-python version
main
Python Interpreter version
3.12.2
Which operating systems have you used?
Linux
macOS
Windows
Reproduction steps
# 1. Given a Jira client instancejira: JIRA# 2. When I call the function with argument xjira.the_function(x)
# 3.
...
Stack trace
n/a
Expected behaviour
jirashell should respect ipython configuration (or have its own)
Additional Context
ipython==8.26.0
The text was updated successfully, but these errors were encountered:
Bug summary
I'm using jiracli version 0.4.12 which uses ipython for the interactive shell, however ipython does not seem to respect my configuration in
~/.ipython/profile_default/ipython_config.py
where I am settingvi
editing more (which works inipython
.I can switch the editing mode in the interactive shell by running:
however, it would be nice not to have to do this every time.
Is there an existing issue for this?
Jira Instance type
Jira Cloud (Hosted by Atlassian)
Jira instance version
No response
jira-python version
main
Python Interpreter version
3.12.2
Which operating systems have you used?
Reproduction steps
Stack trace
Expected behaviour
jirashell should respect ipython configuration (or have its own)
Additional Context
ipython==8.26.0
The text was updated successfully, but these errors were encountered: