not valid in this context: PATH+ when source ~/.bash_profile in macos
My bash_profile as follows:
export PATH+=":/Users/steve/workspace/bash-tools/misc";
when I use
source ~/.bash_profile
it said
/Users/style/.bash_profile:export:2: not valid in this context: PATH+
I searched on Google but found nothing, please help
macos terminal
add a comment |
My bash_profile as follows:
export PATH+=":/Users/steve/workspace/bash-tools/misc";
when I use
source ~/.bash_profile
it said
/Users/style/.bash_profile:export:2: not valid in this context: PATH+
I searched on Google but found nothing, please help
macos terminal
Are you using bash, or zsh? That looks like a zsh error message...
– Gordon Davisson
Nov 21 at 3:32
I'm using zsh. Is it a problem?
– Steve Lam
Nov 21 at 4:31
add a comment |
My bash_profile as follows:
export PATH+=":/Users/steve/workspace/bash-tools/misc";
when I use
source ~/.bash_profile
it said
/Users/style/.bash_profile:export:2: not valid in this context: PATH+
I searched on Google but found nothing, please help
macos terminal
My bash_profile as follows:
export PATH+=":/Users/steve/workspace/bash-tools/misc";
when I use
source ~/.bash_profile
it said
/Users/style/.bash_profile:export:2: not valid in this context: PATH+
I searched on Google but found nothing, please help
macos terminal
macos terminal
asked Nov 21 at 2:28
Steve Lam
448818
448818
Are you using bash, or zsh? That looks like a zsh error message...
– Gordon Davisson
Nov 21 at 3:32
I'm using zsh. Is it a problem?
– Steve Lam
Nov 21 at 4:31
add a comment |
Are you using bash, or zsh? That looks like a zsh error message...
– Gordon Davisson
Nov 21 at 3:32
I'm using zsh. Is it a problem?
– Steve Lam
Nov 21 at 4:31
Are you using bash, or zsh? That looks like a zsh error message...
– Gordon Davisson
Nov 21 at 3:32
Are you using bash, or zsh? That looks like a zsh error message...
– Gordon Davisson
Nov 21 at 3:32
I'm using zsh. Is it a problem?
– Steve Lam
Nov 21 at 4:31
I'm using zsh. Is it a problem?
– Steve Lam
Nov 21 at 4:31
add a comment |
1 Answer
1
active
oldest
votes
zsh's export
command doesn't support the +=
operator, just =
. The standard way to do this is to explicitly include the old PATH
value:
export PATH="$PATH:/Users/steve/workspace/bash-tools/misc"
...but there's another problem. You said this was in your bash_profile, and that's explicitly a bash init file, not zsh. If you want setup to be shared between both bash and zsh, I'd recommend doing something like putting the actual setup code in ~/.profile (which is the generic startup file for POSIX login shells), and then source
ing it from separate ~/.zprofile and ~/.bash_profile files, like this:
[ -f ~/.profile ] || source ~/.profile
This way, you can also add zsh-only setup in the ~/.zprofile file, bash-only setup in the ~/.bash_profile file, and still have them share most of the setup.
On the other hand, if you only use zsh, then just put it in ~/.zprofile.
could you give more detail on how to do it, I don't quite get the step to do
– Steve Lam
Nov 21 at 7:56
1
@SteveLam To fix the error you're getting, replace theexport
command in your bash_profile with the one I gave above. To fix your profile setup... that's much more complicated. I'd have to know more about what shells you use and for what, and what's in your current init file(s) to give you much more advice than I did above.
– Gordon Davisson
Nov 22 at 1:07
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53404497%2fnot-valid-in-this-context-path-when-source-bash-profile-in-macos%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
zsh's export
command doesn't support the +=
operator, just =
. The standard way to do this is to explicitly include the old PATH
value:
export PATH="$PATH:/Users/steve/workspace/bash-tools/misc"
...but there's another problem. You said this was in your bash_profile, and that's explicitly a bash init file, not zsh. If you want setup to be shared between both bash and zsh, I'd recommend doing something like putting the actual setup code in ~/.profile (which is the generic startup file for POSIX login shells), and then source
ing it from separate ~/.zprofile and ~/.bash_profile files, like this:
[ -f ~/.profile ] || source ~/.profile
This way, you can also add zsh-only setup in the ~/.zprofile file, bash-only setup in the ~/.bash_profile file, and still have them share most of the setup.
On the other hand, if you only use zsh, then just put it in ~/.zprofile.
could you give more detail on how to do it, I don't quite get the step to do
– Steve Lam
Nov 21 at 7:56
1
@SteveLam To fix the error you're getting, replace theexport
command in your bash_profile with the one I gave above. To fix your profile setup... that's much more complicated. I'd have to know more about what shells you use and for what, and what's in your current init file(s) to give you much more advice than I did above.
– Gordon Davisson
Nov 22 at 1:07
add a comment |
zsh's export
command doesn't support the +=
operator, just =
. The standard way to do this is to explicitly include the old PATH
value:
export PATH="$PATH:/Users/steve/workspace/bash-tools/misc"
...but there's another problem. You said this was in your bash_profile, and that's explicitly a bash init file, not zsh. If you want setup to be shared between both bash and zsh, I'd recommend doing something like putting the actual setup code in ~/.profile (which is the generic startup file for POSIX login shells), and then source
ing it from separate ~/.zprofile and ~/.bash_profile files, like this:
[ -f ~/.profile ] || source ~/.profile
This way, you can also add zsh-only setup in the ~/.zprofile file, bash-only setup in the ~/.bash_profile file, and still have them share most of the setup.
On the other hand, if you only use zsh, then just put it in ~/.zprofile.
could you give more detail on how to do it, I don't quite get the step to do
– Steve Lam
Nov 21 at 7:56
1
@SteveLam To fix the error you're getting, replace theexport
command in your bash_profile with the one I gave above. To fix your profile setup... that's much more complicated. I'd have to know more about what shells you use and for what, and what's in your current init file(s) to give you much more advice than I did above.
– Gordon Davisson
Nov 22 at 1:07
add a comment |
zsh's export
command doesn't support the +=
operator, just =
. The standard way to do this is to explicitly include the old PATH
value:
export PATH="$PATH:/Users/steve/workspace/bash-tools/misc"
...but there's another problem. You said this was in your bash_profile, and that's explicitly a bash init file, not zsh. If you want setup to be shared between both bash and zsh, I'd recommend doing something like putting the actual setup code in ~/.profile (which is the generic startup file for POSIX login shells), and then source
ing it from separate ~/.zprofile and ~/.bash_profile files, like this:
[ -f ~/.profile ] || source ~/.profile
This way, you can also add zsh-only setup in the ~/.zprofile file, bash-only setup in the ~/.bash_profile file, and still have them share most of the setup.
On the other hand, if you only use zsh, then just put it in ~/.zprofile.
zsh's export
command doesn't support the +=
operator, just =
. The standard way to do this is to explicitly include the old PATH
value:
export PATH="$PATH:/Users/steve/workspace/bash-tools/misc"
...but there's another problem. You said this was in your bash_profile, and that's explicitly a bash init file, not zsh. If you want setup to be shared between both bash and zsh, I'd recommend doing something like putting the actual setup code in ~/.profile (which is the generic startup file for POSIX login shells), and then source
ing it from separate ~/.zprofile and ~/.bash_profile files, like this:
[ -f ~/.profile ] || source ~/.profile
This way, you can also add zsh-only setup in the ~/.zprofile file, bash-only setup in the ~/.bash_profile file, and still have them share most of the setup.
On the other hand, if you only use zsh, then just put it in ~/.zprofile.
answered Nov 21 at 5:40
Gordon Davisson
67.4k97792
67.4k97792
could you give more detail on how to do it, I don't quite get the step to do
– Steve Lam
Nov 21 at 7:56
1
@SteveLam To fix the error you're getting, replace theexport
command in your bash_profile with the one I gave above. To fix your profile setup... that's much more complicated. I'd have to know more about what shells you use and for what, and what's in your current init file(s) to give you much more advice than I did above.
– Gordon Davisson
Nov 22 at 1:07
add a comment |
could you give more detail on how to do it, I don't quite get the step to do
– Steve Lam
Nov 21 at 7:56
1
@SteveLam To fix the error you're getting, replace theexport
command in your bash_profile with the one I gave above. To fix your profile setup... that's much more complicated. I'd have to know more about what shells you use and for what, and what's in your current init file(s) to give you much more advice than I did above.
– Gordon Davisson
Nov 22 at 1:07
could you give more detail on how to do it, I don't quite get the step to do
– Steve Lam
Nov 21 at 7:56
could you give more detail on how to do it, I don't quite get the step to do
– Steve Lam
Nov 21 at 7:56
1
1
@SteveLam To fix the error you're getting, replace the
export
command in your bash_profile with the one I gave above. To fix your profile setup... that's much more complicated. I'd have to know more about what shells you use and for what, and what's in your current init file(s) to give you much more advice than I did above.– Gordon Davisson
Nov 22 at 1:07
@SteveLam To fix the error you're getting, replace the
export
command in your bash_profile with the one I gave above. To fix your profile setup... that's much more complicated. I'd have to know more about what shells you use and for what, and what's in your current init file(s) to give you much more advice than I did above.– Gordon Davisson
Nov 22 at 1:07
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53404497%2fnot-valid-in-this-context-path-when-source-bash-profile-in-macos%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you using bash, or zsh? That looks like a zsh error message...
– Gordon Davisson
Nov 21 at 3:32
I'm using zsh. Is it a problem?
– Steve Lam
Nov 21 at 4:31