help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: key binding not working [SOLVED]
Date: Mon, 26 Sep 2022 06:59:42 -0700	[thread overview]
Message-ID: <727dcb31-3ead-03fb-db9b-e0b8e7c59a00@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMq3g1ZAtOphQk+bch_U=DmvJ1YLyO2oSugrkFkJkY409w@mail.gmail.com>

On 2022-09-25 23:28, Roman Perepelitsa wrote:
> If the non-Debian version is https://github.com/romkatv/zsh-bin, then
> you need to keep in mind that it does not read global rc files. This
> is a statically built binary, so it has no way of knowing where global
> rc files are.
Didn't know, but I'm glad to hear it,  I want all my config to start 
from a single script that I know about (/root/.zshrc in this case which 
your version does seem to find) but don't go sourcing this and that 
without asking.  Yes, when I first got involved the remember hunting 
down all the little things that zsh might go looking for and I killed 
them all -- after moving whatever functionality into *my* config path.

>      zsh --sourcetrace -lis <<<exit
Fabulous, that's just what one wants to figure this kind of thing out.

> If you run that on Debian with the system zsh, you'll see among other
> things /etc/zsh/zshrc. If you look inside, you'll find awful things.
Yep.  I renamed that directory and now the Debian zsh configs itself 
properly and the up arrow is fine.  So now I'll look into those files 
and see what Debian thinks is good for me.

> Some of them you can disable by defining special parameters in

The rest is way over my head but I'll save it play with it.  For now the 
/etc/zsh files are on ice and so far so good.

Thanks Roman, solved.

Hey, supposing we concluded solved threads with some indication, like 
I'm experimenting with in my subject line?

  reply	other threads:[~2022-09-26 14:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 21:14 key binding not working Ray Andrews
2022-09-25 22:31 ` Bart Schaefer
2022-09-25 22:46   ` Ray Andrews
2022-09-25 23:14     ` Ray Andrews
2022-09-26  3:48     ` Marc Chantreux
2022-09-27  0:30     ` zkbd (was Re: key binding not working) Bart Schaefer
2022-09-27  1:39       ` Ray Andrews
2022-09-26  1:16   ` key binding not working Ray Andrews
2022-09-26  1:58     ` Lawrence Velázquez
2022-09-26  3:15       ` Ray Andrews
2022-09-26  4:01         ` Lawrence Velázquez
2022-09-26  6:28     ` Roman Perepelitsa
2022-09-26 13:59       ` Ray Andrews [this message]
2022-09-26 18:04         ` key binding not working [SOLVED] Ray Andrews
2022-09-26 18:13           ` Roman Perepelitsa
2022-09-26 19:12             ` Peter Stephenson
2022-09-26 19:43               ` Mikael Magnusson
2022-09-26 21:31             ` Ray Andrews
2022-09-26 22:27               ` Vin Shelton
2022-09-26 22:35                 ` Ray Andrews

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=727dcb31-3ead-03fb-db9b-e0b8e7c59a00@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \


* 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


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).