Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: I shot the zsheriff, but I do not shout the debuty
- X-seq: zsh-users 9096
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: I shot the zsheriff, but I do not shout the debuty
- Date: Wed, 13 Jul 2005 08:05:17 +0000
- In-reply-to: <20050713.054913.41194296.Meino.Cramer@xxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <1050712002437.ZM25819@xxxxxxxxxxxxxxxxxxxxxxx> <20050712.203614.74755196.Meino.Cramer@xxxxxx> <1050712235359.ZM26835@xxxxxxxxxxxxxxxxxxxxxxx> <20050713.054913.41194296.Meino.Cramer@xxxxxx>
On Jul 13, 5:49am, Meino Christian Cramer wrote:
}
} > grep -ie 'compdef.*\^k' $^fpath/*(.N)
}
}
} What is purpose of these lines like that above? What should they find
} (or not...)? What would be exspected to see on a sane installation of
} zsh?
What would be expected (in that specific example) is exactly what you
saw, which is nothing.
The #compdef line on a file read by compinit is a potential source of
a redefinition of key bindings. Since you don't think there's a
bindkey for ^k anywhere else, searching for a compdef line that was
causing it was the next obvious possibility.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author