Skip to content
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

how to make "debug info/log" text easier to notice? #149

Closed
jairideout opened this issue Jul 24, 2017 · 0 comments
Closed

how to make "debug info/log" text easier to notice? #149

jairideout opened this issue Jul 24, 2017 · 0 comments
Labels

Comments

@jairideout
Copy link
Member

jairideout commented Jul 24, 2017

Current Behavior
It's easy to miss the final line of text output by a command that describes where to find debug info (e.g. --verbose output or the debug logfile).

Current output:

$ qiime dada2 denoise-single --i-demultiplexed-seqs demux.qza --p-trim-left 0 --p-trunc-len -1 --o-representative-sequences rep-seqs-dada2.qza --o-table table-dada2.qza --p-n-threads 0

Plugin error from dada2:

  Argument to 'trunc_len' was -1, should be non-negative.

Debug info has been saved to /tmp/qiime2-q2cli-err-t7y794ah.log.
$

Proposed Behavior
@maxvonhippel suggested adding a trailing newline to the output to make the line easier to notice:

$ qiime dada2 denoise-single --i-demultiplexed-seqs demux.qza --p-trim-left 0 --p-trunc-len -1 --o-representative-sequences rep-seqs-dada2.qza --o-table table-dada2.qza --p-n-threads 0

Plugin error from dada2:

  Argument to 'trunc_len' was -1, should be non-negative.

Debug info has been saved to /tmp/qiime2-q2cli-err-t7y794ah.log.

$

Questions
Are there other ways we can make this line easier to notice? For example, would bold and/or colored text help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants