Adding directory to PATH found error

Support
1

I was adding Jetbrains IDE directory to PATH and the terminal gave me an error.

export PATH=“${PATH}:/home/$USER/.local/share/JetBrains/Toolbox/scripts”
source ~/.bash_profile

/usr/share/bash-completion/bash_completion:45: command not found: shopt
/usr/share/bash-completion/bash_completion:104: command not found: complete
/usr/share/bash-completion/bash_completion:107: command not found: complete
/usr/share/bash-completion/bash_completion:110: command not found: complete
/usr/share/bash-completion/bash_completion:113: command not found: complete
/usr/share/bash-completion/bash_completion:116: command not found: complete
/usr/share/bash-completion/bash_completion:119: command not found: complete
/usr/share/bash-completion/bash_completion:122: command not found: complete
/usr/share/bash-completion/bash_completion:125: command not found: complete
_comp_dequote__initialize:unset:5: no such hash table element: 
/usr/share/bash-completion/bash_completion:617: parse error near `&'
/home/binarydepth/.bashrc:type:65: bad option: -P
/home/binarydepth/.bashrc:106: command not found: shopt
/home/binarydepth/.bashrc:108: command not found: shopt
/home/binarydepth/.bashrc:113: command not found: shoptmpletion/bash_completion:122: command not found: complete
/usr/share/bash-completion/bash_completion:125: command not found: complete
_comp_dequote__initialize:unset:5: no such hash table element: 
/usr/share/bash-completion/bash_completion:617: parse error near `&'
/home/$USER/.bashrc:type:65: bad option: -P
/home/$USER/.bashrc:106: command not found: shopt
/home/$USER/.bashrc:108: command not found: shopt
/home/$USER/.bashrc:113: command not found: shopt
2

Which file did you edit?

reverse that
You clearly made a typo.

I’d use ~/.bashrc instead of ~/.bash_profile

Normally (that is how I’d do it)
~/.local/bin is for executables like scripts - not ~/.local/share

3

This has nothing to do with your path but can be indicator for 100 other things. Without more information it will be hard. Filesystem corruption, incomplete update…are some things to check.
P.s. or of course a typo, or wrong line ending or similar in the bash_profile. But you did not tell us the beginning of the story.

4

I think it didn’t change anything, this how it looks now:

#
# ~/.bash_profile
#

[[ -f ~/.bashrc ]] && . ~/.bashrc
5

No, it didn’t, because you didn’t actually change anything. :wink:

XY Problem detected: You’re asking about your attempted solution rather than your actual problem. This leads to enormous amounts of wasted time and energy, both on the part of people asking for help, and on the part of those providing help.

Please see:

7

Ok but I generally reported what the terminal is saying. Am I as a user supposed to know what is happening. The title says: Adding to PATH error found

8

…is that you might have things in your ~/.bashrc that cannot be processed–possibly unrelated to the application in question. :wink:

Yes, because only you made changes to your user files and installed a third party program that you setup yourself.

9

The errors are from sourcing bash profile, ergo .bashrc. The path is probably fine (a simple echo $PATH will tell you).

10

Excuse me? This is the Jetbrains Toolbox setup. I am following the Arch Wiki to do this FYI

11

A link to that wiki?

12

https://wiki.archlinux.org/title/Environment_variables#Per_user

13

…which you failed to mention in the first post.

Please help us help you by showing respect for the unpaid volunteers that like to help others.

The more information you provide, the more help you will receive.

14

Then tell me to add it. Voila

16

I’m not going to tell you to do anything. I’ve said what I said–which includes reviewing and abiding by the Forum Rules.

:information_source: Your topic is now hidden from the public temporarily until you can prove that you can abide by the rules you agreed to when you created an account on this forum.

17

It’s Ok. You told me as member of your community which you lead that I failed and I told you failed as a leader. welp there you go

18

I’ve just edited my reply above.

No, it’s not “Ok”.

EDIT: This is the official Manjaro support forum. It is neither a realtime chat nor a social network.

:hourglass:

19

Once again, your ~/.bashrc is broken and contains typo(s).
You messed it before, you just didn’t notice until now. But it is unrelated to your path.

20

@binarydepth
what @Teo said

If you want to go back to default without having to hunt for the typo you somehow introduced:

cp /etc/skel/.bashrc ~/

21

Moderator edit: Useless screenshot removed