The ‘eval’ command in Bash and its typical uses

by

eval takes a string as its argument, and evaluates it as if you’d typed that string on a command line. (If you pass several arguments, they are first joined with spaces between them.)

${$n} is a syntax error in bash. Inside the braces, you can only have a variable name, with some possible prefix and suffixes, but you can’t have arbitrary bash syntax and in particular you can’t use variable expansion. There is a way of saying “the value of the variable whose name is in this variable”, though:

echo ${!n}
one

$(…) runs the command specified inside the parentheses in a subshell (i.e. in a separate process that inherits all settings such as variable values from the current shell), and gathers its output. So echo $($n) runs $n as a shell command, and displays its output. Since $n evaluates to 1, $($n) attempts to run the command 1, which does not exist.

eval echo \${$n} runs the parameters passed to eval. After expansion, the parameters are echo and ${1}. So eval echo \${$n} runs the command echo ${1}.

Note that most of the time, you must use double quotes around variable substitutions and command substitutions (i.e. anytime there’s a $): "$foo", "$(foo)". Always put double quotes around variable and command substitutions, unless you know you need to leave them off. Without the double quotes, the shell performs field splitting (i.e. it splits value of the variable or the output from the command into separate words) and then treats each word as a wildcard pattern. For example:

$ ls
file1 file2 otherfile
$ set -- 'f* *'
$ echo "$1"
f* *
$ echo $1
file1 file2 file1 file2 otherfile
$ n=1
$ eval echo \${$n}
file1 file2 file1 file2 otherfile
$eval echo \"\${$n}\"
f* *
$ echo "${!n}"
f* *

eval is not used very often. In some shells, the most common use is to obtain the value of a variable whose name is not known until runtime. In bash, this is not necessary thanks to the ${!VAR} syntax. eval is still useful when you need to construct a longer command containing operators, reserved words, etc.

More Related Contents:

  1. How do I prompt for Yes/No/Cancel input in a Linux shell script?
  2. How do I know the script file name in a Bash script?
  3. Raise error in a Bash script
  4. Find multiple files and rename them in Linux
  5. Bash Script – iterating over output of find
  6. How do I remove newlines from a text file?
  7. Counter increment in Bash loop not working
  8. How to convert hex to ASCII characters in the Linux shell?
  9. sh: 1: Syntax error: "(" unexpected error
  10. How do I write a bash script to restart a process if it dies?
  11. Iterate over a list of files with spaces
  12. How to declare 2D array in bash
  13. Defining a variable with or without export
  14. What does $@ mean in a shell script?
  15. Better way to rename files based on multiple patterns
  16. How to join multiple lines of file names into one with custom delimiter?
  17. Syntax error in shell script with process substitution
  18. What is the difference between “#!/usr/bin/env bash” and “#!/usr/bin/bash”?
  19. Shell/Bash shortcut for bulk renaming of files in a folder
  20. How to preserve line breaks when storing command output to a variable?
  21. How to use sed to remove the last n lines of a file
  22. Passing variables in remote ssh command
  23. How do I run multiple background commands in bash in a single line?
  24. How do I change bash history completion to complete what’s already on the line?
  25. Multithreading in Bash [duplicate]
  26. Difference between shell and environment variables
  27. SUID not working with shell script
  28. What’s the point of eval/bash -c as opposed to just evaluating a variable?
  29. Write a bash shell script that consumes a constant amount of RAM for a user defined time [closed]
  30. How to create a dynamic variable and assign value to it?

Leave a Comment