zsh-users
 help / color / mirror / code / Atom feed
From: Perry Smith <pedz@easesoftware.com>
To: zsh-users@zsh.org
Subject: Trying to learn ... RCS and GLOBAL_RCS
Date: Sat, 26 Mar 2022 08:53:19 -0500	[thread overview]
Message-ID: <19A56C62-2136-410B-BFD7-A5E8E4BFE7D6@easesoftware.com> (raw)

I won’t paste the whole text here but I’m looking at the STARTUP/SHUTDOWN FILES section in zsh(1) / zshall(1) and the documentation isn’t matching what I’m seeing.  Do I need more coffee???

The man page says:

> "Both RCS and GLOBAL_RCS are set by default.”.  

Yet when I do “unsetopt” at the very top of my /etc/zshenv file, it says:

> noglobalrcs
> norcs

But I know all of my RC files and global RC files are being read — via a “trace” function I cobbled together.

I started using ZSH when Apple switched to it and I tried to read and study and learn.  This past week, I was trying to use a BSD system and my history wasn’t being saved.  Turns out Apple hid  setting of the various history zsh variables that in their /etc/zshrc and /etc/zshrc_Apple_Terminal so I never added it to my start up files.  That caused me to start digging more to fully understand things and that’s when I came up with these questions.

It is the same with logout.  On Apple (and I assume on BSD once I get the other options and variables set properly), history is being saved yet the man page says:

> "Note also that the RCS option affects the saving of history files, i.e. if RCS is unset when the shell exits, no history file will be saved.”

These are the 5.8 and 5.8.1 man pages.



             reply	other threads:[~2022-03-26 13:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26 13:53 Perry Smith [this message]
2022-03-26 16:39 ` Bart Schaefer
2022-03-26 16:44   ` Perry Smith
2022-03-26 16:48     ` Bart Schaefer
2022-03-26 17:04       ` Perry Smith
2022-03-26 17:39         ` Mikael Magnusson
2022-03-26 17:05     ` Bart Schaefer
2022-03-26 17:18       ` Perry Smith

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=19A56C62-2136-410B-BFD7-A5E8E4BFE7D6@easesoftware.com \
    --to=pedz@easesoftware.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).