Re: Conda activate command problem
On Fri 14 Oct 2022 at 13:54:54 (-0400), Stephen P. Molnar wrote:
> Miniconda3 on Bullseye.
>
> After a routine reboot of the OS, an attempt to activate a conda
> environment with:
>
> source Miniconda/bin/activate results in:
>
> comp@AbNormal:~$ source Miniconda3/bin/activate
> -bash: Script: command not found
> -bash: $'\E[?2004h\E]0': command not found
> -bash: comp@AbNormal:: command not found
> -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found
> -bash: $'34m~\E[00m$': command not found
> -bash: $'\E[?2004l\r\E[?2004h\E]0': command not found
> -bash: comp@AbNormal:: command not found
> -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found
> -bash: $'34m~\E[00m$': command not found
> -bash: $'\E[?2004l\r\E[?2004h\E]0': command not found
> -bash: comp@AbNormal:: command not found
> -bash: $'32mcomp@AbNormal\E[00m:\E[01': command not found
> -bash: $'34m~\E[00m$': command not found
> -bash: $'exit\r': command not found
> -bash: Script: command not found
> comp@AbNormal:~$
>
> Unfortunately, this impacts on a manor portion of the software I use
> for my In silico Chemistry research.
>
> A solution will be much appreciated.
It looks as if you're trying to eat the output. Watch:
axis!auser 08:14:59 ~$ script
Script started, output log file is 'typescript'.
(This is /home/auser/.bashrc 2022 October 13 on /dev/sda5 toto05
(This is /home/auser/.bash-1-axis 2022 August 18 on bullseye)
(This is /home/auser/.bash-u-usbs 2022 October 13)
(This is /home/auser/.bash-t-transfers 2022 September 01 enp3s0)
(This is /home/auser/.bash-w-web 2022 August 18)
(This is /home/auser/.bash-9-axis 2022 August 18 @1600x900 on 0)
axis!auser 14:06:03 ~$
exit
Script done.
axis!auser 14:06:07 ~$ source typescript
bash: Script: command not found
bash: typescript: line 3: syntax error near unexpected token `$'\r''
'ash: typescript: line 3: `(This is /home/auser/.bash-1-axis 2022 August 18 on bullseye)
2 axis!auser 14:11:02 ~$
Cheers,
David.
Reply to: