From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21716 invoked by alias); 7 Jun 2014 21:02:08 -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: 18882 Received: (qmail 20383 invoked from network); 7 Jun 2014 21:02:06 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) 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.2 From: Bart Schaefer Message-id: <140607140205.ZM26027@torch.brasslantern.com> Date: Sat, 07 Jun 2014 14:02:05 -0700 In-reply-to: <35EC1DF1-5D60-42CA-93FB-A6400E4308CF@laposte.net> Comments: In reply to "nicolas.canceill" "Re: Case-insensitive completion with partial substring matching" (Jun 7, 10:39pm) References: <33086926-C7D7-4D33-AF86-4B0D48977555@laposte.net> <140607105445.ZM24783@torch.brasslantern.com> <140607123006.ZM25086@torch.brasslantern.com> <35EC1DF1-5D60-42CA-93FB-A6400E4308CF@laposte.net> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: Case-insensitive completion with partial substring matching MIME-version: 1.0 Content-type: text/plain; charset=us-ascii This is rapidly approaching a zsh-workers discussion rather than -users. On Jun 7, 10:39pm, nicolas.canceill wrote: } Subject: Re: Case-insensitive completion with partial substring matching } } In order to look into the code, I want to log a bunch of stuff (my } favorite way). The debug flags I see mentioned in the INSTALL file do } not seem relevant. Do you know what the best way to log stuff from } within the functions would be? I'm not sure what you're asking about there. Logging stuff from within the C functions isn't really automated in any way. Logging stuff from the shell functions that make up completion can be done, but it's not of much use in this case (I already examined that). You want to configure --with-zsh-debug --disable-dynamic for pursposes of using e.g. gdb, but the built-in debugging messages mostly take the form of assertions that only produce output if an anticipated condition turns out to be false, but that doesn't really apply. So you're pretty much on your own, I guess.