Hi,

I'm a bit new to this all so bear with me...

I'm using cygwin and have installed Drush in my home directory. (I'm also running Xampp 1.7.1)

Everytime i run drush status I get '~/drush/drush: line 33: tput: command not found' on the first line. Everything else works correctly but this is annoying.

I tried adding export COLUMNS to my .bashrc file but it made no difference.

What am I doing wrong?

Thanks

Comments

greg.1.anderson’s picture

greg.1.anderson CreditAttribution: greg.1.anderson commented
Status: Active » Fixed

I have not tried to use drush with cygwin yet, but the problem is as it says: you do not have the tput command available under cygwin. Run the cygwin setup program and see if you can find it; it's probably in there somewhere.

tribe_of_dan’s picture

tribe_of_dan CreditAttribution: tribe_of_dan commented

I didn't realise tput was a command. For anyone else who needs this, Run the cygwin setup and look for the 'ncurses' package and install it.

Thanks greg.1.anderson!

greg.1.anderson’s picture

greg.1.anderson CreditAttribution: greg.1.anderson commented

ncurses package, huh? That doesn't sound super obvious. I added a comment to the drush script to help future cygwin users.

tribe_of_dan’s picture

tribe_of_dan CreditAttribution: tribe_of_dan commented

PS - I noticed Drush was outputting some wierd characters on Cygwin also. I'm assuming it was to do with the character set of cygwin.

Now I use PuTTY with Cygwin to access localhost on Windows. This helped get rid of that issue. See: http://nfnaaron.posterous.com/use-putty-with-cygwin-to-access-localhost-on

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

threading_signals’s picture

threading_signals CreditAttribution: threading_signals commented
Component: Code » PM (dl, en, up ...)

Is there a way to resolve this using the git bash, which uses msysgit for tput error resolution?

greg.1.anderson’s picture

greg.1.anderson CreditAttribution: greg.1.anderson commented

I don't know the answer to that question. I recommend opening a new issue if you want to discuss; closed issues don't get much play.