Return to Answer

There are numerous ways to do that, including the following:

sed -e '/^[:space:]*$/d' -e 's/$/.txt/' fileNames.txt | xargs -d '\n' touch

This assumes that there is only one filename per line in fileNames.txt. The sed script deletes blank lines (thanks to @rubynorails) and adds '.txt' to the end of each filename before piping them to xargs touch.

By using the -d '\n' option with xargs (which tells xargs to use only newline or '\n' as the delimiter rather than any whitespace) this even copes with filenames that have spaces and other potentially-problematic characters (except for \n or newline itself). e.g. if a line contained 'abet able', without -d '\n', two files (abet and able.txt) would be created. With it, only one file abet able.txt will be created.

There are numerous ways to do that, including the following (assuming GNU xargs):

sed -e '/^[[:space:]]*$/d' -e 's/$/.txt/' fileNames.txt | xargs -rd '\n' touch --

This assumes that there is only one filename per line in fileNames.txt. The sed script deletes blank lines (thanks to @rubynorails) and adds '.txt' to the end of each filename before piping them to xargs touch.

By using the -d '\n' option with xargs (a GNU extension, which tells xargs to use only newline or '\n' as the delimiter rather than any whitespace, and disables quote processing) this even copes with filenames that have spaces and other potentially-problematic characters (except for \n or newline itself). e.g. if a line contained 'abet able', without -d '\n', two files (abet and able.txt) would be created. With it, only one file abet able.txt will be created.

There are numerous ways to do that, including the following:

sed -e 's/$/.txt/' fileNames.txt | xargs -d '\n' touch

This assumes that there is only one filename per line in fileNames.txt. The sed script adds '.txt' to the end of each filename before piping them to xargs touch.

By using the -d '\n' option with xargs (which tells xargs to use only newline or '\n' as the delimiter rather than any whitespace) this even copes with filenames that have spaces and other potentially-problematic characters (except for \n or newline itself). e.g. if a line contained 'abet able', without -d '\n', two files (abet and able.txt) would be created. With it, only one file abet able.txt will be created.

There are numerous ways to do that, including the following:

sed -e '/^[:space:]*$/d' -e 's/$/.txt/' fileNames.txt | xargs -d '\n' touch

This assumes that there is only one filename per line in fileNames.txt. The sed script deletes blank lines (thanks to @rubynorails) and adds '.txt' to the end of each filename before piping them to xargs touch.

By using the -d '\n' option with xargs (which tells xargs to use only newline or '\n' as the delimiter rather than any whitespace) this even copes with filenames that have spaces and other potentially-problematic characters (except for \n or newline itself). e.g. if a line contained 'abet able', without -d '\n', two files (abet and able.txt) would be created. With it, only one file abet able.txt will be created.

There are numerous ways to do that, including the following:

sed -e 's/$/.txt/' fileNames.txt | xargs -d '\n' touch

This assumes that there is only one filename per line in fileNames.txt. The sed script adds '.txt' to the end of each filename before piping them to xargs touch.

By using the -d '\n' option with xargs (which tells xargs to use only newline or '\n' as the delimiter rather than any whitespace) this even copes with filenames that have spaces and other potentially-problematic characters (except for \n or newline itself). e.g. if a line contained 'abet able', without -d '\n', two files (abet.txt and able.txt) would be created. With it, only one file abet able.txt will be created.

There are numerous ways to do that, including the following:

sed -e 's/$/.txt/' fileNames.txt | xargs -d '\n' touch

This assumes that there is only one filename per line in fileNames.txt. The sed script adds '.txt' to the end of each filename before piping them to xargs touch.

By using the -d '\n' option with xargs (which tells xargs to use only newline or '\n' as the delimiter rather than any whitespace) this even copes with filenames that have spaces and other potentially-problematic characters (except for \n or newline itself). e.g. if a line contained 'abet able', without -d '\n', two files (abet and able.txt) would be created. With it, only one file abet able.txt will be created.