Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bug with zsh 4.3.5 and umount on OpenBSD 4.3
- X-seq: zsh-users 12795
- From: "Mikael Magnusson" <mikachu@xxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: Bug with zsh 4.3.5 and umount on OpenBSD 4.3
- Date: Sun, 20 Apr 2008 00:12:58 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=i7sV2Zw6+O0pgl1xRmvjUxwYIMWBYNb9Bexl+xhYYJk=; b=bnYb4BNDTRvgvzRuikDVJeTmqW1FX2IVdERi1+GGmwlb0ZxRxxRaB7GMcOYopgGYUBsxoHrEktiNc+6FMXbx2mY6aSKdYcGhLoqjYeqgfwk82v+MruHbmFfjG+VC3kYr5ThMcRibpK74I7ZBGWCD5CQqeQUFWTvICow32Svpwjk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FGDSqvXbZ3Tgg3Il0DzNT0sRywLXf9qmDlEqIxwXrZ1rtS5MI6caz4dyOmGOGhO2pcQLPc17LjxLmkZUZujUvQYcpQXCc2biKB3s6HiefFInjq5s0oFvJML1IyfmOK5aIQ+IuueabnMc/mPqa/YcKDy/mCXM84HkAzpgl2+Puxo=
- In-reply-to: <20080419220822.GA7203@xxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20080419220822.GA7203@xxxxxxxxxxxxx>
On 20/04/2008, Rene Maroufi <info@xxxxxxxxxxx> wrote:
> Hello,
>
> I use zsh 4.3.5 on OpenBSD. I updated my Notebook with OpenBSD 4.3
> today. If I use the umount command and want to complete the directory
> name from the mountpoint, i became a error message.
>
> For example:
> umount /mn<Press Tab>readlink: unknown option -- q
> usage: readlink [-fn] file
> readlink: unknown option -- q
> usage: readlink [-fn] file
>
> It looks like the zsh want to use the command readlink with the option
> -q which don't exist on OpenBSD Systems.
>
> This doesn't happen with zsh 4.2 on my old OpenBSD 4.2 System.
>
> What can i do to use the completion without the readlink errors?
There was a big thread about this not many weeks ago, I think it's
been fixed in 4.3.6.
--
Mikael Magnusson
Messages sorted by:
Reverse Date,
Date,
Thread,
Author