zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: list zsh-users <zsh-users@sunsite.dk>
Subject: Re: history trouble
Date: Sat, 28 Jan 2006 20:32:36 +0000	[thread overview]
Message-ID: <1060128203236.ZM1042@candle.brasslantern.com> (raw)
In-Reply-To: <20060128190424.GC19690@thomas-richter.de>

On Jan 28,  8:04pm, Thomas Richter wrote:
} Subject: Re: history trouble
}
} Hi Bart Schaefer <schaefer@brasslantern.com>,
} you wrote on Saturday, 2006-01-28 15:53:51 +0000:
} > On Jan 28,  8:41am, Thomas Richter wrote:  
} > }
} > } The options look ok for me:
} > 
} > I don't see "login".  Only login shells read the history automatically.
} 
} On my other computer (zsh 4.1.1 (i386-suse-linux)) there also no 
} login set - but it read my history ...

Sorry, I'm being dense this morning.  I forgot that it's my own setup
that skips history settings for non-login shells.

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)

- the INTERACT option is not set

- lockhistfile() fails because
  + a temporary lock file can't be created in the same directory
    as the HISTFILE
  + a link to that temp file can't be created
  + 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)

- the file can't be opened for reading

- some part of the file is corrupt

- HISTSIZE is zero (in which case, I believe, the file is read but all
  the contents are discarded)

My (new, ahem) guess is that the problem is with the lock file.


  reply	other threads:[~2006-01-28 20:32 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 [this message]
2006-01-29 16:29       ` Thomas Richter
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=1060128203236.ZM1042@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).