From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: zsh got stuck without any message because of history lock file
Date: Fri, 25 Apr 2014 08:26:35 -0700 [thread overview]
Message-ID: <140425082635.ZM12243@torch.brasslantern.com> (raw)
In-Reply-To: <20140425093525.3754a495@pwslap01u.europe.root.pri>
On Apr 25, 9:35am, Peter Stephenson wrote:
}
} On Thu, 24 Apr 2014 22:02:32 -0700
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > However, this would mean that every zsh that is accessing the same
} > HISTFILE has to be using the same locking options. Is that OK?
}
} It's fairly easy to get inconsistent shell options, however. I suppose
} we could think about simple tests to see if it looks like it's been
} locked a different way and print a warning.
That shouldn't be too difficult code-wise, but will require calling
lstat() on the .LOCK file name (ignoring failure thereof).
I'm going to go ahead and commit 32580 while we think about it.
next prev parent reply other threads:[~2014-04-25 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 16:48 Andreas
2014-04-24 17:02 ` Bart Schaefer
2014-04-25 5:02 ` Bart Schaefer
2014-04-25 8:35 ` Peter Stephenson
2014-04-25 15:26 ` Bart Schaefer [this message]
2014-04-25 15:53 ` Bart Schaefer
2014-06-26 20:46 ` Mikael Magnusson
2014-09-06 9:03 ` Mikael Magnusson
2014-09-06 18:51 ` Bart Schaefer
2014-04-24 17:58 ` Andreas
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=140425082635.ZM12243@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).