Running from source forces new terminals to cd into ansible's source dir

[David Reagan]

So, I'm not sure this is an Ansible issue, but it might be, and I bet some of you could help me fix it anyway.

I'm running Ansible from source. As described here http://docs.ansible.com/intro_installation.html#running-from-source I have the repo in ~/vendor/ansible

A while back, after updating to the latest code, my terminals started cd'ing into ~/vendor/ansible whenever I created a new terminal.

It does this because I have my .zshrc file set up to automatically run ```source ./hacking/env-setup```. Basically, I don't want to have to run that command every time I reboot my machine.

First, is that the behaviour that the env-setup script is supposed display?

Second, is there a better way to run the source command automatically? Maybe some kind of if statement in my zshrc file that checks to make sure the hacking settings have been applied?

Thanks!

I'm using Ubuntu 14.04, Terminator, and Zsh, if it matters.

[Greg Andrews]

On Thu, Jan 15, 2015 at 4:57 PM, David Reagan <jer...@gmail.com> wrote:

A while back, after updating to the latest code, my terminals started cd'ing into ~/vendor/ansible whenever I created a new terminal.

It does this because I have my .zshrc file set up to automatically run ```source ./hacking/env-setup```. Basically, I don't want to have to run that command every time I reboot my machine.

I would put that source command into the zsh script that's invoked when you start an interactive shell rather than the file that's invoked on every shell.

  -Greg

[David Reagan]

Well, I did some experimenting with the files listed http://zsh.sourceforge.net/Doc/Release/Files.html#Files

A) env-setup has to be sourced for every terminal window.

B) If I place the source command in one of zsh's files that only gets run once, then new terminals need me to source env-setup again.

Also, I know I'm not very fluent in bash, but why is env-setup causing my terminal to change directories? I see no 'cd' commands in the file at all.

So, I think I can just set the various env values manually. But what about the gen_egg_info() function? And which vars do I really need to set?

--David Reagan

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/kkigUYTNhN8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAPdwyX7aipS-hzk_0XE1UaAKmRZO%3DUP5Rdqqyf%3DQ6D5qNCbfcw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Toshio Kuratomi]

On Jan 16, 2015 9:29 AM, "David Reagan" <jer...@gmail.com> wrote:
>
> Well, I did some experimenting with the files listed http://zsh.sourceforge.net/Doc/Release/Files.html#Files
>
> A) env-setup has to be sourced for every terminal window.
>
> B) If I place the source command in one of zsh's files that only gets run once, then new terminals need me to source env-setup again.
>
> Also, I know I'm not very fluent in bash, but why is env-setup causing my terminal to change directories? I see no 'cd' commands in the file at all.
>

Does this also happen if you source env-setup outside of zsh's startup scripts?

I bet the pushd popd commands are what's leaving you in the wrong directories.  However i'm using zsh with env-setup (not in my startup scripts though) and not run into any problems.  Might be some interaction with other zsh initialization... zsh is very flexible so something different between your config and mine could be causing this.

-Toshio

[Tom Bamford]

Hi David

I’m also using zsh although usually only source env-setup when I need it. If I do source it from ~/.zshrc, it doesn’t change my working directory.

Does adding set -x to the beginning of, and set +x to the end of the env-setup file offer any clues?

​

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CANo%2B_AevfMw_hzQNs0JNF9ofWBcNnhGWzrp2%3DOhX35fKzzWM8w%40mail.gmail.com.

[David Reagan]

To those who replied, thanks!

When I got to my work office computer, it wasn't cd'ing on me anymore. When I finally had time today to try and test things here on my home computer, it stopped cd'ing on me after I updated to the latest devel commit.

So, everything is working fine now. Go figure...

--David Reagan

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAAnNz0PUbovo9UCvkJQ37g9bijxt8mErWM0mpXc39LmFhK4hUw%40mail.gmail.com.