From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28850 invoked by alias); 29 Apr 2011 03:31:48 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 29106 Received: (qmail 14830 invoked from network); 29 Apr 2011 03:31:45 -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,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <110428203139.ZM11856@torch.brasslantern.com> Date: Thu, 28 Apr 2011 20:31:39 -0700 In-reply-to: Comments: In reply to Felipe Contreras "Re: zle messes up 'words' variable?" (Apr 28, 11:19pm) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Felipe Contreras , zsh-workers@zsh.org Subject: Re: zle messes up 'words' variable? MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Apr 28, 11:19pm, Felipe Contreras wrote: } } I saw the following reply online but I wasn't CC'ed: I typically don't Cc on mail to the list unless the sender specifically asks for that. If you asked and I missed it, I apologize. } > What may be happening is that "sticky emulation" is in effect, so } > that when the function is autoloaded in bash compatibility mode, } > "words" becomes non-special. If so, I'm not familiar enough with } > bashcompinit to say whether that's intentional or an accidental } > side-effect. } } This has nothing to do with bashcompinit, the issue is with plain } compinit. Your example in workers/29086 explicitly loads and runs bashcompinit. What am I missing? } BTW. This messes up with a very important function in bash completion: } _get_comp_words_by_ref() I'm now entirely confused. I no longer believe that I know what you mean by "in bash completion." There's no shell function _get_comp_words_by_ref anywhere in the zsh sources. Where is that coming from? If what you're doing is loading functions into zsh that were written to be used with bash's compgen, then I don't follow how you can NOT be using bashcompinit. Either way I have no better explanation for why #compdef and directly calling compdef would behave differently, but I don't see any uses of "emulate sh -c" in bashcompinit so that's probably not right.