From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Completion for cd
Date: Tue, 14 Mar 2017 12:07:15 -0700 [thread overview]
Message-ID: <170314120715.ZM10347@torch.brasslantern.com> (raw)
In-Reply-To: <CABZhJg_McyYz8f_xyVN8c8g4xop+6J_EWj2=CUS3uu9A0SZPNA@mail.gmail.com>
On Mar 14, 6:38pm, Jesper Nygards wrote:
}
} I can't figure out why my configuration change has caused the
} 'ignore-parents' style to stop working.
I tried trivially to reproduce this in the current master from git,
by copy-pasting your example configuration (with suitable adjustment
to cdpath); ignore-parents seemed to be working for me.
The _complete_debug facility is provided to help with tracking down
this sort of thing. A typical process I would follow is:
1. Restore the original configuration where ignore-parents works
and start a new shell.
2. Do a sample completion where ignore-parents should be applied,
but instead of using TAB to complete, use ctrl-x question-mark
which invokes _complete_debug. Note the file name where it
says it stored the trace output (you may have to up-history to
see it).
3. Add your new tag-order configurations and start another new shell.
4. Repeat the same completion with _complete_debug and note the file
name again (it should be similar to the last one, except with the
PID of the new shell).
5. Invoke a side-by-side diff tool such as meld, or ediff (emacs),
etc., and compare the two files. This should give you some clues
about where the completion is going wrong.
The most likely explanation is that the local-directories tag-order
is causing the completion with ignore-parents to find nothing, so
the default is to show the result without ignore-parents ... but
why that happens for you and not when I try to reproduce may be
the detail that comparing debug traces reveals.
next prev parent reply other threads:[~2017-03-14 19:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 17:38 Jesper Nygårds
2017-03-14 19:07 ` Bart Schaefer [this message]
2017-03-14 21:50 ` Jesper Nygårds
2017-03-15 3:56 ` Bart Schaefer
2017-03-15 7:22 ` Jesper Nygårds
2017-03-15 17:00 ` Bart Schaefer
2017-03-15 20:33 ` Jesper Nygårds
-- strict thread matches above, loose matches on Subject: below --
2004-03-28 10:42 Thorsten Haude
2004-03-28 12:03 ` Thorsten Kampe
2004-03-28 20:34 ` Thorsten Haude
2004-03-30 1:15 ` Thorsten Kampe
2004-03-31 20:19 ` Thorsten Haude
2004-04-01 18:04 ` Bart Schaefer
2004-04-01 20:44 ` Thorsten Haude
2004-04-02 4:38 ` Bart Schaefer
2004-04-02 6:52 ` Thorsten Haude
2004-04-02 16:11 ` Bart Schaefer
2004-04-04 14:43 ` Thorsten Haude
2004-04-04 15:14 ` Clint Adams
2004-04-04 15:26 ` Thorsten Haude
2004-04-04 16:39 ` Clint Adams
2004-04-05 0:04 ` Bart Schaefer
2004-04-05 3:50 ` Clint Adams
2004-03-28 19:56 ` Bart Schaefer
2004-03-31 20:22 ` Thorsten Haude
2004-04-01 18:24 ` Bart Schaefer
2004-04-01 20:52 ` Thorsten Haude
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=170314120715.ZM10347@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@zsh.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.
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).