From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: lilydjwg <lilydjwg@gmail.com>, zsh-users@zsh.org
Subject: Re: No fsync on history file? I lost my history
Date: Sun, 23 Sep 2018 13:35:47 +0000 [thread overview]
Message-ID: <1537709747.103981.1517680056.72C7A43E@webmail.messagingengine.com> (raw)
In-Reply-To: <20180923085246.GA19251@lilyforest.localdomain>
lilydjwg wrote on Sun, 23 Sep 2018 16:52 +0800:
> Would you add the fsync call or make an option for that?
I'd be happy to accept patches for this.
Daniel
next prev parent reply other threads:[~2018-09-23 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 8:52 lilydjwg
2018-09-23 13:35 ` Daniel Shahaf [this message]
2018-09-23 14:22 ` lilydjwg
2018-09-23 14:46 ` Daniel Shahaf
2018-09-23 15:25 ` lilydjwg
2018-09-23 15:45 ` Daniel Shahaf
2018-09-23 19:40 ` Vincent Lefevre
2018-09-24 3:03 ` lilydjwg
2018-09-23 18:02 ` Mikael Magnusson
2018-09-24 3:04 ` lilydjwg
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=1537709747.103981.1517680056.72C7A43E@webmail.messagingengine.com \
--to=d.s@daniel.shahaf.name \
--cc=lilydjwg@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).