starnge behavior command correction in tcsh

starnge behavior command correction in tcsh

[Marco Welti]

Hi all

I'm having a little problem with the command correction.
The correction always suggest to take built-in or aliased commands.

For example I have an alias ll 'ls -l'
If I enter ls on the command line I'm always prompted to for correction

mwelti@zug0023d ~~> ls  *

CORRECT>ll  * (y|n|e|a)? 

I'm using the following configuration
from .tcshrc
	set correct = cmd
	set autolist = ambiguous 
	set fignore = (\~ %)
	set complete

So the questions is if this is a bug in tcsh or if it is just a setup
problem

BTW: I'm using B20 and tcsh.curses.6.08.x.00

Best Regards,

Marco Welti
Solutions

The Fantastic Corporation(tm)  
- first in broadband multimedia -

Bahnhofstrasse 12
P.O. Box 1350
CH-6301 Zug, Switzerland
Tel.      +41 41 728 88 88
Direct   +41 41 728 89 56
Fax      +41 41 728 88 12

mailto:marco.welti@fantastic.com
http://www.fantastic.com

Zug - New York - London - Hamburg - Singapore -Lugano
Sydney - Tokyo - Milan - Paris - Washington DC - San Francisco


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: starnge behavior command correction in tcsh

[Corinna Vinschen]

Marco Welti wrote:
> [...]
> For example I have an alias ll 'ls -l'
> If I enter ls on the command line I'm always prompted to for correction
> 
> mwelti@zug0023d ~~> ls  *
> 
> CORRECT>ll  * (y|n|e|a)?
> [...]
> So the questions is if this is a bug in tcsh or if it is just a setup
> problem
> 
> BTW: I'm using B20 and tcsh.curses.6.08.x.00

Never seen this.
Maybe, it's related to another setting?

Corinna

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: starnge behavior command correction in tcsh

[Corinna Vinschen]

Marco Welti wrote:
> to me it looks like the if tcsh doesn't evaluate the $PATH
> (or the hash-table) before invoking the correction-processor.
> 
> mwelti@zug0023d ~~> which cp
> /usr/local/cygnus/CYGWIN~1/H-I586~1/bin/cp
> mwelti@zug0023d ~~> cp foo bar
> 
> CORRECT>cd foo bar (y|n|e|a)?
> 
> I reduced my .tcshrc to the single line
> set correct = cmd
> but without any success. So I don't think it is a shell-setup-problem.
> 
> Is there anything else I could try?

- In the above example:
  Is cp executed if you enter 'n' on the "CORRECT" line?
- Check if your PATH is correct.
- Check the mount points.
- Try in your bin dir `mv cp.exe cp'

Last but not least:

  unset correct

It's only boring the user, IMHO.

Regards,
Corinna


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com