From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4436 invoked by alias); 4 Jun 2010 19:56:34 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 15086 Received: (qmail 6214 invoked from network); 4 Jun 2010 19:56:23 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 Received-SPF: pass (ns1.primenet.com.au: SPF record at benizi.com designates 64.130.10.15 as permitted sender) Date: Fri, 4 Jun 2010 15:49:49 -0400 (EDT) From: "Benjamin R. Haskell" To: Zsh Users Subject: Caveats of setopt magic_equal_subst Message-ID: User-Agent: Alpine 2.01 (LNX 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII As with so many things Zsh-related, I just discovered that something I'd kind of wanted for a while was a built-in option: magic_equal_subst I was just wondering if there were commonly-occurring situations where magic_equal_subst might bite me. It seems like the benefits will outweigh having to workaround such situations, but I was just hoping to get a group opinion or warning if I'm being optimistic. My main reason for switching it on is that I use a lot of named directories, and I'd like to be able to use them where command options are of the form --some-option=~some/filename -- Best, Ben