Skip to content

Should lazygit be aware of the current user's shell? #1642

@ghost

Description

Topic
Today (12/27/2021), lazygit assumes that bash is present on the user's computer, on linux-based OS's at least (or if this is not the default behavior and I doing something wrong, please let me know ;) ). This discussion is about the implementation of a "env variable search" to get the current user's shell.

Your thoughts

My thoughts on the matter are a favorable to a change in the source code, making it such tha lazygit always get the current shell that it is running in. That will prevent unexpected behavior such as launching a instance of bash to run external command or maybe not executing said command at all if bash is not a executable in the user's machine. This behavior is seen in the edit command for example

image

This is something that in most use cases will not occur but today, as I know of, lazygit doesn't cover this issue.

Should it be easy enough to implement, I propose this issue be adressed.

(Again, maybe I'm being dumb and again, to my knowledge, lazygit does not handle this edge case.)
Ps.: Sorry for any bad English. I'm not a native Englishe speaker.

Wishing fruitfull discussions

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions