asdf.sh script bug with bash OSX sessions

[gregors]

on OSX El Capitan the asdf.sh logic to find the root directory doesn't work correctly since the terminal started outputting "/Users/gregoryostermayr/.asdf Saving session... ...saving history...truncating history files... ...completed."

[Stratus3D]

@gregors what version of asdf are you running? You can find out by either running asdf --version or by looking at the second line in ~/.asdf/lib/utils.sh

[gregors]

"0.1" as per readme

[Stratus3D]

I'm on Yosemite (10.10.5), and I am unable to replicate this issue. I know there is an bug in version 0.1 when it's used in a directory name that contains spaces, but it doesn't look like that is the same issue as yours. Are you using Zsh or Bash? Do you have your .bashrc/.zshrc posted somewhere so I could take a look at them?

[gregors]

@Stratus3D you won't see this behavior on Yosemite only El Capitan - tries to be nice by adding a "global history" aka Bash Sessions. see http://superuser.com/questions/975678/strange-output-from-terminal-exit-command-is-this-a-virus

[gregors]

I'll take a stab at creating a fix and run it by you

[Stratus3D]

Great! I don't have access to a machine running El Capitan right now so this is a huge help.

I'm hoping to tag the 0.2.0 release sometime in next couple of weeks, but I'll definitely want to get your fix merged before the release. If you have any questions about the codebase feel free to ask questions.

[philipgiuliani]

I have the same problem on El Capitan :(

[HashNuke]

@gregors did you find a fix? I'm not able to reproduce this on latest master with El Capitan.

[philipgiuliani]

I fixed this bug by creating a file called .bash_sessions_disable. My sessions are still saved, so im not sure how this works.

@HashNuke could you check if you maybe have this file?

touch ~/.bash_sessions_disable

[HashNuke]

@philipgiuliani I don't have the file. But I came across the exact same issue on a colleague's computer last week and fixed it with some googling. I had to create that file.

I'm guessing the fix would have to be setting SHELL_SESSION_HISTORY=0 whenever we run bash internally.

[gregors]

@Stratus3D feedback appreciated

[gregors]

@HashNuke @philipgiuliani I've got a fix without having to disable bash sessions

[gregors]

ping

[jgonzalezd]

I just had this problem. touch ~/.bash_sessions_disablesolved the issue. (After one hour of googling and trying with my .bashrc and .bash_profile files)

[childnode]

-bash:$ type cd
cd is a function
cd () 
{ 
    __zsh_like_cd cd "$@"
}

unset cd and you're gone ... without disabling the history ... which is not a "fix"

https://stackoverflow.com/questions/25381304/why-type-cd-on-mac-os-states-that-cd-is-a-function

[Stratus3D]

@gregors can you check and see if your cd is actually a function?

[Stratus3D]

Closing this issue since it's unclear if this is actually a bug in asdf. PR #334 may help us avoid this problem as we don't use cd when computing the ASDF_DIR path.