Yup. One good SNAFU deserves another...
Since programming is a practice well served by the persnickety, I'll make one final revision:
echo "$0" "$@" |at now + 18 hours
--Danny, who also dislikes here documents, in general
Here documents are cool, but they make scripts harder to read and understand, so I avoid using them unless they're really necessary.
When they're cool, I like them too. In general, they're not cool, though, since I use perl more than shells for scripting, and it's easier to just leave a pair of quotes open for multi-line strings in most cases. ;)
I'm not sure about all shells, but BASH allows multi-line, unescaped strings on the command line and in scripts. I also find BASH's $'C-style escape codes expanded in this kind of string' feature very handy. It's described in the "QUOTING" section of the BASH manual page.
--Danny
Randall Schulz I was wondering about using cron, but thought that it was limited to the time
On Wednesday 04 August 2004 15:41, Randall R Schulz wrote: <SNIP> frames within kcron, since I had trouble trying something even more simple w/ vcron (as in, something more simple wouldn't execute). If I put it directly in crontab, wouldn't the [* /1080 * * *] work? Perhaps I should just do the task manually (if I don't forget) if it is that complicated...? -- ...CH "The more they over-think the plumbing, the easier it is to stop up the drain." Scotty