Edit Learning

Title

Body Context: `rbenv` was installed but not activating correctly (`ruby -v` showed system Ruby, `which gem` showed system gem). The `rbenv init` command in my `.zshrc` was not correctly modifying the `PATH` to prioritize `rbenv` shims, potentially due to conflicts or ordering issues within the `.zshrc` file. Resolution (Temporary): I manually prepended the shims directory for the current session: `export PATH="$HOME/.rbenv/shims:$PATH"`. Resolution (Workaround): I followed the `PLANNING.md` convention of using `rbenv exec` before `bundle` and `rails` commands (e.g., `rbenv exec bundle install`, `rbenv exec rails db:create`). Resolution (Permanent Fix Needed): My `.zshrc` still requires investigation to ensure `rbenv init` works correctly on shell startup (check order, potential conflicts). Learning: Correct shell integration (`eval "$(rbenv init -)"`) is crucial for `rbenv`. I learned to check `PATH` and `.zshrc` initialization order if versions aren't switching automatically. `rbenv exec` is a reliable workaround if shell integration is problematic.

Learned on (YYYY-MM-DD)

Tags

Add comma-separated tags. They help filter learnings later.