From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: shared history file
Date: Sat, 2 Oct 2021 19:54:23 +0200 [thread overview]
Message-ID: <CAP+y1xBFZ=jTvsxXZbXogne3NV-0_-L9cLmfkGkTiFY58Q-PJw@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xBVmk9aBx3fjFNhSVAD8harR+JcyxxY9zNjvjje35yjCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
I forgot to mention that, while I was able to read the history file, the
new commands typed were not written to it, and this is the problem I would
like to solve
thanks
Pier Paolo Grassi
Il giorno sab 2 ott 2021 alle ore 19:52 Pier Paolo Grassi <
pierpaolog@gmail.com> ha scritto:
> Hello, I was trying to implement a per project shell history file.
> Some of these projects are on windows shared mounted via cifs. when I open
> those files as history with fc -p I get:
>
> /root/.zshrc:440: locking failed for /mnt/docs/projects/devbox/.history:
> operation not supported: reading anyway
> zsh: locking failed for /mnt/docs/projects/devbox/.history: operation not
> supported: reading anyway
>
> Is it possible to work around this? is it possibile in zsh to disable
> locking the history file during write operations? I am the only one writing
> to those files so I shouldn't risk a concurrent operation.
> I tried using setopt HIST_FCNTL_LOCK but ended up with an emptied history
> file.
>
> Pier Paolo Grassi
>
[-- Attachment #2: Type: text/html, Size: 1730 bytes --]
next prev parent reply other threads:[~2021-10-02 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 17:52 Pier Paolo Grassi
2021-10-02 17:54 ` Pier Paolo Grassi [this message]
2021-10-02 23:12 ` Bart Schaefer
2021-10-02 23:19 ` Pier Paolo Grassi
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='CAP+y1xBFZ=jTvsxXZbXogne3NV-0_-L9cLmfkGkTiFY58Q-PJw@mail.gmail.com' \
--to=pierpaolog@gmail.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).