bash if -f in home directory
Clash Royale CLAN TAG#URR8PPP
I try to determinate, if a given path points to a file or a directory. I tried this with following code:
#if $mypath is a file
if [[ -f $mypath ]]; then
and
#if mypath is a directory
if [[ -d $mypath ]]; then
Both of these snippets are working fine, when the given path is absolute e.g. /home/user/mydir/... But when the given path starts with a ~, like ~/mydir/... both of these snippets will return true, regardless if the path points to a file, or directory.
Does anybody know, what I'm missing, or if it's even possible?
bash
asked Feb 18 at 19:28
flobueflobue
11
|
show 1 more comment
I try to determinate, if a given path points to a file or a directory. I tried this with following code:
#if $mypath is a file
if [[ -f $mypath ]]; then
and
#if mypath is a directory
if [[ -d $mypath ]]; then
Both of these snippets are working fine, when the given path is absolute e.g. /home/user/mydir/... But when the given path starts with a ~, like ~/mydir/... both of these snippets will return true, regardless if the path points to a file, or directory.
Does anybody know, what I'm missing, or if it's even possible?
bash
asked Feb 18 at 19:28
flobueflobue
11
1
Unrelated: The variable calledPATHis very special. It contains a list of directories where commands may be used. Please use another variable name, preferably lower case. See e.g. Are there naming conventions for variables in shell scripts?
– Kusalananda
Feb 18 at 19:30
1
I can't reproduce this inbash5.0. How do you assign the value to your variable?
– Kusalananda
Feb 18 at 19:40
1
In fact, if$mypathcontains an actual tilde character, which has not been expanded to a home directory, both should test should fail (unless there's a file or directory with an actual tilde in its name at that path).
– Kusalananda
Feb 18 at 19:44
I fetch them from a config file, which is filtered, by a few simple grep commands.conf=$(cat /path/to/conf | grep -v "#" | grep -ve "^$")
– flobue
Feb 18 at 19:56
What do you mean with both tests should fail? That both won't work correctly, or just return a false? And what do you mean with an actual tilde character? Would they automatically be expanded in some cases?
– flobue
Feb 18 at 20:04
|
show 1 more comment
I try to determinate, if a given path points to a file or a directory. I tried this with following code:
#if $mypath is a file
if [[ -f $mypath ]]; then
and
#if mypath is a directory
if [[ -d $mypath ]]; then
Both of these snippets are working fine, when the given path is absolute e.g. /home/user/mydir/... But when the given path starts with a ~, like ~/mydir/... both of these snippets will return true, regardless if the path points to a file, or directory.
Does anybody know, what I'm missing, or if it's even possible?
bash
asked Feb 18 at 19:28
flobueflobue
11
I try to determinate, if a given path points to a file or a directory. I tried this with following code:
#if $mypath is a file
if [[ -f $mypath ]]; then
and
#if mypath is a directory
if [[ -d $mypath ]]; then
Both of these snippets are working fine, when the given path is absolute e.g. /home/user/mydir/... But when the given path starts with a ~, like ~/mydir/... both of these snippets will return true, regardless if the path points to a file, or directory.
Does anybody know, what I'm missing, or if it's even possible?
bash
bash
asked Feb 18 at 19:28
flobueflobue
11
asked Feb 18 at 19:28
flobueflobue
11
edited Feb 18 at 19:33
flobue
asked Feb 18 at 19:28
flobueflobue
11
asked Feb 18 at 19:28
flobueflobue
11
asked Feb 18 at 19:28
flobueflobue
11
11
1
Unrelated: The variable calledPATHis very special. It contains a list of directories where commands may be used. Please use another variable name, preferably lower case. See e.g. Are there naming conventions for variables in shell scripts?
– Kusalananda
Feb 18 at 19:30
1
I can't reproduce this inbash5.0. How do you assign the value to your variable?
– Kusalananda
Feb 18 at 19:40
1
In fact, if$mypathcontains an actual tilde character, which has not been expanded to a home directory, both should test should fail (unless there's a file or directory with an actual tilde in its name at that path).
– Kusalananda
Feb 18 at 19:44
I fetch them from a config file, which is filtered, by a few simple grep commands.conf=$(cat /path/to/conf | grep -v "#" | grep -ve "^$")
– flobue
Feb 18 at 19:56
What do you mean with both tests should fail? That both won't work correctly, or just return a false? And what do you mean with an actual tilde character? Would they automatically be expanded in some cases?
– flobue
Feb 18 at 20:04
|
show 1 more comment
1
Unrelated: The variable calledPATHis very special. It contains a list of directories where commands may be used. Please use another variable name, preferably lower case. See e.g. Are there naming conventions for variables in shell scripts?
– Kusalananda
Feb 18 at 19:30
1
I can't reproduce this inbash5.0. How do you assign the value to your variable?
– Kusalananda
Feb 18 at 19:40
1
In fact, if$mypathcontains an actual tilde character, which has not been expanded to a home directory, both should test should fail (unless there's a file or directory with an actual tilde in its name at that path).
– Kusalananda
Feb 18 at 19:44
I fetch them from a config file, which is filtered, by a few simple grep commands.conf=$(cat /path/to/conf | grep -v "#" | grep -ve "^$")
– flobue
Feb 18 at 19:56
What do you mean with both tests should fail? That both won't work correctly, or just return a false? And what do you mean with an actual tilde character? Would they automatically be expanded in some cases?
– flobue
Feb 18 at 20:04
1
1
Unrelated: The variable called
PATH is very special. It contains a list of directories where commands may be used. Please use another variable name, preferably lower case. See e.g. Are there naming conventions for variables in shell scripts?– Kusalananda
Feb 18 at 19:30
Unrelated: The variable called
PATH is very special. It contains a list of directories where commands may be used. Please use another variable name, preferably lower case. See e.g. Are there naming conventions for variables in shell scripts?– Kusalananda
Feb 18 at 19:30
1
1
I can't reproduce this in
bash 5.0. How do you assign the value to your variable?– Kusalananda
Feb 18 at 19:40
I can't reproduce this in
bash 5.0. How do you assign the value to your variable?– Kusalananda
Feb 18 at 19:40
1
1
In fact, if
$mypath contains an actual tilde character, which has not been expanded to a home directory, both should test should fail (unless there's a file or directory with an actual tilde in its name at that path).– Kusalananda
Feb 18 at 19:44
In fact, if
$mypath contains an actual tilde character, which has not been expanded to a home directory, both should test should fail (unless there's a file or directory with an actual tilde in its name at that path).– Kusalananda
Feb 18 at 19:44
I fetch them from a config file, which is filtered, by a few simple grep commands.
conf=$(cat /path/to/conf | grep -v "#" | grep -ve "^$")– flobue
Feb 18 at 19:56
I fetch them from a config file, which is filtered, by a few simple grep commands.
conf=$(cat /path/to/conf | grep -v "#" | grep -ve "^$")– flobue
Feb 18 at 19:56
What do you mean with both tests should fail? That both won't work correctly, or just return a false? And what do you mean with an actual tilde character? Would they automatically be expanded in some cases?
– flobue
Feb 18 at 20:04
What do you mean with both tests should fail? That both won't work correctly, or just return a false? And what do you mean with an actual tilde character? Would they automatically be expanded in some cases?
– flobue
Feb 18 at 20:04
|
show 1 more comment
1 Answer
1
active
oldest
votes
I found the problem.
The problem was, that I was fetching the path from an config file, and thus the path was saved as string. Trough this, the tilde was not expanded, which is the cause for the problem.
My workaround was just to manually replace the tilde with $HOME, which will be expanded, even if the path is quoted. So basically:
mypath="$mypath/#~/$HOME"
#if $mypath is a file
if [[ -f $mypath ]]; then
answered Feb 18 at 20:47
flobueflobue
11
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f501436%2fbash-if-f-in-home-directory%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
I found the problem.
The problem was, that I was fetching the path from an config file, and thus the path was saved as string. Trough this, the tilde was not expanded, which is the cause for the problem.
My workaround was just to manually replace the tilde with $HOME, which will be expanded, even if the path is quoted. So basically:
mypath="$mypath/#~/$HOME"
#if $mypath is a file
if [[ -f $mypath ]]; then
answered Feb 18 at 20:47
flobueflobue
11
add a comment |
I found the problem.
The problem was, that I was fetching the path from an config file, and thus the path was saved as string. Trough this, the tilde was not expanded, which is the cause for the problem.
My workaround was just to manually replace the tilde with $HOME, which will be expanded, even if the path is quoted. So basically:
mypath="$mypath/#~/$HOME"
#if $mypath is a file
if [[ -f $mypath ]]; then
answered Feb 18 at 20:47
flobueflobue
11
add a comment |
I found the problem.
The problem was, that I was fetching the path from an config file, and thus the path was saved as string. Trough this, the tilde was not expanded, which is the cause for the problem.
My workaround was just to manually replace the tilde with $HOME, which will be expanded, even if the path is quoted. So basically:
mypath="$mypath/#~/$HOME"
#if $mypath is a file
if [[ -f $mypath ]]; then
answered Feb 18 at 20:47
flobueflobue
11
I found the problem.
The problem was, that I was fetching the path from an config file, and thus the path was saved as string. Trough this, the tilde was not expanded, which is the cause for the problem.
My workaround was just to manually replace the tilde with $HOME, which will be expanded, even if the path is quoted. So basically:
mypath="$mypath/#~/$HOME"
#if $mypath is a file
if [[ -f $mypath ]]; then
answered Feb 18 at 20:47
flobueflobue
11
answered Feb 18 at 20:47
flobueflobue
11
answered Feb 18 at 20:47
flobueflobue
11
answered Feb 18 at 20:47
flobueflobue
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f501436%2fbash-if-f-in-home-directory%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
Unrelated: The variable called
PATHis very special. It contains a list of directories where commands may be used. Please use another variable name, preferably lower case. See e.g. Are there naming conventions for variables in shell scripts?– Kusalananda
Feb 18 at 19:30
1
I can't reproduce this in
bash5.0. How do you assign the value to your variable?– Kusalananda
Feb 18 at 19:40
1
In fact, if
$mypathcontains an actual tilde character, which has not been expanded to a home directory, both should test should fail (unless there's a file or directory with an actual tilde in its name at that path).– Kusalananda
Feb 18 at 19:44
I fetch them from a config file, which is filtered, by a few simple grep commands.
conf=$(cat /path/to/conf | grep -v "#" | grep -ve "^$")– flobue
Feb 18 at 19:56
What do you mean with both tests should fail? That both won't work correctly, or just return a false? And what do you mean with an actual tilde character? Would they automatically be expanded in some cases?
– flobue
Feb 18 at 20:04