“which” sometimes includes an extra backslash in bash
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
When looking for java, I typed "which java" in terminal. Printed "/usr/bin//java." The double "/" shouldn't be there. What's going on?
bash shell path
asked Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
add a comment |
When looking for java, I typed "which java" in terminal. Printed "/usr/bin//java." The double "/" shouldn't be there. What's going on?
bash shell path
asked Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
1
This is a (mild) misbehavior of thewhichprogram: Bash’s built-intypediscards the extra/.
– Davis Herring
Dec 29 '18 at 2:38
add a comment |
When looking for java, I typed "which java" in terminal. Printed "/usr/bin//java." The double "/" shouldn't be there. What's going on?
bash shell path
asked Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
When looking for java, I typed "which java" in terminal. Printed "/usr/bin//java." The double "/" shouldn't be there. What's going on?
bash shell path
bash shell path
asked Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
asked Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
asked Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
asked Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
asked Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
1861215
1
This is a (mild) misbehavior of thewhichprogram: Bash’s built-intypediscards the extra/.
– Davis Herring
Dec 29 '18 at 2:38
add a comment |
1
This is a (mild) misbehavior of thewhichprogram: Bash’s built-intypediscards the extra/.
– Davis Herring
Dec 29 '18 at 2:38
1
1
This is a (mild) misbehavior of the
which program: Bash’s built-in type discards the extra /.– Davis Herring
Dec 29 '18 at 2:38
This is a (mild) misbehavior of the
which program: Bash’s built-in type discards the extra /.– Davis Herring
Dec 29 '18 at 2:38
add a comment |
1 Answer
1
active
oldest
votes
It turns out the PATH had /usr/bin/ in it, and the extra "/" was picked up. Changing the path to contain /usr/bin with no trailing "/" fixed the problem.
answered Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
1
This is not a problem. The path still works fine in all contexts.
– that other guy
Nov 23 '18 at 21:29
Maybe. It sure confused me.
– Zach Boyd
Nov 23 '18 at 21:30
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%2f53453091%2fwhich-sometimes-includes-an-extra-backslash-in-bash%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
It turns out the PATH had /usr/bin/ in it, and the extra "/" was picked up. Changing the path to contain /usr/bin with no trailing "/" fixed the problem.
answered Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
1
This is not a problem. The path still works fine in all contexts.
– that other guy
Nov 23 '18 at 21:29
Maybe. It sure confused me.
– Zach Boyd
Nov 23 '18 at 21:30
add a comment |
It turns out the PATH had /usr/bin/ in it, and the extra "/" was picked up. Changing the path to contain /usr/bin with no trailing "/" fixed the problem.
answered Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
1
This is not a problem. The path still works fine in all contexts.
– that other guy
Nov 23 '18 at 21:29
Maybe. It sure confused me.
– Zach Boyd
Nov 23 '18 at 21:30
add a comment |
It turns out the PATH had /usr/bin/ in it, and the extra "/" was picked up. Changing the path to contain /usr/bin with no trailing "/" fixed the problem.
answered Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
It turns out the PATH had /usr/bin/ in it, and the extra "/" was picked up. Changing the path to contain /usr/bin with no trailing "/" fixed the problem.
answered Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
answered Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
answered Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
answered Nov 23 '18 at 21:25
Zach BoydZach Boyd
1861215
1861215
1
This is not a problem. The path still works fine in all contexts.
– that other guy
Nov 23 '18 at 21:29
Maybe. It sure confused me.
– Zach Boyd
Nov 23 '18 at 21:30
add a comment |
1
This is not a problem. The path still works fine in all contexts.
– that other guy
Nov 23 '18 at 21:29
Maybe. It sure confused me.
– Zach Boyd
Nov 23 '18 at 21:30
1
1
This is not a problem. The path still works fine in all contexts.
– that other guy
Nov 23 '18 at 21:29
This is not a problem. The path still works fine in all contexts.
– that other guy
Nov 23 '18 at 21:29
Maybe. It sure confused me.
– Zach Boyd
Nov 23 '18 at 21:30
Maybe. It sure confused me.
– Zach Boyd
Nov 23 '18 at 21:30
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.
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%2f53453091%2fwhich-sometimes-includes-an-extra-backslash-in-bash%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
1
This is a (mild) misbehavior of the
whichprogram: Bash’s built-intypediscards the extra/.– Davis Herring
Dec 29 '18 at 2:38