From: Bart Schaefer <schaefer@brasslantern.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: suggested patch for error flagged in static analysis
Date: Mon, 04 Aug 2014 13:53:25 -0700 [thread overview]
Message-ID: <140804135325.ZM1993@torch.brasslantern.com> (raw)
In-Reply-To: <83960560B9A9E445909AC748DB1139982B5AB441@MX103CL01.corp.emc.com>
On Aug 4, 7:28pm, Miles Ohlrich wrote:
}
} !CMF_FILE is always 0. Should be ~CMF_FILE.
}
} --- zsh-5.0.5/Src/Zle/compctl.c.orig 2014-08-04 12:20:54.327001219 -0700
} +++ zsh-5.0.5/Src/Zle/compctl.c 2014-08-04 12:21:41.079945543 -0700
Wow, compctl ? This is a really ancient bug. I wonder what the effect
was in practice ... it'll likely have almost no visible effect these days,
as compctl is all but unused.
Still, no reason not to commit it.
prev parent reply other threads:[~2014-08-04 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 19:28 Miles Ohlrich
2014-08-04 20:53 ` Bart Schaefer [this message]
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=140804135325.ZM1993@torch.brasslantern.com \
--to=schaefer@brasslantern.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).