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
Thank you so much for this application! I use it every day and am very happy with it. I'm having an issue where I'm not able to quickly use the output of the help because it's being logged to standard error instead of standard out.
Request
Log jira help to standard out.
Reasons why
It's hard to remember to redirect to standard out
It's hard to type 2>&1 especially in the context of "quickly wanting to find help"
Printing help to standard out follows some widely accepted coding standards
Context
Using jira to quickly find something on the help menu or prevent the help output from scrolling past the screen.
Solution
The solution to both those problems is to use grep or less.
For example, if I want to find the first custom command that has the sse prefix:
jira help | grep sse | awk NR==1
sse-create: Create issue AND add to the current sprint
This isn't possible right now because go-jira is sending the help to standard error.
Current workaround
Redirecting standard error to standard out
jira help 2>&1 | grep sse | awk NR==1
sse-create: Create issue AND add to the current sprint
I agree, I briefly looked into it a while ago. I think there were complications in the underlying getopts library we use, but I will try to double check to see if there is a simple fix that I overlooked last time.
Thank you so much for this application! I use it every day and am very happy with it. I'm having an issue where I'm not able to quickly use the output of the help because it's being logged to standard error instead of standard out.
Request
Log jira help to standard out.
Reasons why
2>&1
especially in the context of "quickly wanting to find help"Context
Using jira to quickly find something on the help menu or prevent the help output from scrolling past the screen.
Solution
The solution to both those problems is to use
grep
orless
.For example, if I want to find the first custom command that has the
sse
prefix:This isn't possible right now because go-jira is sending the help to standard error.
Current workaround
Redirecting standard error to standard out
GNU Coding Standards link summary
The text was updated successfully, but these errors were encountered: