< ^ txt
Tue Nov 29 09:28:26 EST 2016
Slept from ten-thirty to seven-thirty. Woke briefly around four-thirty.
Partly sunny today, with a high of fifty-nine.
Work:
- Decide what to do before end of year
Done.
Paul:
- Finish centralized logging
- Work on watchdog for maintenance call system (new sub-project, but part of emergency maintenance calling)
- Maybe rough-out asset tracking system
Scott:
- Finish public web site
- Finish virtualizing door entry system
Forty-five minute walk at lunch. Pleasant. Saw a robin and half a dozen seagulls. Also, found a few dandelions in full bloom.
http://www.naturenorth.com/summer/dandelion/Dandelion2.html
> Dandelions tend to flower most abundantly in spring, but can re-flower in the fall, too.
They're also a source of natural rubber/latex. Huh.
https://en.wikipedia.org/wiki/Taraxacum#As_source_of_natural_rubber
http://php.net/manual/en/pdo.prepared-statements.php
http://dev.mysql.com/doc/refman/5.7/en/sql-syntax-prepared-statements.html
http://dev.mysql.com/doc/refman/5.7/en/prepare.html
http://www.tldp.org/LDP/abs/html/quotingvar.html
--- falstaff !2555 ~ % dash
$ echo '\\\\'
\\
$ echo "\\\\"
\
$ /bin/echo '\\\\'
\\\\
$ /bin/echo "\\\\"
\\
$ x='\\\\'
$ echo $x
\\
$ echo "$x"
\\
$ /bin/echo $x
\\\\
$ x="\\\\"
$ echo $x
\
$ echo "$x"
\
$ /bin/echo $x
\\
Tricky. It appears that the shell interprets the string on input _and_ output. Nothing gets interpreted in single quoted input. But for output, the behavior differs depending on whether we echo using the shell built-in or `/bin/echo`.
To be safe, I think we would need to get input with single quotes to a variable, and do output with the quoted variable, like:
$ x='Don'\''t be unsafe!'
$ echo "$x"
Don't be unsafe!
Home:
- Grocery or laundry
Both done! Two loads of laundry even!
- Take a long walk
Done.
I put up a couple of strands of Christmas lights.
Breakfast: carrots, spinach, a spoonful of yogurt, coffee with half-and-half
Lunch: nuts
Dinner: toquitos
< ^ txt