From: Florian CROUZAT <gentoo@floriancrouzat.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] why emerge --config don't work
Date: Fri, 20 Aug 2010 16:57:33 +0200 [thread overview]
Message-ID: <0716FF31-3460-49C1-8588-AB70DF1A75F6@floriancrouzat.net> (raw)
In-Reply-To: <201008201650.24528.wonko@wonkology.org>
On 20 août 2010, at 16:50, Alex Schuster wrote:
> weird% echo =find
> /usr/bin/find
>
> Your command works, when the = is escaped by a \, or when the stuff is
> quoted.
I don't use zsh, but a little of google's magic[1] shows:
> A command name with a = prepended is replaced with its full pathname. This can be very convenient. If it's not convenient for you, you can turn it off:
>
> % ls
> =foo =bar
> % ls =foo =bar
> zsh: foo not found
> % setopt noequals
> % ls =foo =bar
> =foo =bar
[1] http://zsh.sourceforge.net/Intro/intro_7.html
-----
Florian.
/ For security reasons, all text in this mail
is double-rot13 encrypted. /
next prev parent reply other threads:[~2010-08-20 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 12:56 [gentoo-user] why emerge --config don't work Zhu Sha Zang
2010-08-20 14:50 ` Alex Schuster
2010-08-20 14:57 ` Florian CROUZAT [this message]
2010-08-20 21:39 ` Volker Armin Hemmann
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=0716FF31-3460-49C1-8588-AB70DF1A75F6@floriancrouzat.net \
--to=gentoo@floriancrouzat.net \
--cc=gentoo-user@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox