What is the logic behind how bash tests for true/false?What is the difference between : and true?What is the...
Do Phineas and Ferb ever actually get busted in real time?
New order #4: World
Is there a familial term for apples and pears?
Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?
What would happen to a modern skyscraper if it rains micro blackholes?
declaring a variable twice in IIFE
"which" command doesn't work / path of Safari?
A function which translates a sentence to title-case
How do we improve the relationship with a client software team that performs poorly and is becoming less collaborative?
How do I create uniquely male characters?
N.B. ligature in Latex
How is it possible to have an ability score that is less than 3?
Example of a relative pronoun
Motorized valve interfering with button?
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
GPS Rollover on Android Smartphones
How to add power-LED to my small amplifier?
XeLaTeX and pdfLaTeX ignore hyphenation
When blogging recipes, how can I support both readers who want the narrative/journey and ones who want the printer-friendly recipe?
Are tax years 2016 & 2017 back taxes deductible for tax year 2018?
What makes Graph invariants so useful/important?
How old can references or sources in a thesis be?
Is it tax fraud for an individual to declare non-taxable revenue as taxable income? (US tax laws)
Draw simple lines in Inkscape
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;
}
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
add a comment |
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
1
Your update does not include enough information. Please (a) include the values ofTERM
,TMUX
, andTMUX_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
1 hour ago
I should just be going this in perl. Fuck this crazy shit.
– StevieD
1 hour ago
Jesus, finally figured it out. Posting solution.
– StevieD
1 hour ago
add a comment |
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
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
bash
edited 57 mins ago
StevieD
asked 1 hour ago
StevieDStevieD
1679
1679
1
Your update does not include enough information. Please (a) include the values ofTERM
,TMUX
, andTMUX_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
1 hour ago
I should just be going this in perl. Fuck this crazy shit.
– StevieD
1 hour ago
Jesus, finally figured it out. Posting solution.
– StevieD
1 hour ago
add a comment |
1
Your update does not include enough information. Please (a) include the values ofTERM
,TMUX
, andTMUX_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
1 hour ago
I should just be going this in perl. Fuck this crazy shit.
– StevieD
1 hour ago
Jesus, finally figured it out. Posting solution.
– StevieD
1 hour 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
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
1 hour ago
I should just be going this in perl. Fuck this crazy shit.
– StevieD
1 hour ago
I should just be going this in perl. Fuck this crazy shit.
– StevieD
1 hour ago
Jesus, finally figured it out. Posting solution.
– StevieD
1 hour ago
Jesus, finally figured it out. Posting solution.
– StevieD
1 hour ago
add a comment |
1 Answer
1
active
oldest
votes
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
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 Runset -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
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%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
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
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 Runset -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
add a comment |
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
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 Runset -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
add a comment |
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
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
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 Runset -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
add a comment |
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 Runset -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
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%2f511129%2fwhat-is-the-logic-behind-how-bash-tests-for-true-false%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
Your update does not include enough information. Please (a) include the values of
TERM
,TMUX
, andTMUX_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
1 hour ago
I should just be going this in perl. Fuck this crazy shit.
– StevieD
1 hour ago
Jesus, finally figured it out. Posting solution.
– StevieD
1 hour ago