Timeline for Odd inconsistency between executing and sourcing Bash script
Current License: CC BY-SA 4.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 1, 2024 at 22:40 | comment | added | Chris Davies | There are (were) a number of talk derivatives. I think ytalk was one that worked for me - but it was a good number of years ago | |
| Mar 1, 2024 at 18:45 | history | edited | mesr | CC BY-SA 4.0 | added 1 character in body |
| Mar 1, 2024 at 18:16 | comment | added | mesr | Good point, @PrestonL.Bannister and I'm aware. I tried talk already and could never get it to work. I came across multiple issues that many other users seem to be experiencing too. That is normally the point where I start exploring the possibility of implementing what I need, especially for such a simple, single task that I need this for. Without mentioning the learning value of doing so. | |
| Mar 1, 2024 at 16:56 | comment | added | Preston L. Bannister | Just to note, you are re-inventing "talk". sourceforge.net/directory/unix-talk | |
| Feb 29, 2024 at 15:06 | history | edited | mesr | CC BY-SA 4.0 | deleted 3 characters in body |
| Feb 26, 2024 at 15:36 | history | edited | mesr | CC BY-SA 4.0 | added 101 characters in body |
| Feb 26, 2024 at 13:43 | comment | added | ilkkachu | Right, tmux runs those commands through a shell (since otherwise that <<< within wouldn't work), and the shell interprets the quotes here. So nevermind. But, in general, foo="'something'"; echo "$foo" is not the same as echo "something", and putting extra quotes is a common mistake people make when trying to store a command in a variable... In any case, it's best to take care to not add unwanted differences when comparing one situation to another. | |
| Feb 26, 2024 at 12:51 | history | became hot network question | |||
| Feb 26, 2024 at 12:51 | vote | accept | mesr | ||
| Feb 26, 2024 at 12:16 | comment | added | mesr | By "both commands are not the same", do you mean that there are no quotes in the CLI form? Aren't quote inert anyways? They're in the scripted form to avoid code injection exploits. I tried adding them to the CLI form, just to be sure, with exact same result. I will update my question with debug output. | |
| Feb 26, 2024 at 11:51 | answer | added | Kamil Maciorowski | timeline score: 17 | |
| Feb 26, 2024 at 8:16 | comment | added | ilkkachu | Well, at least that tmux new "while true; do ... is not the same command as that tmux new "$TMUX_TOP" \; ... and for some reason you have single quotes embedded in the TMUX_TOP and TMUX_BOTTOM vars, ones that don't appear in the command you show in the other snippet. But you also don't show the set -x trace output, so we can't see what exactly happens. | |
| Feb 26, 2024 at 5:20 | history | edited | mesr | CC BY-SA 4.0 | deleted 2 characters in body |
| Feb 26, 2024 at 4:37 | history | edited | mesr | CC BY-SA 4.0 | edited title |
| Feb 26, 2024 at 4:23 | history | edited | mesr | CC BY-SA 4.0 | added 3 characters in body |
| Feb 26, 2024 at 4:17 | history | edited | mesr | CC BY-SA 4.0 | deleted 4 characters in body |
| Feb 26, 2024 at 4:10 | history | edited | mesr | CC BY-SA 4.0 | added 10 characters in body |
| Feb 26, 2024 at 4:05 | history | edited | mesr | CC BY-SA 4.0 | added 10 characters in body |
| Feb 26, 2024 at 3:50 | history | asked | mesr | CC BY-SA 4.0 |