-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
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
cli: logs
output formatting
#371
Labels
Comments
diegodelemos
pushed a commit
to diegodelemos/reana-client
that referenced
this issue
Feb 14, 2020
* Modeled after brew and archlinux log styles (closes reanahub#371).
diegodelemos
pushed a commit
to diegodelemos/reana-client
that referenced
this issue
Feb 14, 2020
* Modeled after brew and archlinux log styles (closes reanahub#371).
diegodelemos
pushed a commit
to diegodelemos/reana-client
that referenced
this issue
Feb 14, 2020
* Modeled after brew and archlinux log styles (closes reanahub#371).
diegodelemos
pushed a commit
to diegodelemos/reana-client
that referenced
this issue
Feb 14, 2020
* Modeled after brew and archlinux log styles (closes reanahub#371).
diegodelemos
pushed a commit
to diegodelemos/reana-client
that referenced
this issue
Feb 17, 2020
* Modeled after brew and archlinux log styles (closes reanahub#371).
diegodelemos
pushed a commit
to diegodelemos/reana-client
that referenced
this issue
Feb 17, 2020
* Modeled after brew and archlinux log styles (closes reanahub#371).
diegodelemos
pushed a commit
to diegodelemos/reana-client
that referenced
this issue
Feb 17, 2020
* Modeled after brew and archlinux log styles (closes reanahub#371).
diegodelemos
pushed a commit
to diegodelemos/reana-client
that referenced
this issue
Feb 17, 2020
* Modeled after brew and archlinux log styles (closes reanahub#371).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behaviour
The
logs
command return info as follows:This is rich and follows #348 but it is not easiest for quick grepping of information, and "job id" is lowercase while
JOB NAME
in uppercase, etc.Expected behaviour
It'll be good to harmonise this and invent a structure allowing for easy location of various sections of the file.
We could even think about creating org-mode or markdown-mode styled file for easy folding/unfolding of various sections, but the markup should be sufficiently different from what people might use in their logs so that it would not mix up.
Possible example:
using leading `>>> ' prefix to quickly localise sections.
Could use ":::" and whatnot instead.
This structure would permit quick grepping and also folding/unfolding of various individual steps
in text editors.
(E.g. BSM log can be huge.)
P.S. Note also the task about outputting only wanted steps #369
The text was updated successfully, but these errors were encountered: