For the character $ is treated specially between a pair of double quotes.
echo "$PATH"
If I really want to print $, I need to say
echo "\$PATH"
Could anybody let me know the complete set of characters that need to
be escaped (prepend with backslash) between a pair of double quotes if
I really w
> Could anybody let me know the complete set of characters that need to
> be escaped (prepend with backslash) between a pair of double quotes if
> I really want to print the character?
RTFM. In particular, the manual page ("man bash") has a succinct section
entitled "QUOTING".
--
Hi,
I think that that may not be a unique naming convention for bash
script filenames. But I use the following.
For an executable bash script I use the suffix .sh. For a bash script
that is only source-able but runnable, I use the suffix .bashrc.
People may use different conventions. I just want
Peng Yu wrote:
> For an executable bash script I use the suffix .sh. For a bash script
> that is only source-able but runnable, I use the suffix .bashrc.
>
> People may use different conventions. I just want to see what most
> people use and follow the common practice. Could anybody give me any
>
On Sun, 11 Jul 2010, Peng Yu wrote:
> Hi,
>
> I think that that may not be a unique naming convention for bash
> script filenames. But I use the following.
>
> For an executable bash script I use the suffix .sh. For a bash script
> that is only source-able but runnable, I use the suffix .bashrc.