v2.0.4

UPDATE

v2.0.2

Merge #8 - huge thanks to @ahmetoozcan for all the help! Now, the program will not break PATH for Powershell (as in #7).

v2.0.1

• Fixed GitHub Action workflow
• This release includes all the goodies from version 2

Version 2.0 - Finally!

Version 2.0 adds the ability to specify system PATH.
While user PATH remains the default, you can now add !system to the query, and the command will operate on the system PATH rather than the user PATH. This works for all commands.

For example, instead of path add C:\foo, you can type path add !system C:\foo.

The !sytem flag is case-sensitive. Make sure there are no spaces in it, and that it is a separate term (surrounded with spaces).

The !system flag must appear directly after the command (e.g. add or get), or else it will be interpreted as part of the
inputted folder path - for example, path add C:\foo !system will not trigger the flag; instead, the literal path C:\foo !system will be added to the user PATH.

Important

Editing system PATH requires administrator privileges.
This means that Flow Launcher will show a popup requesting administrator privileges
every time this plugin is used with the !system flag.
To make FlowLauncher always run as administrator, see Running as Administrator.

Other Changes

Besides the addition of the !system flag, several major changes are included in this version. These include:

• An entirely new and reworked interface that makes using the plugin more intuitive
• A batch script to configure FlowLauncher to always run as administrator (to
  allow editing of the system PATH)
• Several major bug fixes (including input sanitization)
• Improved error handling and messages
• Folder path validation
• A feature to avoid and fix corruption of the PATH environmental variable.
  Along with all these new features, the code has been fully refactored and improved.

V1.0 (Initial Release)

Initial Release

Thoroughly Tested.

Warning: Dealing with environment variables is dangerous and can break things. Though I have tried to make this plugin as safe to use as I can, I cannot guarantee that it won't break or corrupt your PATH environment variable.

Use at your own risk. I am not responsible if this plugin breaks things for you.