From: Thomas Richter <richter@thomas-richter.de>
To: list zsh-users <zsh-users@sunsite.dk>
Subject: Re: history trouble
Date: Sun, 29 Jan 2006 17:29:20 +0100 [thread overview]
Message-ID: <20060129162920.GA32595@thomas-richter.de> (raw)
In-Reply-To: <1060128203236.ZM1042@candle.brasslantern.com>
Hi Bart Schaefer <schaefer@brasslantern.com>,
you wrote on Saturday, 2006-01-28 20:32:36 +0000:
> On Jan 28, 8:04pm, Thomas Richter wrote:
>
> Possible reasons for the history not to be read are:
>
> - the NO_RCS option is set (the doc says this prevents history from
> being written, but it also suppresses reading it)
This option is not set.
> - the INTERACT option is not set
This option is set.
> - lockhistfile() fails because
> + a temporary lock file can't be created in the same directory
> as the HISTFILE
How can I test this?
> + a link to that temp file can't be created
ln -s $HISTFILE newname is ok
> + something else [possibly several somethings] has the file locked
> for more than about 10 seconds (but this shouldn't apply at shell
> startup, only for incremental history)
no process has this file open
> - the file can't be opened for reading
cat $HISTFILE is ok
> - some part of the file is corrupt
no contains only one line with one word
> - HISTSIZE is zero (in which case, I believe, the file is read but all
> the contents are discarded)
HISTSIZE = 99999
> My (new, ahem) guess is that the problem is with the lock file.
wkr Thomas Richter
--
dss1://49.431.801306 Wot're we going to do tonight, Brain ?
gsm://49.179.5192431 The same thing we do every night, Pinky .
icq://124849926 Try to TAKE OVER THE WORLD !
mailto:richter@thomas-richter.de http://www.thomas-richter.de
next prev parent reply other threads:[~2006-01-29 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 7:41 Thomas Richter
2006-01-28 15:53 ` Bart Schaefer
2006-01-28 19:04 ` Thomas Richter
2006-01-28 20:32 ` Bart Schaefer
2006-01-29 16:29 ` Thomas Richter [this message]
2006-02-01 0:04 ` Peter A. Castro
2006-02-01 2:10 ` Frank Terbeck
2006-02-01 18:20 ` Peter A. Castro
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=20060129162920.GA32595@thomas-richter.de \
--to=richter@thomas-richter.de \
--cc=zsh-users@sunsite.dk \
/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).