Comments on: Link collection 2009/03

By: sven

sven — Tue, 31 Mar 2009 19:53:44 +0000

Yep, indentation was eaten. Anyway, your approach works fine as long as you have control over how the commandline arguments are processed. But at times you just want to leave the pre-existing commandline parsing alone or even use some sort of library function for this. In that case, your approach won’t work. But it is a really nice idea for own scripts that are fully under ones control. Thanks for sharing the idea.

By: Patrick

Patrick — Tue, 31 Mar 2009 19:33:50 +0000

Hi,
the link to the lost+found article is broken. It also points to Seans blog entry.
Regards,
Patrick

By: Anonymous

Anonymous — Tue, 31 Mar 2009 16:16:49 +0000

OK, the indentation got eaten, but otherwise that came through fine. Anyway, the above approach works with any whitespace or strange symbols you want to put into the parameters, without having to escape them.

By: Anonymous

Anonymous — Tue, 31 Mar 2009 16:13:48 +0000

Regarding the approach to saving and restoring parameters, a much easier solution (which hopefully won’t get mangled in this comment):

echo Original $# arguments: “$@”

echo Processing arguments one at a time…
n=$#
set “$@” “$@”
while [ "$#" -gt "$n" ]; do
echo Processing argument “$1″
shift
done

echo Back to the original $# arguments: “$@”

By: Cuetzpallin

Cuetzpallin — Tue, 31 Mar 2009 15:05:39 +0000

Nice and useful links, thanks for your share