Скачать или смотреть The PowerShell Equivalent of Unix Shell export Command

Discover how to use PowerShell to pass environment variables to Unix shells. Learn the proper syntax and steps to replicate the Unix `export` functionality in PowerShell.
---
This video is based on the question https://stackoverflow.com/q/62308709/ asked by the user 'Sled' ( https://stackoverflow.com/u/254477/ ) and on the answer https://stackoverflow.com/a/62309326/ provided by the user 'js2010' ( https://stackoverflow.com/u/6654942/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: What is the PowerShell equivalent of the Unix shell `export` command?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the Problem

When working across different operating systems, developers often face challenges when trying to share environment variables between shells. For instance, if you're transitioning from Unix-based systems to PowerShell, you might encounter a stumbling block when trying to replicate the Unix shell's export command, which allows you to set environment variables.

Here’s what’s happening:
You want to set an environment variable in PowerShell and then access that variable in a Bash subprocess. When you try to use the export command directly in PowerShell, you receive an error indicating that export is not recognized. In this post, we’ll break down how to effectively transfer variables between PowerShell and Bash by using the correct syntax and methodologies.

The Solution

The key to achieving your objective lies in using the correct environment variable syntax in PowerShell. Here's how you can do it:

1. Set Environment Variables Using the env: Drive

In PowerShell, you have a special drive called env: that allows you to work with environment variables. To assign a variable and make it accessible to an external process (like Bash), follow these steps:

Step 1: Assign a Value

You can assign a value to an environment variable using the $env: scope. Here’s the command:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Call Bash and Use the Variable

Once you have assigned the variable in PowerShell, you can call a Bash process and use that variable:

[[See Video to Reveal this Text or Code Snippet]]

Result

When executed, this code will output:

[[See Video to Reveal this Text or Code Snippet]]

This confirms that the variable pwtst was successfully passed to the Bash shell.

2. Using set-content for Environment Variables

Another method to set an environment variable for usage in a Bash subprocess is by using the set-content command. For example:

Command Syntax

[[See Video to Reveal this Text or Code Snippet]]

Expected Output

[[See Video to Reveal this Text or Code Snippet]]

This shows that the foo variable was correctly passed and echoed back from Bash.

Conclusion

In summary, if you're transitioning from Unix to PowerShell, remember that the export command does not exist in PowerShell. Instead, utilize the $env: context to set environment variables. This approach allows you to bridge the gap between PowerShell and Bash, making it easier to combine scripts and functions across different platforms.

Armed with this information, you can now port your existing Unix scripts to PowerShell more efficiently, ensuring your scripts remain functional and effective across environments.

For any further questions or troubleshooting, feel free to reach out in the comments or consult PowerShell documentation.