From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Fix unintentional history modifiers.
Date: Thu, 22 Sep 2016 20:14:03 +0000 [thread overview]
Message-ID: <20160922201403.GA32196@fujitsu.shahaf.local2> (raw)
In-Reply-To: <160922093445.ZM7021@torch.brasslantern.com>
Bart Schaefer wrote on Thu, Sep 22, 2016 at 09:34:45 -0700:
> On Sep 22, 11:43am, Daniel Shahaf wrote:
> } Subject: [PATCH] Fix unintentional history modifiers.
> }
> } The _dates one worked even before this patch (!); I haven't investigated why.
>
> The _dsh one should have worked too. There is no :d modifier, so:
This doesn't explain why _dates worked: it had a parameter expansion in
a single-quoted string.
next prev parent reply other threads:[~2016-09-22 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 11:43 Daniel Shahaf
2016-09-22 16:34 ` Bart Schaefer
2016-09-22 20:14 ` Daniel Shahaf [this message]
2016-09-22 20:46 ` Bart Schaefer
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=20160922201403.GA32196@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--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).