Is this a typo in Bash manual’s redirection section?
The use of the word duplication seems a little strange to me in
this context. Perhaps that is throwing me.
bash
Stateful bash function
I’d like to implement a function in Bash which increases (and returns) a count with every call. Unfortunately this seems non-trivial since I’m invoking the function inside a subshell and it consequently cannot modify its parent shell’s variables.
Bash is not finding a program even though it’s on my path
I have a program on my path. The program runs when executed with a full path specified. But the program cannot be found when I run it with just its name.
Using data read from a pipe instead than from a file in command options
Per man definition, this command gets the input from a file.
What’s the right way to quote $(command $arg)?
It’s high time to solve this conundrum that’s been bothering me for years…
How do I close a terminal without saving the history?
More than once I’ve accidentally run a number of commands and polluted my bash history. How do I close my terminal without saving my bash history? I’m using Fedora.
understand a sequence of redirections
If several redirections are used together, does changing their order make difference?
Is there a way to set the size of the history list in bash to more than 5000 lines?
No matter how much I set the HISTSIZE environment variable to be larger than 5000, when printing the history list with the history builtin, it prints only the last 5000 commands.
I need that because I often have a large .bash_history which exceeds 5000 lines, and sometimes one needs to address an early command by pressing Ctrl-R, but if that command is more than 5000 commands earlier, I can’t access it using that mechanism. I know I can use grep on the .bash_history, but I think the Ctrl-R mechanism would be much more faster (and convenient). I use gnu bash version 4.1.
Invisible prompt after global redirection of stderr to /dev/null
Studying TLDP’s Advanced Bash-Scripting Guide I am unable to reconstruct the following shell output in bash 4.4.12 in debian 9, both from tty and pts:
Confusing use of && and || operators
I was skimming through an /etc/rc.d/init.d/sendmail file (I know this is hardly ever used, but I’m studying for an exam), and I’ve become a bit confused about the && and the || operators. I’ve read where they can be used in statements such as: