[Bioperl-l] Why is '+' a delimiter in $OBDA_SEARCH_PATH?

[Hilmar Lapp]

I'm for semicolon. Isn't that more url-ish even (wasn't semicolon going
to replace the ampersand)? -hilmar

> -----Original Message-----
> From: Brian Osborne [mailto:brian_osborne at cognia.com] 
> Sent: Thursday, May 22, 2003 10:50 AM
> To: lstein at cshl.org; Andreas Kahari
> Cc: bioperl-l at bioperl.org
> Subject: RE: [Bioperl-l] Why is '+' a delimiter in $OBDA_SEARCH_PATH?
> 
> 
> Lincoln,
> 
> I will wait a few days and change it to semi-colon if no one 
> objects. My apologies to those who will have to change their 
> OBDA_SEARCH_PATHs.
> 
> Brian O.
> 
> -----Original Message-----
> From: bioperl-l-bounces at portal.open-bio.org
> [mailto:bioperl-l-bounces at portal.open-bio.org]On Behalf Of 
> Lincoln Stein
> Sent: Thursday, May 22, 2003 12:49 PM
> To: Brian Osborne; Andreas Kahari
> Cc: bioperl-l at bioperl.org
> Subject: Re: [Bioperl-l] Why is '+' a delimiter in $OBDA_SEARCH_PATH?
> 
> What was wrong with using ";" then?  It's unlikely to be 
> found in Unix path names because of its meaning to the shell.
> 
> Lincoln
> 
> On Thursday 22 May 2003 10:13 am, Brian Osborne wrote:
> > Andreas,
> >
> > >The standard search path delimiter is the ':' (see you 
> $PATH variable 
> > >for example).
> >
> > Of course you're right. It's the Windows PATH that's 
> delimited by ';'.
> >
> > Brian O.
> >
> >
> > -----Original Message-----
> > From: Andreas Kahari [mailto:ak at ebi.ac.uk]
> > Sent: Thursday, May 22, 2003 10:03 AM
> > To: Brian Osborne
> > Cc: bioperl-l at bioperl.org
> > Subject: Re: [Bioperl-l] Why is '+' a delimiter in 
> $OBDA_SEARCH_PATH?
> >
> > On Thu, May 22, 2003 at 07:48:47AM -0400, Brian Osborne wrote:
> > > Bioperl-l,
> > > The character '+' is being used a delimiter in this 
> variable instead 
> > > of
> >
> > the
> >
> > > standard Unix ';'. If I'm not mistaken one can use '+' in a 
> > > directory or file name, whereas ';' seems not to be allowed. In 
> > > fact, isn't
> >
> > "lost+found"
> >
> > > a system directory in some Unixes? Anyway, I will change 
> this unless
> >
> > someone
> >
> > > can convince me not to.
> > > Brian O.
> >
> > The ';' may be part of a directory or file name without any problem 
> > (just quote it for the shell).  The forward slash ('/'), 
> however, is 
> > not allowed on Unix-type systems (Mac OS X might have additional 
> > restrictions with ':'?).
> >
> > The plus sign is very uncommon in file names, and the "lost+found" 
> > directory (where 'fsck' stores files and directories which doesn't 
> > have an associated name after a system or disk crash) is about the 
> > only place I've ever seen it...  Having said that I haven't 
> seen ';' 
> > in a name *anywhere*, but it's allowed.
> >
> >     mkdir ';'
> >     ls -ldF ';'
> >     drwxr-x--x  2 ak       ensembl     4096 May 22 14:00 ;/
> >
> > The standard search path delimiter is the ':' (see you 
> $PATH variable 
> > for example).
> >
> > Andreas
> 
> -- 
> ==============================================================
> ==========
> Lincoln D. Stein                           Cold Spring Harbor 
> Laboratory
> lstein at cshl.org                                   Cold Spring 
> Harbor, NY
> ==============================================================
> ==========
> 
> 
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l at portal.open-bio.org 
> http://portal.open-> bio.org/mailman/listinfo/bioperl-l
> 
> 
> 
> 
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l at portal.open-bio.org 
> http://portal.open-> bio.org/mailman/listinfo/bioperl-l
>