I don't know why but on gmail the error doesn't displAy correctly.

Traceback (most recent call last):
    File "<string>", line 1, in <module>
  ImportError: No module named virtualenvwrapper.hook_loader
  virtualenvwrapper.sh: There was a problem running the initialization
hooks.
  If Python could not import the module virtualenvwrapper.hook_loader, check
  that virtualenv has been installed for VIRTUALENVWRAPPER_PYTHON=/usr
   /bin/python and that PATH is  set properly.

is printed twice in the tty with the hilighted line between the two.

On Fri, Mar 23, 2012 at 10:26 AM, Michael Havens <bmike1@gmail.com> wrote:

> hmmmm.... in the tty the error is a bit different:
>
>
> Traceback (most recent call last):
>     File "<string>", line 1, in <module>
>   ImportError: No module named virtualenvwrapper.hook_loader
>   virtualenvwrapper.sh: There was a problem running the initialization
> hooks.
>   If Python could not import the module virtualenvwrapper.hook_loader,
> check
>   that virtualenv has been installed for VIRTUALENVWRAPPER_PYTHON=/usr
>    /bin/python and that PATH is  set properly.
>    --bash:__rvm_add_to_path: command not found.
>
> Traceback (most recent call last):
>     File "<string>", line 1, in <module>
>   ImportError: No module named virtualenvwrapper.hook_loader
>   virtualenvwrapper.sh: There was a problem running the initialization
> hooks.
>   If Python could not import the module virtualenvwrapper.hook_loader,
> check
>   that virtualenv has been installed for VIRTUALENVWRAPPER_PYTHON=/usr
>    /bin/python and that PATH is  set properly.
>
>
> On Fri, Mar 23, 2012 at 10:21 AM, Michael Havens <bmike1@gmail.com> wrote:
>
>> thanks Gerard!
>>
>>
>> On Fri, Mar 23, 2012 at 10:11 AM, Gerard Snitselaar <dev@snitselaar.org>wrote:
>>
>>> On Fri Mar 23 12, Michael Havens wrote:
>>> > I moved ~/.bashrc to ~/.bashrc-old and the error remains.
>>> > hmmmmmm.... I just looked at my directory to verify that ~/.bashrc was
>>> > moved and see a file called '.bashrc~'. the contents of which is what
>>> was
>>> > in .bashrc:
>>> >
>>> >      more .bashrc~
>>> >      [[ -s $HOME/.pythonbrew/etc/bashrc ]] && source $HOME/.pythonbrew
>>> >           /etc/bashrc
>>> >
>>> > I wonder where that file came from!
>>> >
>>>
>>> Files ending with ~ are backup files created by editors normally when
>>> you modify a file.
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>>
>>
>>
>>
>> --
>> :-)~MIKE~(-:
>>
>
>
>
> --
> :-)~MIKE~(-:
>



-- 
:-)~MIKE~(-: