<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 15, 2015 at 10:22 AM, <span dir="ltr"><<a href="mailto:jep200404@columbus.rr.com" target="_blank">jep200404@columbus.rr.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">There is no difference in this case<br>
with the bash shell that I'm using.<br></blockquote><div><br></div><div>The "with the ... shell that I'm using" is the best reason for (and why I concur with):</div><div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> I usually enclose my regular expression for grep<br>
and commands for sed with single quotes, not double quotes.<br></blockquote><div> </div><div><br></div><div>Long ago, it got burned into my brain that "sed programs passed via the command line must be surrounded by single-quotes" so (even though it's not strictly true) I just do it and don't think about it (unless, of course, I need to do some variable substitution with the shell to modify the sed command).</div><div><br></div><div>With all of the extensions/hacks and varieties of shells and environment modifications and command-line editors (and not remembering which obscure meta-characters are active in each possible scenario and not knowing what the next person maintaining your script might change in the search/sed string), being more conservative about (or should I say "liberal with" ?) quoting will save you mental cycles of trying to figure out whether or not to actually quote and/or why the command didn't do what you expected without quotes. <br></div><div><br></div><div>Jeff</div><div><br></div></div></div></div>