Re: including a path in a batch run



On 2008-03-28, hume.spamfilter@xxxxxxx <hume.spamfilter@xxxxxxx> wrote:
Use:

blastloc = "~/bin/blast-2.2.18/bin/";

Well, the spaces should be removed--otherwise the shell attempts
to find a command named blastloc. Instead I suggest this:

blastloc=~/bin/blast-2.2.18/bin/

(The quotes and the semicolon at the end of the line are unnecessary. But
please take care that this gets executed by a /bin/ksh or /bin/bash as
/bin/sh does not support the ~ shortcut for $HOME.)

I'd also recommend picking up a book on Unix shell scripting.

»man sh« is quite readable.

Andreas.
.



Relevant Pages

  • Re: Background subprocess help?
    ... This description does not correspond to the command above. ... command is confusing because it uses quotes in a strange way. ... meant at the linguistic level and the inner quotes are shell quotes. ... d> processes and/or callbacks and 50+ lines of python code. ...
    (comp.lang.python)
  • Re: Rsync --exclude option
    ... I don't think you are doing that, otherwise your use of the rsync ... so that they are not interpreted by the shell at all. ... to protect them from expansion. ... If the expansion tries to produce quotes, ...
    (comp.unix.shell)
  • Re: Bash commands: maybe they want to drive us crazy?
    ... Bill Unruh wrote: ... single quotes would cause the find command to expand the * ... Which means that a shell command and the shell itself are two very different ...
    (comp.os.linux.misc)
  • Re: Bash: Asterisk reading problem
    ... That is the way shell expansion works. ... No it will not if you use double quotes. ... expand everything with the double quotes. ...
    (uk.comp.os.linux)
  • Re: Bash commands: maybe they want to drive us crazy?
    ... > single quotes would cause the find command to expand the * ... > The shell seems to expect a command inside back quotes (or back ticks, ... the single quotes turns the shell into parrot. ...
    (comp.os.linux.misc)