From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Eric Freese <ericdfreese@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] Include number of chars in zle unget mechanism in $PENDING calculation
Date: Sat, 4 Mar 2017 14:53:07 +0000 [thread overview]
Message-ID: <20170304145307.GA18347@fujitsu.shahaf.local2> (raw)
In-Reply-To: <CAAikoA+cgd9_jvPH9L2oDuvmZrTEaoh9qoH0K_VGo37U3N_oqw@mail.gmail.com>
Eric Freese wrote on Fri, Mar 03, 2017 at 16:54:39 -0700:
> Would love to see this merged.
It was merged yesterday (67c5d83df33c).
next prev parent reply other threads:[~2017-03-04 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 23:54 Eric Freese
2017-03-04 14:53 ` Daniel Shahaf [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-01 1:25 Eric Freese
2017-03-01 2:52 ` Bart Schaefer
2017-03-01 3:51 ` Eric Freese
2017-03-02 14:31 ` Peter Stephenson
2017-03-01 14:41 ` Eric Freese
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=20170304145307.GA18347@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=ericdfreese@gmail.com \
--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).