Bash variables - Revision history

Chubbard at 22:02, 25 April 2024

2024-04-25T22:02:15Z

← Older revision		Revision as of 15:02, 25 April 2024
Line 1:		Line 1:
			<metadesc>Examples of working with bash variables</metadesc>
	== Finding defined variables ==		== Finding defined variables ==
	Assuming you have done something like foo="bar" at your bash prompt it is not always clear how to echo ALL the defined variables back from your bash session. The following is a good way to get that information when needed. This can also be useful for debugging scripts that you are in the process of building out.		Assuming you have done something like foo="bar" at your bash prompt it is not always clear how to echo ALL the defined variables back from your bash session. The following is a good way to get that information when needed. This can also be useful for debugging scripts that you are in the process of building out.

Chubbard: /* Bash builtins */

2023-10-07T03:38:42Z

Bash builtins

← Older revision		Revision as of 20:38, 6 October 2023
Line 36:		Line 36:
	man bash \| awk '/ Shell Variables/,/ Arrays/' \| more		man bash \| awk '/ Shell Variables/,/ Arrays/' \| more
	</pre>		</pre>
			== Bash history ==
			Looks like it can reside in different dot files. For Ubuntu it is in ~/.bashrc
			<pre>
			HISTSIZE=2000
			HISTFILESIZE=4000
			</pre>

	[[Category:Bash]]		[[Category:Bash]]

Chubbard: /* Convert upper to lower case in various ways */

2023-09-27T22:37:22Z

Convert upper to lower case in various ways

@@ Line 30: / Line 30: @@
 foobar
 </pre>
 [[Category:Bash]]

Chubbard at 02:00, 29 October 2022

2022-10-29T02:00:05Z

@@ Line 15: / Line 15: @@
 compgen -v | while read line; do echo $line=${!line};done
 </pre>
+<pre>
 [[Category:Bash]]

Chubbard: /* Finding defined variables */

2022-10-26T19:29:25Z

Finding defined variables

← Older revision		Revision as of 12:29, 26 October 2022
Line 11:		Line 11:
	</pre>		</pre>

	An alternate command that will also give nice and parsable results		An alternate command that will also give nice and parsable results. This is quite nice, as the loop itself will pull the values that compgen -v gave as just var names.
	<pre>		<pre>
	compgen -v \| while read line; do echo $line=${!line};done		compgen -v \| while read line; do echo $line=${!line};done

Chubbard at 19:27, 26 October 2022

2022-10-26T19:27:54Z

← Older revision		Revision as of 12:27, 26 October 2022
Line 10:		Line 10:
	declare -xp		declare -xp
	</pre>		</pre>

			An alternate command that will also give nice and parsable results
			<pre>
			compgen -v \| while read line; do echo $line=${!line};done
			</pre>


	[[Category:Bash]]		[[Category:Bash]]

Chubbard: Created page with "== Finding defined variables == Assuming you have done something like foo="bar" at your bash prompt it is not always clear how to echo ALL the defined variables back from your..."

2022-10-26T19:26:13Z

Created page with "== Finding defined variables == Assuming you have done something like foo="bar" at your bash prompt it is not always clear how to echo ALL the defined variables back from your..."

New page

== Finding defined variables ==
Assuming you have done something like foo="bar" at your bash prompt it is not always clear how to echo ALL the defined variables back from your bash session. The following is a good way to get that information when needed. This can also be useful for debugging scripts that you are in the process of building out.

<pre>
declare -p
</pre>

If you only want the environment variables, and do not want to use env for some reason
<pre>
declare -xp
</pre>

[[Category:Bash]]