From: DervishD <zsh@dervishd.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@sunsite.dk>
Subject: Re: Why this expansion doesn't work?
Date: Sun, 13 Mar 2005 10:39:15 +0100 [thread overview]
Message-ID: <20050313093915.GA81@DervishD> (raw)
In-Reply-To: <1050312204940.ZM12046@candle.brasslantern.com>
Hi Bart :)
* Bart Schaefer <schaefer@brasslantern.com> dixit:
> On Mar 12, 11:14am, DervishD wrote:
> } Subject: Why this doesn't work?
> As long as I'm passing out netiquette lessons, I might as well say
> that it would be nice if the word "this" in that Subject had been
> replaced by a slightly more descriptive phrase.
Yes, you're right, but I couldn't think of a more apropriate
subject at the time, sorry O:)) Next time I'll use a better and more
descriptive subject.
> } $ eval printf -- "Hello\\n"
> } Hello$
> If this is really what you're seeing, then something is indeed wrong.
> What you should see is "Hellon", not "Hello".
That's weird :(( I still have open the console where I saw that,
but in a new virtual console that doesn't happen and yes, I see
'Hellon' and not 'Hello'. I don't know why, because the options are
the same in both terminals (I've double checked that) :???
On every new terminal I see 'Hellon'.
> } $ eval printf -- "Hello\\\n"
> } Hello<newline>
> } I mean, no newline character is output when using just two
> } backslashes, and I don't understand that.
> Remember that when you use "eval" the command line is actually parsed
> twice. So
> eval printf -- "Hello\\n"
> is equivalent to
> printf -- Hello\n
>
> The first parse removes the quotes and one of the backslashes, and the
> second parse removes the remaining backslash.
So I must use something like:
eval printf -- \"Hello\\n\"
I forgot that the double quotes were removed :((( Is there any
way of seeing how a command line is parsed *just before* being
executed by the shell? That would avoid the stupidity from the user
(that is, me) you can see above O:) I've tried the eval command with
the double quotes quoted and works perfectly ;)
Thanks a lot for answering, Bart, and my excuses for the poor
subject O:)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.dervishd.net & http://www.pleyades.net/
It's my PC and I'll cry if I want to...
next prev parent reply other threads:[~2005-03-13 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 10:14 Why this " DervishD
2005-03-12 20:49 ` Bart Schaefer
2005-03-13 9:39 ` DervishD [this message]
2005-03-13 17:16 ` Why this expansion " Bart Schaefer
2005-03-14 10:50 ` DervishD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050313093915.GA81@DervishD \
--to=zsh@dervishd.net \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).