zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Weird history behavior
Date: Wed, 8 Jun 2022 10:03:16 -0700	[thread overview]
Message-ID: <CAH+w=7a5kG=_dUY4SGbY7TpbK=uAOd-T870+uzOGLx7Mq=yu4w@mail.gmail.com> (raw)
In-Reply-To: <20220608165528.suhoqmhgo3qbkhq7@marcos.localdomain>

On Wed, Jun 8, 2022 at 9:55 AM Adam Cooper <adam@theadamcooper.com> wrote:
>
> My reading of the docs tells me that (in the absence of /etc/zsh/zshenv) ~/.zshenv is read first, and if ZDOTDIR is set there, the remaining configuration files will be read from ZDOTDIR.

That's correct under the assumption that ZDOTDIR is not already
exported into the environment, but if you export it, then everything
is read from there by child shells, including $ZDOTDIR/.zshenv

> (Moving .zshenv into ZDOTDIR resulted in zsh displaying a menu with options for configuring zsh from the start.)

That's because zsh-newuser-install is looking for some comment lines
in $ZDOTDIR/.zshrc

> Evidence-wise, when I first log in to tty1, HISTFILE is set, as is HISTSIZE (conspicuously set to 9998), so I conclude .zshenv is being read. When I then run startx to enter xmonad, HISTFILE is unset, while HISTSIZE remains set. The only other configuration file, ZDOTDIR/.zshrc, is read correctly.

This sounds like either xmonad is removing HISTFILE from the
environment, or some /etc init file is doing so, and it's not put back
because $HOME/.zshenv is skipped in favor of $ZDOTDIR/.zshenv


  parent reply	other threads:[~2022-06-08 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 19:23 Adam Cooper
2022-06-08  5:02 ` Bart Schaefer
2022-06-08 16:55   ` Adam Cooper
2022-06-08 16:58     ` Roman Perepelitsa
2022-06-08 17:03     ` Bart Schaefer [this message]
2022-06-08 17:07     ` Bart Schaefer

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='CAH+w=7a5kG=_dUY4SGbY7TpbK=uAOd-T870+uzOGLx7Mq=yu4w@mail.gmail.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).