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

How to run miniforge prompt with Powershell? #516

Open
MordorianGuy opened this issue Nov 16, 2023 · 7 comments
Open

How to run miniforge prompt with Powershell? #516

MordorianGuy opened this issue Nov 16, 2023 · 7 comments
Labels
question Further information is requested windows

Comments

@MordorianGuy
Copy link

Comment:

I have usually used anaconda before that provides "Anaconda Powershell Prompt" running a console corresponding to an environment where I could use conda commands. But I have found only "Miniforge prompt" running a cmd console not Powershell. How to run it in Powershell? I tried to run corresponding bat files (activate.bat & conda.bat activate) but nothing happened.

@MordorianGuy MordorianGuy added the question Further information is requested label Nov 16, 2023
@jaimergp
Copy link
Member

You can run powershell from cmd but I think we can port the shortcut over to conda-forge too.

@alex180500
Copy link

just do conda init powershell or mamba init powershell from the miniforge prompt and then you can use powershell as well.

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Mar 8, 2024

is the package that we would have to port over: https://anaconda.org/anaconda/powershell_shortcut ???

@keale
Copy link

keale commented Oct 5, 2024

Hello everyone,
I am trying to integrate miniforge release 24.7.1-2 into powershell 5.1. I did conda and mamba init powershell. After this I can call the mamba command from PS and create environments. But it is still not possible to activate an environment with mamba activate mytestenv. No errors are thrown, but the active environment is still base. With conda activate mytestenv it works. My PS profile file looks like this:

#region conda initialize
# !! Contents within this block are managed by 'conda init' !!
If (Test-Path "C:\Users\mysusername\mambaforge\Scripts\conda.exe") {
    (& "C:\Users\myusername\mambaforge\Scripts\conda.exe" "shell.powershell" "hook") | Out-String | ?{$_} | Invoke-Expression
}
#endregion

What I have to add to work with the mamba command? I use Winsows 10 pro, V. 2009

@alex180500
Copy link

This is a known issue of windows, see mamba-org/mamba#1717

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Oct 7, 2024

today with the introduction of conda-libmamba-solver the advantages of mamba are much more muted.

I think conda should be pretty fast. if that is an acceptable that should get you around most headaches.

@keale
Copy link

keale commented Oct 9, 2024

Ok, so long conda and mamba don't conflict both are fine for me. Thank You all for comments!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested windows
Development

No branches or pull requests

5 participants