On Tue, 16 Nov 2010 15:33:30 +0200, "Ciprian Dorin, Craciun" <ciprian.craciun at gmail.com> wrote: > But in my particular case `~/.notmuch-config` is symlinked to an > applications configuration directory which is versioned. Thus I've > expected than when notmuch updates the config, it opens it for > read-write, but with the truncation flag (which as a consequence would > have modified the symlinked file). But instead it deleted the symlink, > and replaced it with a newly created file (thus breaking my custom > configuration backup system.) > > So my question is: is this behaviour (of deleting the file and > creating a new one) deliberate? If not, could it be fixed (I could > provide a patch) to just update the file in place?
Hi, Ciprian. I had not noticed this, but now that you mention it, I see that the same thing happened to me. This behavior is surely not deliberate, and is definitely undesirable. A patch would be welcome. jamie. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20101116/af48bf11/attachment.pgp>
