DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=q+p2vceQimiM0U6Zo/YaeSLYMICXFHzBz/v/Sp+eAUwHYLJq7lumE
	wSSE1X8LZyAqzrHVE4CTyPnBZTEGn2GD1cX0KP8yp1XXEsS7HuPvtTQ1aqdAuuGq
	+iB3zrnEZ+90IA1RkCKWpNZaYipM/Yo+l9GBJD9NjBeG9ONlJGVFy4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Fri, 3 Jul 2015 12:39:28 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: latest tcsh build has problems completing ln -s
Message-ID: <20150703103928.GY2918@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <loom DOT 20150702T214153-878 AT post DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="JKGvNdIvrY8Ovf7Z"
Content-Disposition: inline
In-Reply-To: <loom.20150702T214153-878@post.gmane.org>
User-Agent: Mutt/1.5.23 (2014-03-12)

--JKGvNdIvrY8Ovf7Z
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jul  2 19:56, Lester Ingber wrote:
> Since the newest tcsh build on Cygwin (i'm using cygwin64),
> version tcsh 6.19.00 (Astron) 2015-05-21 (x86_64-unknown-cygwin) options=
=20
> wide,nls,dl,al,kan,sm,rh,color
> the completion of files using TAB does not work anymore.
> It works fine under bash.
>=20
> I've inserted [TAB] where I have pressed Tab.
> On tcsh I just get "<link_name> as a response.=20=20
> The problem only occurs with trying soft links "ln -s" not hard links "ln=
".
>=20
> 12:34:48pm ingber AT lesterX1:~% touch tp1
> 12:35:00pm ingber AT lesterX1:~% ln -s ./t [TAB]
> <link_name>
> 12:35:00pm ingber AT lesterX1:~% ln -s ./tp1 tp2
> 12:35:15pm ingber AT lesterX1:~% ls -l
> -rw-r--r-- 1 ingber Users 0 Jul  2 12:35 tp1
> lrwxrwxrwx 1 ingber Users 5 Jul  2 12:35 tp2 -> ./tp1
> 12:38:09pm ingber AT lesterX1:~% bash
> [12:38:13 ingber AT lesterX1 ~]$ touch tp3
> [12:38:23 ingber AT lesterX1 ~]$ ln -s ./tp [TAB]
> tp1  tp2  tp3
> [12:38:23 ingber AT lesterX1 ~]$ ln -s ./tp3 tp4
> [12:39:22 ingber AT lesterX1 ~]$ ls -l
> -rw-r--r-- 1 ingber Users   0 Jul  2 12:35 tp1
> lrwxrwxrwx 1 ingber Users   5 Jul  2 12:35 tp2 -> ./tp1
> -rw-r--r-- 1 ingber Users   0 Jul  2 12:38 tp3
> lrwxrwxrwx 1 ingber Users   5 Jul  2 12:38 tp4 -> ./tp3
>=20
> I've compiled the new tcsh on several linux platforms,
> and this problem does not occur.

Yes, it does.  I just tested it on Linux and the same problem occurs.
It depends on whether you use the default completions from
/etc/profile.d/complete.tcsh or not.  Usually I don't (setting
`uncomplete *' in my .cshrc), neither on Cygwin nor on Linux.

So, yes, if I use the `ln' completion from /etc/profile.d/complete.tcsh,
I can reproduce this problem on Linux and Cygwin with tcsh-6.19,
while it works as expected on tcsh-6.18.

Looks like an upstream bug to me.  I'll report it to the maintainer.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--JKGvNdIvrY8Ovf7Z
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVlmZgAAoJEPU2Bp2uRE+gERgQAI6HFRM2NDP031D5YsUNVxnz
ivHzFbdAkVb+IF9Ngp/PeIOGv8tGPBJlr3KsEBA5XUR5hjabZBlosquAzK/GgzPy
cL8MBwdwDJ9OB5J35Qn2pTivmkkUF8giXYqI1fQrP6+5cAUbkM/3qxmq0Cxk2xQb
eIG6yWD8Q+HZSl8sejJMiI15LNd+wSDYos3vYpSLgnRr5cndUYAFAjBBHaCBhBq+
ppM6HbzOe9bfhA2Q2I5FFHunsTRojrtddouFaFJMhCDC0GEXvaS33NQvZGfT7zpJ
Ae+auhUTGv9tlx+tthDw3KYTqvGD4PFEEEas2OuqcKs3HEsXiCRK2EEmC6h4tBwF
hPDjPr8Krbau01n8Swo1QDUda50zacQVt3a3MRyfaQROfpMH6k+nqnHRopzXFW0e
Zge2wPJfqBQI0V8fS6SRHb3PvzTWqRLPTPOZf91txyzTFwty6di4k5+hgdx3EQ9n
eIyj5IJVaFNg+RTsmT08KGT/Yhc6TWgBdIzfXo7zO8AUxkSsU5ZRKH72gVPbBFrG
X3F0uJPA3FO2RbLiVIvW1N/tmfrbZU1PLf/boW4dFl0kh0geBenH/IrMEeqqvs70
Als2DY3OdWfmZ4HQpdhaXHkXim8E8JwwrQSv1NkF2IBvWr0Qz+jPgcFD5weZjgEV
0CPapapkGeB4hE8peisp
=URhq
-----END PGP SIGNATURE-----

--JKGvNdIvrY8Ovf7Z--