Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Patch posted to SourceForge for zsh on cygwin

X-seq: zsh-workers 13271
From: Cosmo <cosmo@xxxxxxxxxxxx>
To: Andrej Borsenkow <Andrej.Borsenkow@xxxxxxxxxxxxxx>
Subject: Re: Patch posted to SourceForge for zsh on cygwin
Date: Thu, 14 Dec 2000 12:49:04 +0000
Cc: ZSH workers mailing list <zsh-workers@xxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
Organization: Transact Solutions
References: <000801c065cb$37db0180$21c9ca95@xxxxxxxxxxxxxx>
Sender: simond@xxxxxxxxxxxx

Andrej Borsenkow wrote:
> 
> I think it should be discussed here.
> 
> The patch checks for $HOME being single slash when processing startup files to
> avoid creating `//.zshrc' name that is interpreted as UNC name.

> So, I ask - should we commit this patch that does not actually solve the
> problems or just warn users against setting HOME to `/'?

Just a thought.

Would setting HOME to `/..' be any kind of workaround? It should point to the same place
as `/' but I don't know enough about any internal processing that would possibly optimise
a path of `/../' to `//'?

Cosmo

References:
- RE: Patch posted to SourceForge for zsh on cygwin
  - From: Andrej Borsenkow

Messages sorted by: Reverse Date, Date, Thread, Author