What is the logic behind how bash tests for true/false?What is the difference between : and true?What is the...

Patience, young "Padovan"

How to report a triplet of septets in NMR tabulation?

Example of a relative pronoun

What do you call a Matrix-like slowdown and camera movement effect?

Why is this code 6.5x slower with optimizations enabled?

Is Social Media Science Fiction?

Work Breakdown with Tikz

Shell script can be run only with sh command

How is it possible to have an ability score that is less than 3?

Are tax years 2016 & 2017 back taxes deductible for tax year 2018?

Motorized valve interfering with button?

Is there really no realistic way for a skeleton monster to move around without magic?

DOS, create pipe for stdin/stdout of command.com(or 4dos.com) in C or Batch?

Why don't electromagnetic waves interact with each other?

A Journey Through Space and Time

What is the offset in a seaplane's hull?

How do we improve the relationship with a client software team that performs poorly and is becoming less collaborative?

Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)

A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?

Infinite past with a beginning?

Why Is Death Allowed In the Matrix?

How do you conduct xenoanthropology after first contact?

I see my dog run

What would happen to a modern skyscraper if it rains micro blackholes?



What is the logic behind how bash tests for true/false?


What is the difference between : and true?What is the builtin `:` used for in Bash?bash script trap for exit and err and logic for differenceWhat is the rationale behind $array not expanding the whole array in ksh and bash?extract columns from TRUE/FALSE matrix based on proportion of TRUE values within the columnExpression evaluates to false in for loop whereas it's true in ifWhy does `source foo && true` exit the script in bash?for loop logic porting from bash to cshBash: how can I run `sudo -n true` in the background without interfering with `read`?What's the purpose of “true” in bash “if sudo true; then”






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















This:



echo $VAR



yields: something



And this:



[[ -z "$VAR" ]]
echo $?



yields: 1



Yet this:



if [[ -z "$TMUX_MAN_PANE" ]]; then
echo 'NEVER PRINTS!'



This screws with my head and I need some kind logical way to think about this before I go insane.



UPDATE



Here's some real code. I can't get this to fucking work for the life of me. Fuck bash. :)



tmux_man_page() {
if [[ "$TERM" =~ 'screen' ]] && [[ -n "$TMUX" ]]; then
tmux list-panes -t $TMUX_MAN_PANE &> /dev/null
echo $?
echo $TMUX_MAN_PANE
[[ -z "$TMUX_MAN_PANE" ]]
echo $?
if ! [[ -z "$TMUX_MAN_PANE" ]] && [[ $? ]]; then
echo luck
tmux -q respawn-pane -k -t $TMUX_MAN_PANE man $1
else
echo fuck
tmux split-window -vf man $1
TMUX_MAN_PANE=$(tmux display-message -p "#{pane_id}")
export TMUX_MAN_PANE
tmux select-pane -t {last}
fi
fi
}


UPDATE 2: Success



Finally figured it out. Was hvaing a hell of a time getting the status of the first line in the if statement. Had to do some trickery to get the output of the tmux statement in the first line of the if statement. If anyone knows a cleaner way to do this, I'm all ears.



Holy shit, I don't know how people program in Bash. Drives me nuts. Sorry for the foul language. I was apeshit. :) Here's the working code:



tmux_man_page() {
if [[ "$TERM" =~ 'screen' ]] && [[ -n "$TMUX" ]]; then
fucker=$(tmux list-panes -t $TMUX_MAN_PANE 2>&1)
if ! [[ -z "$TMUX_MAN_PANE" ]] && ! [[ $fucker =~ 'find pane' ]]; then
tmux -q respawn-pane -k -t $TMUX_MAN_PANE man $1
else
tmux split-window -vf man $1
TMUX_MAN_PANE=$(tmux display-message -p "#{pane_id}")
export TMUX_MAN_PANE
tmux select-pane -t {last}
fi
fi
}

tmux_man_page_close() {
if [ $TMUX_MAN_PANE ]; then
tmux kill-pane -t $TMUX_MAN_PANE
fi
}









share|improve this question




















  • 1





    Your update does not include enough information. Please (a) include the values of TERM, TMUX, and TMUX_MAN_PANE from before the function runs and (b) include the output of the function and then (c) explain how that output differs from what you expect.

    – John1024
    1 hour ago











  • It's all a mess. In the first line of the if statement, I just want to know if that command is throwing an error. There is no seemingly rational way to do that. I don't want the output from the command, I want to know if it's throwing an error. That's it.

    – StevieD
    1 hour ago













  • It's showing the command was a success even though it can't find the pane. I see no way to extract the output from that tmux command.

    – StevieD
    58 mins ago











  • I should just be going this in perl. Fuck this crazy shit.

    – StevieD
    57 mins ago











  • Jesus, finally figured it out. Posting solution.

    – StevieD
    52 mins ago




















1















This:



echo $VAR



yields: something



And this:



[[ -z "$VAR" ]]
echo $?



yields: 1



Yet this:



if [[ -z "$TMUX_MAN_PANE" ]]; then
echo 'NEVER PRINTS!'



This screws with my head and I need some kind logical way to think about this before I go insane.



UPDATE



Here's some real code. I can't get this to fucking work for the life of me. Fuck bash. :)



tmux_man_page() {
if [[ "$TERM" =~ 'screen' ]] && [[ -n "$TMUX" ]]; then
tmux list-panes -t $TMUX_MAN_PANE &> /dev/null
echo $?
echo $TMUX_MAN_PANE
[[ -z "$TMUX_MAN_PANE" ]]
echo $?
if ! [[ -z "$TMUX_MAN_PANE" ]] && [[ $? ]]; then
echo luck
tmux -q respawn-pane -k -t $TMUX_MAN_PANE man $1
else
echo fuck
tmux split-window -vf man $1
TMUX_MAN_PANE=$(tmux display-message -p "#{pane_id}")
export TMUX_MAN_PANE
tmux select-pane -t {last}
fi
fi
}


UPDATE 2: Success



Finally figured it out. Was hvaing a hell of a time getting the status of the first line in the if statement. Had to do some trickery to get the output of the tmux statement in the first line of the if statement. If anyone knows a cleaner way to do this, I'm all ears.



Holy shit, I don't know how people program in Bash. Drives me nuts. Sorry for the foul language. I was apeshit. :) Here's the working code:



tmux_man_page() {
if [[ "$TERM" =~ 'screen' ]] && [[ -n "$TMUX" ]]; then
fucker=$(tmux list-panes -t $TMUX_MAN_PANE 2>&1)
if ! [[ -z "$TMUX_MAN_PANE" ]] && ! [[ $fucker =~ 'find pane' ]]; then
tmux -q respawn-pane -k -t $TMUX_MAN_PANE man $1
else
tmux split-window -vf man $1
TMUX_MAN_PANE=$(tmux display-message -p "#{pane_id}")
export TMUX_MAN_PANE
tmux select-pane -t {last}
fi
fi
}

tmux_man_page_close() {
if [ $TMUX_MAN_PANE ]; then
tmux kill-pane -t $TMUX_MAN_PANE
fi
}









share|improve this question




















  • 1





    Your update does not include enough information. Please (a) include the values of TERM, TMUX, and TMUX_MAN_PANE from before the function runs and (b) include the output of the function and then (c) explain how that output differs from what you expect.

    – John1024
    1 hour ago











  • It's all a mess. In the first line of the if statement, I just want to know if that command is throwing an error. There is no seemingly rational way to do that. I don't want the output from the command, I want to know if it's throwing an error. That's it.

    – StevieD
    1 hour ago













  • It's showing the command was a success even though it can't find the pane. I see no way to extract the output from that tmux command.

    – StevieD
    58 mins ago











  • I should just be going this in perl. Fuck this crazy shit.

    – StevieD
    57 mins ago











  • Jesus, finally figured it out. Posting solution.

    – StevieD
    52 mins ago
















1












1








1








This:



echo $VAR



yields: something



And this:



[[ -z "$VAR" ]]
echo $?



yields: 1



Yet this:



if [[ -z "$TMUX_MAN_PANE" ]]; then
echo 'NEVER PRINTS!'



This screws with my head and I need some kind logical way to think about this before I go insane.



UPDATE



Here's some real code. I can't get this to fucking work for the life of me. Fuck bash. :)



tmux_man_page() {
if [[ "$TERM" =~ 'screen' ]] && [[ -n "$TMUX" ]]; then
tmux list-panes -t $TMUX_MAN_PANE &> /dev/null
echo $?
echo $TMUX_MAN_PANE
[[ -z "$TMUX_MAN_PANE" ]]
echo $?
if ! [[ -z "$TMUX_MAN_PANE" ]] && [[ $? ]]; then
echo luck
tmux -q respawn-pane -k -t $TMUX_MAN_PANE man $1
else
echo fuck
tmux split-window -vf man $1
TMUX_MAN_PANE=$(tmux display-message -p "#{pane_id}")
export TMUX_MAN_PANE
tmux select-pane -t {last}
fi
fi
}


UPDATE 2: Success



Finally figured it out. Was hvaing a hell of a time getting the status of the first line in the if statement. Had to do some trickery to get the output of the tmux statement in the first line of the if statement. If anyone knows a cleaner way to do this, I'm all ears.



Holy shit, I don't know how people program in Bash. Drives me nuts. Sorry for the foul language. I was apeshit. :) Here's the working code:



tmux_man_page() {
if [[ "$TERM" =~ 'screen' ]] && [[ -n "$TMUX" ]]; then
fucker=$(tmux list-panes -t $TMUX_MAN_PANE 2>&1)
if ! [[ -z "$TMUX_MAN_PANE" ]] && ! [[ $fucker =~ 'find pane' ]]; then
tmux -q respawn-pane -k -t $TMUX_MAN_PANE man $1
else
tmux split-window -vf man $1
TMUX_MAN_PANE=$(tmux display-message -p "#{pane_id}")
export TMUX_MAN_PANE
tmux select-pane -t {last}
fi
fi
}

tmux_man_page_close() {
if [ $TMUX_MAN_PANE ]; then
tmux kill-pane -t $TMUX_MAN_PANE
fi
}









share|improve this question
















This:



echo $VAR



yields: something



And this:



[[ -z "$VAR" ]]
echo $?



yields: 1



Yet this:



if [[ -z "$TMUX_MAN_PANE" ]]; then
echo 'NEVER PRINTS!'



This screws with my head and I need some kind logical way to think about this before I go insane.



UPDATE



Here's some real code. I can't get this to fucking work for the life of me. Fuck bash. :)



tmux_man_page() {
if [[ "$TERM" =~ 'screen' ]] && [[ -n "$TMUX" ]]; then
tmux list-panes -t $TMUX_MAN_PANE &> /dev/null
echo $?
echo $TMUX_MAN_PANE
[[ -z "$TMUX_MAN_PANE" ]]
echo $?
if ! [[ -z "$TMUX_MAN_PANE" ]] && [[ $? ]]; then
echo luck
tmux -q respawn-pane -k -t $TMUX_MAN_PANE man $1
else
echo fuck
tmux split-window -vf man $1
TMUX_MAN_PANE=$(tmux display-message -p "#{pane_id}")
export TMUX_MAN_PANE
tmux select-pane -t {last}
fi
fi
}


UPDATE 2: Success



Finally figured it out. Was hvaing a hell of a time getting the status of the first line in the if statement. Had to do some trickery to get the output of the tmux statement in the first line of the if statement. If anyone knows a cleaner way to do this, I'm all ears.



Holy shit, I don't know how people program in Bash. Drives me nuts. Sorry for the foul language. I was apeshit. :) Here's the working code:



tmux_man_page() {
if [[ "$TERM" =~ 'screen' ]] && [[ -n "$TMUX" ]]; then
fucker=$(tmux list-panes -t $TMUX_MAN_PANE 2>&1)
if ! [[ -z "$TMUX_MAN_PANE" ]] && ! [[ $fucker =~ 'find pane' ]]; then
tmux -q respawn-pane -k -t $TMUX_MAN_PANE man $1
else
tmux split-window -vf man $1
TMUX_MAN_PANE=$(tmux display-message -p "#{pane_id}")
export TMUX_MAN_PANE
tmux select-pane -t {last}
fi
fi
}

tmux_man_page_close() {
if [ $TMUX_MAN_PANE ]; then
tmux kill-pane -t $TMUX_MAN_PANE
fi
}






bash






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 48 mins ago







StevieD

















asked 1 hour ago









StevieDStevieD

1679




1679








  • 1





    Your update does not include enough information. Please (a) include the values of TERM, TMUX, and TMUX_MAN_PANE from before the function runs and (b) include the output of the function and then (c) explain how that output differs from what you expect.

    – John1024
    1 hour ago











  • It's all a mess. In the first line of the if statement, I just want to know if that command is throwing an error. There is no seemingly rational way to do that. I don't want the output from the command, I want to know if it's throwing an error. That's it.

    – StevieD
    1 hour ago













  • It's showing the command was a success even though it can't find the pane. I see no way to extract the output from that tmux command.

    – StevieD
    58 mins ago











  • I should just be going this in perl. Fuck this crazy shit.

    – StevieD
    57 mins ago











  • Jesus, finally figured it out. Posting solution.

    – StevieD
    52 mins ago
















  • 1





    Your update does not include enough information. Please (a) include the values of TERM, TMUX, and TMUX_MAN_PANE from before the function runs and (b) include the output of the function and then (c) explain how that output differs from what you expect.

    – John1024
    1 hour ago











  • It's all a mess. In the first line of the if statement, I just want to know if that command is throwing an error. There is no seemingly rational way to do that. I don't want the output from the command, I want to know if it's throwing an error. That's it.

    – StevieD
    1 hour ago













  • It's showing the command was a success even though it can't find the pane. I see no way to extract the output from that tmux command.

    – StevieD
    58 mins ago











  • I should just be going this in perl. Fuck this crazy shit.

    – StevieD
    57 mins ago











  • Jesus, finally figured it out. Posting solution.

    – StevieD
    52 mins ago










1




1





Your update does not include enough information. Please (a) include the values of TERM, TMUX, and TMUX_MAN_PANE from before the function runs and (b) include the output of the function and then (c) explain how that output differs from what you expect.

– John1024
1 hour ago





Your update does not include enough information. Please (a) include the values of TERM, TMUX, and TMUX_MAN_PANE from before the function runs and (b) include the output of the function and then (c) explain how that output differs from what you expect.

– John1024
1 hour ago













It's all a mess. In the first line of the if statement, I just want to know if that command is throwing an error. There is no seemingly rational way to do that. I don't want the output from the command, I want to know if it's throwing an error. That's it.

– StevieD
1 hour ago







It's all a mess. In the first line of the if statement, I just want to know if that command is throwing an error. There is no seemingly rational way to do that. I don't want the output from the command, I want to know if it's throwing an error. That's it.

– StevieD
1 hour ago















It's showing the command was a success even though it can't find the pane. I see no way to extract the output from that tmux command.

– StevieD
58 mins ago





It's showing the command was a success even though it can't find the pane. I see no way to extract the output from that tmux command.

– StevieD
58 mins ago













I should just be going this in perl. Fuck this crazy shit.

– StevieD
57 mins ago





I should just be going this in perl. Fuck this crazy shit.

– StevieD
57 mins ago













Jesus, finally figured it out. Posting solution.

– StevieD
52 mins ago







Jesus, finally figured it out. Posting solution.

– StevieD
52 mins ago












1 Answer
1






active

oldest

votes


















4














The key is that 0 means true and 1 (or any other non-zero value) means false.



In shell, a test that is true (or a program which completes successfully), exits with code 0. The test [[ -z "$VAR" ]] returns code zero (true) if $VAR is empty or one (false) if it is not empty:



$ var=""; [[ -z "$var" ]]; echo $?
0
$ var="NOT EMPTY"; [[ -z "$var" ]]; echo $?
1


In sum, if $VAR is non-empty, then [[ -z "$VAR" ]] is false (returns 1) and the then statement does not execute.



Did you intend for the test to return true if the variable was non-empty? If so, replace -z with -n:



$ var=""; [[ -n "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ -n "$var" ]]; echo $?
0


For brevity, the same test is performed if -n is omitted:



$ var=""; [[ "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ "$var" ]]; echo $?
0





share|improve this answer


























  • I just posted my real code. I cannot, for the life of me, get that to work. I'm literally going fucking nuts.

    – StevieD
    1 hour ago






  • 1





    @StevieD Run set -x and then run your code. This will show you how every step is evaluated.

    – John1024
    1 hour ago













  • Ah, shit. Forgot about that setting. I'll try it.

    – StevieD
    1 hour ago












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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f511129%2fwhat-is-the-logic-behind-how-bash-tests-for-true-false%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









4














The key is that 0 means true and 1 (or any other non-zero value) means false.



In shell, a test that is true (or a program which completes successfully), exits with code 0. The test [[ -z "$VAR" ]] returns code zero (true) if $VAR is empty or one (false) if it is not empty:



$ var=""; [[ -z "$var" ]]; echo $?
0
$ var="NOT EMPTY"; [[ -z "$var" ]]; echo $?
1


In sum, if $VAR is non-empty, then [[ -z "$VAR" ]] is false (returns 1) and the then statement does not execute.



Did you intend for the test to return true if the variable was non-empty? If so, replace -z with -n:



$ var=""; [[ -n "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ -n "$var" ]]; echo $?
0


For brevity, the same test is performed if -n is omitted:



$ var=""; [[ "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ "$var" ]]; echo $?
0





share|improve this answer


























  • I just posted my real code. I cannot, for the life of me, get that to work. I'm literally going fucking nuts.

    – StevieD
    1 hour ago






  • 1





    @StevieD Run set -x and then run your code. This will show you how every step is evaluated.

    – John1024
    1 hour ago













  • Ah, shit. Forgot about that setting. I'll try it.

    – StevieD
    1 hour ago
















4














The key is that 0 means true and 1 (or any other non-zero value) means false.



In shell, a test that is true (or a program which completes successfully), exits with code 0. The test [[ -z "$VAR" ]] returns code zero (true) if $VAR is empty or one (false) if it is not empty:



$ var=""; [[ -z "$var" ]]; echo $?
0
$ var="NOT EMPTY"; [[ -z "$var" ]]; echo $?
1


In sum, if $VAR is non-empty, then [[ -z "$VAR" ]] is false (returns 1) and the then statement does not execute.



Did you intend for the test to return true if the variable was non-empty? If so, replace -z with -n:



$ var=""; [[ -n "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ -n "$var" ]]; echo $?
0


For brevity, the same test is performed if -n is omitted:



$ var=""; [[ "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ "$var" ]]; echo $?
0





share|improve this answer


























  • I just posted my real code. I cannot, for the life of me, get that to work. I'm literally going fucking nuts.

    – StevieD
    1 hour ago






  • 1





    @StevieD Run set -x and then run your code. This will show you how every step is evaluated.

    – John1024
    1 hour ago













  • Ah, shit. Forgot about that setting. I'll try it.

    – StevieD
    1 hour ago














4












4








4







The key is that 0 means true and 1 (or any other non-zero value) means false.



In shell, a test that is true (or a program which completes successfully), exits with code 0. The test [[ -z "$VAR" ]] returns code zero (true) if $VAR is empty or one (false) if it is not empty:



$ var=""; [[ -z "$var" ]]; echo $?
0
$ var="NOT EMPTY"; [[ -z "$var" ]]; echo $?
1


In sum, if $VAR is non-empty, then [[ -z "$VAR" ]] is false (returns 1) and the then statement does not execute.



Did you intend for the test to return true if the variable was non-empty? If so, replace -z with -n:



$ var=""; [[ -n "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ -n "$var" ]]; echo $?
0


For brevity, the same test is performed if -n is omitted:



$ var=""; [[ "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ "$var" ]]; echo $?
0





share|improve this answer















The key is that 0 means true and 1 (or any other non-zero value) means false.



In shell, a test that is true (or a program which completes successfully), exits with code 0. The test [[ -z "$VAR" ]] returns code zero (true) if $VAR is empty or one (false) if it is not empty:



$ var=""; [[ -z "$var" ]]; echo $?
0
$ var="NOT EMPTY"; [[ -z "$var" ]]; echo $?
1


In sum, if $VAR is non-empty, then [[ -z "$VAR" ]] is false (returns 1) and the then statement does not execute.



Did you intend for the test to return true if the variable was non-empty? If so, replace -z with -n:



$ var=""; [[ -n "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ -n "$var" ]]; echo $?
0


For brevity, the same test is performed if -n is omitted:



$ var=""; [[ "$var" ]]; echo $?
1
$ var="NOT EMPTY"; [[ "$var" ]]; echo $?
0






share|improve this answer














share|improve this answer



share|improve this answer








edited 1 hour ago

























answered 1 hour ago









John1024John1024

48.4k5113128




48.4k5113128













  • I just posted my real code. I cannot, for the life of me, get that to work. I'm literally going fucking nuts.

    – StevieD
    1 hour ago






  • 1





    @StevieD Run set -x and then run your code. This will show you how every step is evaluated.

    – John1024
    1 hour ago













  • Ah, shit. Forgot about that setting. I'll try it.

    – StevieD
    1 hour ago



















  • I just posted my real code. I cannot, for the life of me, get that to work. I'm literally going fucking nuts.

    – StevieD
    1 hour ago






  • 1





    @StevieD Run set -x and then run your code. This will show you how every step is evaluated.

    – John1024
    1 hour ago













  • Ah, shit. Forgot about that setting. I'll try it.

    – StevieD
    1 hour ago

















I just posted my real code. I cannot, for the life of me, get that to work. I'm literally going fucking nuts.

– StevieD
1 hour ago





I just posted my real code. I cannot, for the life of me, get that to work. I'm literally going fucking nuts.

– StevieD
1 hour ago




1




1





@StevieD Run set -x and then run your code. This will show you how every step is evaluated.

– John1024
1 hour ago







@StevieD Run set -x and then run your code. This will show you how every step is evaluated.

– John1024
1 hour ago















Ah, shit. Forgot about that setting. I'll try it.

– StevieD
1 hour ago





Ah, shit. Forgot about that setting. I'll try it.

– StevieD
1 hour ago


















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f511129%2fwhat-is-the-logic-behind-how-bash-tests-for-true-false%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

Always On Availability groups resolving state after failover - Remote harden of transaction...

update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...