Hi All,
I think it makes a lot of sense to allow disabling the addition of stderr
and/or stdout to dataset.info on a per tool/output dataset basis. I’ve added a
Trello card for this here: https://trello.com/c/hC5HABnr. Not sure when anyone
might have a chance to look into it, but pull requests
if possible please?
Thanks
Neil
Message: 3
Date: Fri, 30 May 2014 15:04:47 +0200
From: Wolfgang Maier wolfgang.ma...@biologie.uni-freiburg.de
To: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] stdout in history
Message-ID: lm9vle$70e$2...@ger.gmane.org
Content-Type: text/plain; charset=UTF-8; format
Hi Neil,
I had some problems with this before too, so I created an tool config option a
long time ago in my own galaxy fork. Never really bothered with submitting it,
but it lives in these commits:
https://bitbucket.org/glormph/adapt/commits/4ba256a9b8782642429ecb5472a456584bed86d5
Hi,
It seems that the first 4/5 lines that are printed in the source code
tools appear in the history (when expended) and in stdout link. Is there anyway
to stop print statements appearing in the history panel?
Thanks
Neil
___
Please
you could just redirect stdout to /dev/null in the tool's xml command
line ?
Is that an option for you ?
Cheers,
Wolfgang
On 30.05.2014 14:35, neil.burd...@csiro.au wrote:
Hi,
It seems that the first 4/5 lines that are printed in the source
code tools appear in the history (when
Yes that would work. Can you supply an example if possible please?
Thanks
Neil
Message: 3
Date: Fri, 30 May 2014 15:04:47 +0200
From: Wolfgang Maier wolfgang.ma...@biologie.uni-freiburg.de
To: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] stdout in history
Message-ID: lm9vle$70e$2
