Bash basics - Revision history

M at 15:42, 15 March 2019

2019-03-15T15:42:36Z

← Older revision		Revision as of 15:42, 15 March 2019
Line 1:		Line 1:
	Bash ~~certainly has its set~~ of snafus.		DO NOT USE BASH IF YOU HAVE ANOTHER OPTION. Bash is a bucket of snafus.

	=== proper way to exit mid-script ===		=== proper way to exit mid-script ===
	kill -SIGINT $$;		kill -SIGINT $$;

			=== squelch ALL output ===

			noisycommand &>/dev/null

	=== store commands in variables ===		=== store commands in variables ===

2017-07-13T12:29:10Z

← Older revision		Revision as of 12:29, 13 July 2017
Line 1:		Line 1:
	Bash certainly has its set of snafus.		Bash certainly has its set of snafus.

			=== proper way to exit mid-script ===
			kill -SIGINT $$;

	=== store commands in variables ===		=== store commands in variables ===

2017-07-13T12:27:29Z

← Older revision		Revision as of 12:27, 13 July 2017
Line 48:		Line 48:

	=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===		=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===

			=== misc ===
			{\| class="mw-collapsible mw-collapsed wikitable"
			! bash chmod dirs
			\|-
			\|
			find /path/to/base/dir -type d -exec chmod g+x {} \;
			\|}

2017-07-08T18:33:26Z

grep your code

← Older revision		Revision as of 18:33, 8 July 2017
Line 44:		Line 44:
	cd src		cd src
	grepcode blah		grepcode blah
			Here's the alias:
			alias grep='grep -inIEr --color=ALWAYS'

	=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===		=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===

2017-07-08T18:32:19Z

grep your code

← Older revision		Revision as of 18:32, 8 July 2017
Line 41:		Line 41:
	I use an alias for common params, so just do this:		I use an alias for common params, so just do this:
	grep "my[ ]regex" source/code/directory/ --include="*.cpp"		grep "my[ ]regex" source/code/directory/ --include="*.cpp"
	~~Here's the full format, from [https://readwrite.com/2010/11/10/how-to-search-your-source-with/~~ this ~~blog post]~~:		You can also use (and tweak) this helper:
	~~grep -inIEr –color=ALWAYS "my[ ]regex" source/code/directory/ --include="*.sh"~~		cd src
			grepcode blah

	=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===		=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===

2017-07-08T18:28:08Z

grep your code

← Older revision		Revision as of 18:28, 8 July 2017
Line 40:		Line 40:
	=== grep your code ===		=== grep your code ===
	I use an alias for common params, so just do this:		I use an alias for common params, so just do this:
	grep "my[ ]regex" source/code/directory/		grep "my[ ]regex" source/code/directory/ --include="*.cpp"
	Here's the full format, from [https://readwrite.com/2010/11/10/how-to-search-your-source-with/ this blog post]:		Here's the full format, from [https://readwrite.com/2010/11/10/how-to-search-your-source-with/ this blog post]:
	grep -inIEr –color=ALWAYS "my[ ]regex" source/code/directory/		grep -inIEr –color=ALWAYS "my[ ]regex" source/code/directory/ --include="*.sh"

	=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===		=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===

2017-07-08T18:07:11Z

grep your code

← Older revision		Revision as of 18:07, 8 July 2017
Line 38:		Line 38:
	fi</pre>		fi</pre>

	=== [https://readwrite.com/2010/11/10/how-to-search-your-source-with/ grep ~~your~~ code~~] ===~~		=== grep your code ===
			I use an alias for common params, so just do this:
			grep "my[ ]regex" source/code/directory/
			Here's the full format, from [https://readwrite.com/2010/11/10/how-to-search-your-source-with/ this blog post]:
			grep -inIEr –color=ALWAYS "my[ ]regex" source/code/directory/

	=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===		=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===

2017-07-07T13:44:22Z

← Older revision		Revision as of 13:44, 7 July 2017
Line 37:		Line 37:
	fi		fi
	fi</pre>		fi</pre>

			=== [https://readwrite.com/2010/11/10/how-to-search-your-source-with/ grep your code] ===

	=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===		=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===

2017-07-07T13:43:33Z

← Older revision		Revision as of 13:43, 7 July 2017
Line 1:		Line 1:
	Bash certainly has its set of snafus.		Bash certainly has its set of snafus.

	* To store commands in variables:		=== store commands in variables ===
	<pre># NOTE don't put spaces around equals sign!		<pre># NOTE don't put spaces around equals sign!
	# NOTE don't use ampersands within command strings, they won't work		# NOTE don't use ampersands within command strings, they won't work
Line 13:		Line 13:
	$mycmd1 && $mycmd2 && $mycmd3		$mycmd1 && $mycmd2 && $mycmd3
	</pre>		</pre>
	* To capture output		=== capture output ===
	<pre>myout=`program1 param`;</pre>		<pre>myout=`program1 param`;</pre>
	* Note the difference a single quote makes to output...		* Note the difference a single quote makes to output...
Line 21:		Line 21:
	abc def		abc def
	</pre>		</pre>
	* To check for an error		=== check for an error ===
	<pre>mkdir "$d2"		<pre>mkdir "$d2"
	if [ $? -gt 0 ]; then		if [ $? -gt 0 ]; then
Line 28:		Line 28:
	fi		fi
	</pre>		</pre>
	* To read input from user		=== read input from user ===
	<pre>echo "Create the subdirectory? [$d2]"		<pre>echo "Create the subdirectory? [$d2]"
	if read answer; then		if read answer; then
Line 38:		Line 38:
	fi</pre>		fi</pre>

	[http://www.panix.com/~elflord/unix/grep.html grep ~~powerful~~ options]		=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===

2017-07-07T13:42:18Z

← Older revision		Revision as of 13:42, 7 July 2017
Line 37:		Line 37:
	fi		fi
	fi</pre>		fi</pre>

			[http://www.panix.com/~elflord/unix/grep.html grep powerful options]