-bash: Setting: command not found - error when opening iterm [closed]

-1

I keep receiving this error message each time I open a new tab in iterm:

-bash: Setting: command not found

Not sure how to fix this. I think it may have to do with .bashrc file that I recently edited.

edited Feb 3 at 11:11

ilkkachu

59.9k996169

asked Feb 3 at 10:32

LunarAlchemist

closed as off-topic by Kusalananda, Jeff Schaller, jimmij, tripleee, Mr Shunz Feb 4 at 10:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

"Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Kusalananda, Jeff Schaller, jimmij, tripleee, Mr Shunz

If this question can be reworded to fit the rules in the help center, please edit the question.

3

Maybe have a look at your .bashrc file to see if it tries to run a command called Setting. Is this maybe a comment that is lacking a # character?

– Kusalananda
Feb 3 at 10:34

If this is on macOS, you should also check .bash_profile since bash is usually started as a login shell on that platform. Also, please don't post images of text.

– Kusalananda
Feb 3 at 10:44

Okay thanks, I will also check .bash_profile. I am new to this site. Ive see other posts with photos of text, is there a specific reason why you recommend not to post them? I thought it would help to determine the issue.

– LunarAlchemist
Feb 3 at 10:52

The contents of the file(s) and what you are seeing in the console may well be important for us to take part of, but post these as text rather than as screenshots. See e.g. unix.meta.stackexchange.com/questions/4086 which describes the issue with this.

– Kusalananda
Feb 3 at 11:02

Text is better than a photo of text, because text is easier to read: It does not suffer from low resolution, it is quicker to download, it can be translated, it can be read aloud, it can be pasted…

– ctrl-alt-delor
Feb 3 at 13:42

|
show 1 more comment

-1

I keep receiving this error message each time I open a new tab in iterm:

-bash: Setting: command not found

Not sure how to fix this. I think it may have to do with .bashrc file that I recently edited.

edited Feb 3 at 11:11

ilkkachu

59.9k996169

asked Feb 3 at 10:32

LunarAlchemist

closed as off-topic by Kusalananda, Jeff Schaller, jimmij, tripleee, Mr Shunz Feb 4 at 10:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

"Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Kusalananda, Jeff Schaller, jimmij, tripleee, Mr Shunz

If this question can be reworded to fit the rules in the help center, please edit the question.

3

Maybe have a look at your .bashrc file to see if it tries to run a command called Setting. Is this maybe a comment that is lacking a # character?

– Kusalananda
Feb 3 at 10:34

If this is on macOS, you should also check .bash_profile since bash is usually started as a login shell on that platform. Also, please don't post images of text.

– Kusalananda
Feb 3 at 10:44

Okay thanks, I will also check .bash_profile. I am new to this site. Ive see other posts with photos of text, is there a specific reason why you recommend not to post them? I thought it would help to determine the issue.

– LunarAlchemist
Feb 3 at 10:52

The contents of the file(s) and what you are seeing in the console may well be important for us to take part of, but post these as text rather than as screenshots. See e.g. unix.meta.stackexchange.com/questions/4086 which describes the issue with this.

– Kusalananda
Feb 3 at 11:02

Text is better than a photo of text, because text is easier to read: It does not suffer from low resolution, it is quicker to download, it can be translated, it can be read aloud, it can be pasted…

– ctrl-alt-delor
Feb 3 at 13:42

|
show 1 more comment

-1

I keep receiving this error message each time I open a new tab in iterm:

-bash: Setting: command not found

Not sure how to fix this. I think it may have to do with .bashrc file that I recently edited.

edited Feb 3 at 11:11

ilkkachu

59.9k996169

asked Feb 3 at 10:32

LunarAlchemist

I keep receiving this error message each time I open a new tab in iterm:

-bash: Setting: command not found

Not sure how to fix this. I think it may have to do with .bashrc file that I recently edited.

bash command

edited Feb 3 at 11:11

ilkkachu

59.9k996169

asked Feb 3 at 10:32

LunarAlchemist

edited Feb 3 at 11:11

ilkkachu

59.9k996169

asked Feb 3 at 10:32

LunarAlchemist

edited Feb 3 at 11:11

ilkkachu

59.9k996169

edited Feb 3 at 11:11

ilkkachu

59.9k996169

edited Feb 3 at 11:11

ilkkachu

59.9k996169

asked Feb 3 at 10:32

LunarAlchemist

asked Feb 3 at 10:32

LunarAlchemist

asked Feb 3 at 10:32

LunarAlchemist

closed as off-topic by Kusalananda, Jeff Schaller, jimmij, tripleee, Mr Shunz Feb 4 at 10:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

"Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Kusalananda, Jeff Schaller, jimmij, tripleee, Mr Shunz

If this question can be reworded to fit the rules in the help center, please edit the question.

closed as off-topic by Kusalananda, Jeff Schaller, jimmij, tripleee, Mr Shunz Feb 4 at 10:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

"Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Kusalananda, Jeff Schaller, jimmij, tripleee, Mr Shunz

If this question can be reworded to fit the rules in the help center, please edit the question.

3

Maybe have a look at your .bashrc file to see if it tries to run a command called Setting. Is this maybe a comment that is lacking a # character?

– Kusalananda
Feb 3 at 10:34

If this is on macOS, you should also check .bash_profile since bash is usually started as a login shell on that platform. Also, please don't post images of text.

– Kusalananda
Feb 3 at 10:44

Okay thanks, I will also check .bash_profile. I am new to this site. Ive see other posts with photos of text, is there a specific reason why you recommend not to post them? I thought it would help to determine the issue.

– LunarAlchemist
Feb 3 at 10:52

The contents of the file(s) and what you are seeing in the console may well be important for us to take part of, but post these as text rather than as screenshots. See e.g. unix.meta.stackexchange.com/questions/4086 which describes the issue with this.

– Kusalananda
Feb 3 at 11:02

Text is better than a photo of text, because text is easier to read: It does not suffer from low resolution, it is quicker to download, it can be translated, it can be read aloud, it can be pasted…

– ctrl-alt-delor
Feb 3 at 13:42

|
show 1 more comment

3

Maybe have a look at your .bashrc file to see if it tries to run a command called Setting. Is this maybe a comment that is lacking a # character?

– Kusalananda
Feb 3 at 10:34

If this is on macOS, you should also check .bash_profile since bash is usually started as a login shell on that platform. Also, please don't post images of text.

– Kusalananda
Feb 3 at 10:44

Okay thanks, I will also check .bash_profile. I am new to this site. Ive see other posts with photos of text, is there a specific reason why you recommend not to post them? I thought it would help to determine the issue.

– LunarAlchemist
Feb 3 at 10:52

The contents of the file(s) and what you are seeing in the console may well be important for us to take part of, but post these as text rather than as screenshots. See e.g. unix.meta.stackexchange.com/questions/4086 which describes the issue with this.

– Kusalananda
Feb 3 at 11:02

Text is better than a photo of text, because text is easier to read: It does not suffer from low resolution, it is quicker to download, it can be translated, it can be read aloud, it can be pasted…

– ctrl-alt-delor
Feb 3 at 13:42

Maybe have a look at your .bashrc file to see if it tries to run a command called Setting. Is this maybe a comment that is lacking a # character?

– Kusalananda
Feb 3 at 10:34

If this is on macOS, you should also check .bash_profile since bash is usually started as a login shell on that platform. Also, please don't post images of text.

– Kusalananda
Feb 3 at 10:44

Okay thanks, I will also check .bash_profile. I am new to this site. Ive see other posts with photos of text, is there a specific reason why you recommend not to post them? I thought it would help to determine the issue.

– LunarAlchemist
Feb 3 at 10:52

The contents of the file(s) and what you are seeing in the console may well be important for us to take part of, but post these as text rather than as screenshots. See e.g. unix.meta.stackexchange.com/questions/4086 which describes the issue with this.

– Kusalananda
Feb 3 at 11:02

Text is better than a photo of text, because text is easier to read: It does not suffer from low resolution, it is quicker to download, it can be translated, it can be read aloud, it can be pasted…

– ctrl-alt-delor
Feb 3 at 13:42

|
show 1 more comment

2 Answers
2

active

oldest

votes

That error message means Bash tried to run a command literally called Setting, i.e. a line that starts with that word.

Bash reads/can read a number of files as startup files, including at least /etc/profile, ~/.bash_profile, ~/.bash_login, ~/.profile, ~/.bashrc (depending on how it's started, see Bash Startup Files in the online reference), plus many distributions have /etc/profile also read the files in /etc/profile.d/.

You'll need to look into those to find the offending line.

answered Feb 3 at 11:16

ilkkachu

59.9k996169

add a comment |

Thanks for the assistance! There was a missing # symbol in front of the code for python setting in .bash_profile.

# Setting PATH for Python 3.7 is the corrected command line.

Then enter source .bash_profile command after edit.

source ~/.bash_profile

answered Feb 3 at 11:30

LunarAlchemist

add a comment |

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

That error message means Bash tried to run a command literally called Setting, i.e. a line that starts with that word.

You'll need to look into those to find the offending line.

answered Feb 3 at 11:16

ilkkachu

59.9k996169

add a comment |

That error message means Bash tried to run a command literally called Setting, i.e. a line that starts with that word.

You'll need to look into those to find the offending line.

answered Feb 3 at 11:16

ilkkachu

59.9k996169

add a comment |

That error message means Bash tried to run a command literally called Setting, i.e. a line that starts with that word.

You'll need to look into those to find the offending line.

answered Feb 3 at 11:16

ilkkachu

59.9k996169

That error message means Bash tried to run a command literally called Setting, i.e. a line that starts with that word.

You'll need to look into those to find the offending line.

answered Feb 3 at 11:16

ilkkachu

59.9k996169

answered Feb 3 at 11:16

ilkkachu

59.9k996169

answered Feb 3 at 11:16

ilkkachu

59.9k996169

answered Feb 3 at 11:16

ilkkachu

59.9k996169

add a comment |

Thanks for the assistance! There was a missing # symbol in front of the code for python setting in .bash_profile.

# Setting PATH for Python 3.7 is the corrected command line.

Then enter source .bash_profile command after edit.

source ~/.bash_profile

answered Feb 3 at 11:30

LunarAlchemist

add a comment |

Thanks for the assistance! There was a missing # symbol in front of the code for python setting in .bash_profile.

# Setting PATH for Python 3.7 is the corrected command line.

Then enter source .bash_profile command after edit.

source ~/.bash_profile

answered Feb 3 at 11:30

LunarAlchemist

add a comment |

Thanks for the assistance! There was a missing # symbol in front of the code for python setting in .bash_profile.

# Setting PATH for Python 3.7 is the corrected command line.

Then enter source .bash_profile command after edit.

source ~/.bash_profile

answered Feb 3 at 11:30

LunarAlchemist

Thanks for the assistance! There was a missing # symbol in front of the code for python setting in .bash_profile.

# Setting PATH for Python 3.7 is the corrected command line.

Then enter source .bash_profile command after edit.

source ~/.bash_profile

answered Feb 3 at 11:30

LunarAlchemist

answered Feb 3 at 11:30

LunarAlchemist

answered Feb 3 at 11:30

LunarAlchemist

answered Feb 3 at 11:30

LunarAlchemist

add a comment |

搜尋此網誌

mjhjmtu