Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: can't write zsh_history
- X-seq: zsh-users 10869
- From: Phil Pennock <phil.pennock@xxxxxxxxxxx>
- To: William Scott <wgscott@xxxxxxxxxxxxxxxxxx>
- Subject: Re: can't write zsh_history
- Date: Sat, 14 Oct 2006 03:49:09 +0200
- Cc: zsh-users@xxxxxxxxxx
- In-reply-to: <Pine.OSX.4.61.0610130720390.16279@xxxxxxxxxxxxxxx>
- Mail-followup-to: William Scott <wgscott@xxxxxxxxxxxxxxxxxx>, zsh-users@xxxxxxxxxx
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <76C42610-83A0-4174-ADBF-5CD4D75891D5@xxxxxxxxx> <200610121802.k9CI2A8i025805@xxxxxxxxxxxxxx> <Pine.OSX.4.61.0610130720390.16279@xxxxxxxxxxxxxxx>
- Sender: Phil Pennock <phil@xxxxxxxxxxxxx>
On 2006-10-13 at 07:27 -0700, William Scott wrote:
> luser-% sudo zsh
> root-# (various nefarious evildoing)
> root-# exit
> zsh: can't write history file /Users/luser/.zsh_history
>
> (I call it .zsh_history, BTW).
>
> Even "sudo zsh -l" doesn't help. $HISTFILE never changes.
I strongly suspect that somewhere in your zsh startup files, you're
exporting HISTFILE to the environment. The variable is used by tcsh
too, so tcsh will then be seeing the value and writing data in its own
format. zsh later does sanity checks when writing its history, so
complains.
HISTFILE should be set, but not exported, being an internal control
variable.
In zsh:
% env | grep '^HISTFILE='
Regards,
-Phil
Messages sorted by:
Reverse Date,
Date,
Thread,
Author