Shell commands no longer run from the current repository directory

[peppy]

Regressed at some point, used to work. Testing on current HEAD (05ae080)

[stefanhaller]

Can't reproduce, seems to work correctly for me. Could you provide more detail? From which directory are you starting lazygit, and what is the path to your repo? This is hard to see from the video.

[peppy]

Sorry, here's a more clear video:

iTerm.2024-08-29.at.10.41.35.mp4

I'm starting lazygit from ~/Projects and the repo here is ~/Projects/osu.

May be something to do with my shell being fish, but it did work until recently and I don't believe I've changed anything at my end.

[stefanhaller]

It's probably caused by #3793 then. Does your config.fish cd to ~/Projects? That would explain it.

[peppy]

Yes, it does 😅, sorry I forgot that's how I had things setup:

if status is-interactive
    cd ~/Projects
end

I wonder if I can implement a solution in my config in that case.

[stefanhaller]

We have no way to customize the shell that is being used for custom commands. We were hoping that calling $SHELL -i would always work well, but here's one case where it doesn't.

One potential workaround could be if lazygit would set an environment variable (e.g. LAZYGIT_CUSTOM_COMMAND=1 or some such) which you could then check in your config file.

But my recommendation would be to remove it from your config file, and instead configure your terminal so that it cds to Projects when you open a new tab. Most terminals have such an option, I think.

[peppy]

I think the reason I set it up this way was for ssh sessions to also get the correct default directory. But I seldom use that so I will take your advice for now.

Thanks!