Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Users using GitBash Need Export Not Set #141

Open
say25 opened this issue Apr 16, 2020 · 2 comments
Open

Windows Users using GitBash Need Export Not Set #141

say25 opened this issue Apr 16, 2020 · 2 comments

Comments

@say25
Copy link

say25 commented Apr 16, 2020

On Windows when using GitBash, Linux terminology export is used instead of set.

Ideally we would provide the ability to set an override setting to use Export over Set.

Example:

var cmd = format === 'export' ? 'export' : 'SET';

@aaron-seitz
Copy link

To gather more info, most users on Windows are utilizing Powershell without issue - is there a reason that you cannot utilize Powershell in this use case?

@say25
Copy link
Author

say25 commented May 29, 2020

I mean yea I can use Powershell but there are other cons. For example, we have bash scripts that are used cross OS that are easier to implement in bash (yes with Powershell Core you can have powershell on Linux and macOS but it is less popular). So in a bash shell, I can be running some commands, get to a point when I need to re-login and basically have to switch to Chrome to get the bash exports because calling alks ... will give me Powershell specific commands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants