Re: [galaxy-dev] backslash in string for galaxy tool

Indeed this combination works perfectly now: Thanks! From: Eric Rasche Organization: TAMU Date: Thursday 10 March 2016 at 17:16 To: Jasper Koehorst , Subject: Re: [galaxy-dev] backslash in string for galaxy tool

Re: [galaxy-dev] Error attempting to display contents of library (New data library)

Hi Juan, I'm working on a few errors I've uncovered trying to track down your issue here, but my hunch is you're hitting a different one. The branch is here if you want to try it: https://github.com/dannon/galaxy/commits/library_errors Do you have any non-ascii characters in a particular field

Re: [galaxy-dev] Galaxy tools for docking protein-compounds.

Am 10.03.2016 um 21:30 schrieb Léo Biscassi: > Hi folks, > I have make somes alterations on my tools to adjust of according with > best pratices of development of tools presented in [1] [2]. The > repository of tools was changed for [3]. > I was testing the tool of docking [4] with the command

Re: [galaxy-dev] Galaxy tools for docking protein-compounds.

Hi, yes it more or less the same. 1) You fork the galaxytools repository in github. 2) You clone your fork of galaxtools 3) now inside of your clone you do: - git branch autodock - git checkout autodock 4) add your tools and modfiy any file you want with - git add ./foo/bar - git commit -m

Re: [galaxy-dev] backslash in string for galaxy tool

Hi Jasper, You'll find that sanitizers are what you want. https://wiki.galaxyproject.org/Admin/Tools/ToolConfigSyntax?highlight=%28sanitizer%29#A.3Csanitizer.3E_tag_set Here's an example of a sanitizer permitting the pound character that I use: Ciao, Eric On

[galaxy-dev] backslash in string for galaxy tool

I am creating a tool which allows you to query RDF files. However when performing a \n in the query it is replaced by Xn. Other special characters such as > are replaced by an __gt__ . How can I either allow galaxy to accept \n entries or that the backslash is replaced by something like __bs__

Re: [galaxy-dev] Missing dependency issue

Hello Scott I don't have any insight into your specific problem with the readline package, however it might be worth looking for the INSTALLATION.log file from the tool install process. Assuming that this is the iuc version of package_readline_6_2 then you can try looking for it under