Date: Thu, 29 May 2014 12:50:16 -0400 From: Andre Goree <andre@drenet.net> To: Polytropon <freebsd@edvax.de> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: csh and echo Message-ID: <e5e9cb6fd51af69e07500d12bc81668a@drenet.net> In-Reply-To: <20140529183942.7119a5e6.freebsd@edvax.de> References: <6afd2e37bfc1736513878d896c5c8314@drenet.net> <20140529183942.7119a5e6.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Try with single quotes: > > # echo '$1$rVxldcGZ$CisrIAX4SBYUkMJt9KjXl0' > $1$rVxldcGZ$CisrIAX4SBYUkMJt9KjXl0 > > > ( Sorry for the damaged 2nd mail, in case it got through ) > > Michael Thanks! > > The csh does exactly what it should to. Use '...' instead of "..." > to avoid evaluations within a string, for example: > > % echo '$1$rVxldcGZ$CisrIAX4SBYUkMJt9KjXl0' > $1$rVxldcGZ$CisrIAX4SBYUkMJt9KjXl0 > > It's not an issue, it's intended. Strings enclosed in "..." are > allowed to contain variables, whereas strings enclosed in '...' > are being processed without expansion. > > $ echo '$1$rVxldcGZ$CisrIAX4SBYUkMJt9KjXl0' > $1$rVxldcGZ$CisrIAX4SBYUkMJt9KjXl0 > > I'm sure this is mentioned somewhere in "man bash", as well as > in "man csh" regarding the C Shell. :-) You're absolutely correct, complete derp moment on my part. I knew it would be something so easy, my brain's been fried lately, lol. Thanks! -- Andre Goree -=-=-=-=-=- Email - andre at drenet.net Website - http://www.drenet.net PGP key - http://www.drenet.net/pubkey.txt -=-=-=-=-=-
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e5e9cb6fd51af69e07500d12bc81668a>