Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Failing to write to history file if containing directory doesn't exist
- X-seq: zsh-workers 23917
- From: "Nikolai Weibull" <now@xxxxxxxx>
- To: "Peter Stephenson" <pws@xxxxxxx>
- Subject: Re: Failing to write to history file if containing directory doesn't exist
- Date: Mon, 8 Oct 2007 14:08:08 +0200
- Cc: zsh-workers <zsh-workers@xxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=YM3rY7oUPozZOb9c8Z0Phyfcl96u63vVpOu9EF1GNO0=; b=fC6cM2xOichAqEP8suhD+TcDcGI2erFJVxsmN4zNIgv3h/KsViUyjWc/+35sVnTki7fADIkNiggSjHJ/r1Y/wXRfzjDT95PeZGRsQpOHOpCjZqBV0Hk1vYmQeyxY7+ZWOcq5h33roeVZtd/XPpE4YNBTBLztJ5257dVwFbcNVCI=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Pv9stbOIDq9c3YEincy1VdbsWxjx73E2ti2xaQh/q5N7JQ693klCBN5of8SS/UZlbtERZjf5w9zbv1B2lNeD0YBweo1lvGz707fJbrFTk2goJILFnj6f5GpYDlwCa1vLF/VtuzexMOrRsAVag7NDfPKhWAQqqWTNnpnYHPV1zaE=
- In-reply-to: <200710081015.l98AFlIU018448@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <dbfc82860710080309m41cfa984q5aa0474c6b4bdf62@xxxxxxxxxxxxxx> <200710081015.l98AFlIU018448@xxxxxxxxxxxxxx>
- Sender: nikolai.weibull@xxxxxxxxx
On 10/8/07, Peter Stephenson <pws@xxxxxxx> wrote:
> "Nikolai Weibull" wrote:
<rant>
Why do mail user agents still do this? My name /is/ Nikolai Weibull.
</rant>
> > Zsh currently fails to write a history file if the directory
> > containing it doesn't exist. Would a patch that creates the parent
> > directory if it doesn't exist before attempting to write to the
> > history file be of any interest? I'd be willing to write such a
> > patch, but if this behavior is undesirable, I won't waste my time.
> I'd have thought it was a reasonable expectation that the directory
> already existed. You can always add "mkdir -p ${HISTFILE:h}" when you
> set HISTFILE, if you need to.
Yes, sure, but if we assume that this isn't always the case, would
code that dealt with this case be interesting for inclusion?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author