Simpler processing of shell script options
I’m looking for way to process shell script arguments that is cleaner and more “self documenting” than getopt/getopts.
bash
Regular expression problem(s) in Bash: [^negate] doesn’t seem to work
When I execute ls /directory | grep '[^term]' in Bash I get a regular listing, as if the grep command is ignored somehow. I tried the same thing with egrep, I tried to use it with double and single quotes, but to no better results. When I try ls /directory | grep '^[term] I get all entries beginning with term – as expected.
What’s the difference between “>&1” and “>/proc/self/fd/1” redirection?
I’m working on some script that being run by rc.local at startup, and I noticed that output redirection works quite strange.
Shell script to check for the presence of one or more files with a specific extension?
I want to write a script to find a file with specific extension.this much i have done:
How to call a script after every bash command
Is it possible to call a script in this example named hey.sh after every bash command?
Why does bash show ‘Terminated’ after killing a process?
Here is the behaviour I want to understand:
Why does “$(( ~33 ))” produce -34?
NOT x = −x − 1
Need a loop to sleep for a fraction of second
On my machine I need to execute a cycle that iterates 1 simple command that must have a delay expressed in fractions of second.
Kill backgrounded SSH when shell exits
I’m trying to spawn an SSH from my bash profile script that runs in the background for connection sharing (via its control socket). The problem I’m running into is a reliable way to ensure the SSH doesn’t stay running once the TTY is closed (or more directly; once the parent bash shell has exited).