[opensuse] SymLink bug in tcsh
I use tcsh under Leap 15.1.
When I type "ln -s" followed by some characters and hit the tab key
for getting a completion, the tcsh answers "
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/12/2019 18.07, Wolfgang Mueller wrote:
I use tcsh under Leap 15.1.
When I type "ln -s" followed by some characters and hit the tab key for getting a completion, the tcsh answers "
" instead of completing the file name. Without the parameter "-s", i.e. for a hard link, the completion works correctly.
When a new patch comes, I always hope there is a correction of this boring bug, but in vain. Since the tcsh users are a neglectable minority compared to the large bash user community, I am perhaps the only one that observes it.
I'll state the obvious: Bugzilla number? If there is no bugzilla, the issue does not exist. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXe/eVwAKCRC1MxgcbY1H 1T/wAJ9TEUYU6TwijVr9Pahz9DCH+qikwgCgjwNQB1Sx8UsaEzgW+JjBuFc1uYI= =zon0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 10 Dec 2019 at 19:05:21 +0100, Carlos E. R. wrote:
On 10/12/2019 18.07, Wolfgang Mueller wrote:
I use tcsh under Leap 15.1.
When I type "ln -s" followed by some characters and hit the tab key for getting a completion, the tcsh answers "
" instead of completing the file name. Without the parameter "-s", i.e. for a hard link, the completion works correctly.
When a new patch comes, I always hope there is a correction of this boring bug, but in vain. Since the tcsh users are a neglectable minority compared to the large bash user community, I am perhaps the only one that observes it.
I'll state the obvious: Bugzilla number?
If there is no bugzilla, the issue does not exist.
No idea how to find the Bugzilla number of my issue. I have joined the tcsh mailing list instead. Regards, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/10/19 3:39 PM, Wolfgang Mueller wrote:
On Tue, 10 Dec 2019 at 19:05:21 +0100, Carlos E. R. wrote:
On 10/12/2019 18.07, Wolfgang Mueller wrote:
I use tcsh under Leap 15.1.
When I type "ln -s" followed by some characters and hit the tab key for getting a completion, the tcsh answers "
" instead of completing the file name. Without the parameter "-s", i.e. for a hard link, the completion works correctly.
When a new patch comes, I always hope there is a correction of this boring bug, but in vain. Since the tcsh users are a neglectable minority compared to the large bash user community, I am perhaps the only one that observes it.
I'll state the obvious: Bugzilla number?
If there is no bugzilla, the issue does not exist.
No idea how to find the Bugzilla number of my issue. I have joined the tcsh mailing list instead.
Create a bug. If it already exists the maintainers will mark it as duplicate. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Architect LINUX Technical Team Lead Public Cloud rjschwei@suse.com IRC: robjo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2019-12-10 a las 21:39 +0100, Wolfgang Mueller escribió:
On Tue, 10 Dec 2019 at 19:05:21 +0100, Carlos E. R. wrote:
On 10/12/2019 18.07, Wolfgang Mueller wrote:
...
When a new patch comes, I always hope there is a correction of this boring bug, but in vain. Since the tcsh users are a neglectable minority compared to the large bash user community, I am perhaps the only one that observes it.
I'll state the obvious: Bugzilla number?
If there is no bugzilla, the issue does not exist.
No idea how to find the Bugzilla number of my issue. I have joined the tcsh mailing list instead.
No, no :-) The thing is, you found an issue and expect on each update to find it solved. But you have not reported it! It will never be solved unless /you/ report it in Bugzilla :-) That's how things work :-) - -- Cheers Carlos E. R. (from openSUSE 15.1 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXfA2Rhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVZfIAnjO7Kd03RFEtwk3H5cjp NSZr9ss7AJ4wZ6xI/HcUZYEPgIcjkf2EBPoptg== =Fqir -----END PGP SIGNATURE-----
On Wed, 11 Dec 2019 at 01:20:22 +0100, Carlos E. R. wrote:
El 2019-12-10 a las 21:39 +0100, Wolfgang Mueller escribió:
On Tue, 10 Dec 2019 at 19:05:21 +0100, Carlos E. R. wrote:
On 10/12/2019 18.07, Wolfgang Mueller wrote:
...
When a new patch comes, I always hope there is a correction of this boring bug, but in vain. Since the tcsh users are a neglectable minority compared to the large bash user community, I am perhaps the only one that observes it.
I'll state the obvious: Bugzilla number?
If there is no bugzilla, the issue does not exist.
No idea how to find the Bugzilla number of my issue. I have joined the tcsh mailing list instead.
No, no :-)
The thing is, you found an issue and expect on each update to find it solved. But you have not reported it! It will never be solved unless /you/ report it in Bugzilla :-)
That's how things work :-)
So let's have a look on things that do not work. ;) Since tcsh is not present in https://www.bugzilla.org, there is no possibility to report the bug there. So I have to resign myself to solving the issue only on the day of Saint Never. Sancte Nunquam, ora pro nobis! But that is less tragic than it sounds. It has been easy to find a simple workaround. Bye, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2019-12-11 a las 02:10 +0100, Wolfgang Mueller escribió:
On Wed, 11 Dec 2019 at 01:20:22 +0100, Carlos E. R. wrote:
El 2019-12-10 a las 21:39 +0100, Wolfgang Mueller escribió:
On Tue, 10 Dec 2019 at 19:05:21 +0100, Carlos E. R. wrote:
On 10/12/2019 18.07, Wolfgang Mueller wrote:
...
No, no :-)
The thing is, you found an issue and expect on each update to find it solved. But you have not reported it! It will never be solved unless /you/ report it in Bugzilla :-)
That's how things work :-)
So let's have a look on things that do not work. ;)
Since tcsh is not present in https://www.bugzilla.org, there is no possibility to report the bug there. So I have to resign myself to solving the issue only on the day of Saint Never. Sancte Nunquam, ora pro nobis!
But that is less tragic than it sounds. It has been easy to find a simple workaround.
LOL :-D Just select "other" when you do not know. But I think it is "basesystem". There is an unknown group of people that scans "other" and forward the bug to the right people. - -- Cheers Carlos E. R. (from openSUSE 15.1 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXfBFvhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVBOoAmwXS5Q3+i+kCt2jjYT1J UtFQLCdCAJ99/jeZMl6jXhnBbCehmmBA194w5w== =Ak5R -----END PGP SIGNATURE-----
On 12/11/19 11:56 AM, Carlos E. R. wrote:
El 2019-12-11 a las 02:10 +0100, Wolfgang Mueller escribió:
On Wed, 11 Dec 2019 at 01:20:22 +0100, Carlos E. R. wrote:
El 2019-12-10 a las 21:39 +0100, Wolfgang Mueller escribió:
On Tue, 10 Dec 2019 at 19:05:21 +0100, Carlos E. R. wrote:
On 10/12/2019 18.07, Wolfgang Mueller wrote:
...
No, no :-)
The thing is, you found an issue and expect on each update to find it solved. But you have not reported it! It will never be solved unless /you/ report it in Bugzilla :-)
That's how things work :-)
So let's have a look on things that do not work. ;)
Since tcsh is not present in https://www.bugzilla.org, there is no possibility to report the bug there. So I have to resign myself to solving the issue only on the day of Saint Never. Sancte Nunquam, ora pro nobis!
But that is less tragic than it sounds. It has been easy to find a simple workaround.
LOL :-D
Just select "other" when you do not know. But I think it is "basesystem".
He was looking at the wrong bugzilla, the following link will help you https://en.opensuse.org/openSUSE:Submitting_bug_reports (If an openSUSE bug doesn't exist then it's unlikely any fix would be taken from a new tcsh version and included in leap) -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/12/2019 03.23, Simon Lees wrote:
On 12/11/19 11:56 AM, Carlos E. R. wrote:
El 2019-12-11 a las 02:10 +0100, Wolfgang Mueller escribió:
On Wed, 11 Dec 2019 at 01:20:22 +0100, Carlos E. R. wrote:
> ...
That's how things work :-)
So let's have a look on things that do not work. ;)
Since tcsh is not present in https://www.bugzilla.org, there is no . . . . . . . . . . . . . . . . . . . . .*************** possibility to report the bug there. So I have to resign myself to solving the issue only on the day of Saint Never. Sancte Nunquam, ora pro nobis!
But that is less tragic than it sounds. It has been easy to find a simple workaround.
LOL :-D
Just select "other" when you do not know. But I think it is "basesystem".
He was looking at the wrong bugzilla, the following link will help you https://en.opensuse.org/openSUSE:Submitting_bug_reports (If an openSUSE bug doesn't exist then it's unlikely any fix would be taken from a new tcsh version and included in leap)
OOOooh, right! I did not see that. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXfC9QQAKCRC1MxgcbY1H 1YE1AJ9BJBGSd1zxyj8uDO71WFsBiNlCxQCfZtcK3eBheBJP0QhanoRbQjaC2Ds= =QcUp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R. -
Robert Schweikert -
Simon Lees -
Wolfgang Mueller