From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id ff20de67 for ; Sat, 9 Mar 2019 16:44:32 +0000 (UTC) Received: (qmail 1490 invoked by alias); 9 Mar 2019 16:44:21 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 44110 Received: (qmail 12354 invoked by uid 1010); 9 Mar 2019 16:44:21 -0000 X-Qmail-Scanner-Diagnostics: from out2-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.100.2/25376. spamassassin: 3.4.2. Clear:RC:0(66.111.4.26):SA:0(-2.6/5.0):. Processed in 5.287069 secs); 09 Mar 2019 16:44:21 -0000 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= daniel.shahaf.name; h=message-id:in-reply-to:references:date :from:to:cc:subject:content-type; s=fm2; bh=uHLH082kpVmvdTzJV4Az tWXeIz1ZhGVJisoO1kbdCQQ=; b=hb8YP43hbJZSCm0N3qLIFobqrjkNoGbSFiil MObZ4fz+mGSnmo0+Hv9cr9PGMgmXS6U6DUqJyvp1dtjnzVOSBWzPKZqYSoz9iF7j pj76mGcCsr4pevjdSDdVIyRwdSsZCPVqrdPYMmkUhNmwZDr2AtxEtSBxxrqf+rzU CCBAzkfF5Nh1xPFXZQn7cg7ukmJR2VZu8VQXUaoDddPzG3GpO3HvI1gf9oXHlGCZ NI0eEqtyuxfWbL+BFRwFuzlq38t0Uoj1ELbf48GOhtjHZnnatzVh8MNCMp8rrRcW 6kXpxVvLUvpEoDEuxEgyCQHXu4RHZv40mBST6gcvcmslfV/S9w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=uHLH082kpVmvdTzJV 4AztWXeIz1ZhGVJisoO1kbdCQQ=; b=lxDUt6VjQtj43iP3eAqoYr/ldF0idWupL s5LKQ2gQFypmpQc4dEGuZ8paEdcx7OpTOvLDUaQ9aCerv0CIEPnQun89F5dLm+Je RQL7QuiS81i4x8IFWVtckXdozMMXGQLE+is7yUqJjBHqDHniEJ6GTC2M6+goASCJ k/kedg2rQw2jz/eK+jEmqVtiambh7Q8e6Hya3C06cOCR0Sr+82I4r4wVi1StdRmD Je/yz8bFXL1BtarN/Yf7BFH9XPDj2DbhQbO6qH+egmlUhB49omyE1ULdubrmUDfd d6RA3T1bR256JlogVn4wwlJgVWpHNjDy6FXa/Yw1Tg7gjLaDH75SQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrgedvgdelhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfkfgjfhffhffvufgtsehttdertd erreejnecuhfhrohhmpedfffgrnhhivghlucfuhhgrhhgrfhdfuceougdrshesuggrnhhi vghlrdhshhgrhhgrfhdrnhgrmhgvqeenucfrrghrrghmpehmrghilhhfrhhomhepugdrsh esuggrnhhivghlrdhshhgrhhgrfhdrnhgrmhgvnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.5-925-g644bf8c-fmstable-20190228v5 X-Me-Personality: 3897223 Message-Id: <57caa504-8287-4078-bd34-47ac7426e1db@www.fastmail.com> In-Reply-To: <85B1B476-6F08-4AB0-8E30-B165A0E98082@dana.is> References: <20190307192305.GA3173@av.sy.gs> <7a2210af-0a67-4289-86c2-388e67eff32e@www.fastmail.com> <85B1B476-6F08-4AB0-8E30-B165A0E98082@dana.is> Date: Sat, 09 Mar 2019 11:43:40 -0500 From: "Daniel Shahaf" To: dana Cc: zsh-workers@zsh.org, "Adrian Vollmer" Subject: =?UTF-8?Q?Re:_Bug_in_git_tab_completion:_If_git.showSignature_=3D_true_i?= =?UTF-8?Q?s_set_globally,_tab_completion_of_commits_is_garbled?= Content-Type: text/plain X-Qmail-Scanner-2.11: added fake MIME-Version header MIME-Version: 1.0 dana wrote on Sat, 09 Mar 2019 16:26 +00:00: > On 8 Mar 2019, at 14:22, Daniel Shahaf wrote: > >Should we use git-rev-list(1) instead of git-log(1)? The former is a > >plumbing command, so should be the more appropriate interface for this > >use-case. > > Not sure. For a plumbing command it leaves a bit to be desired; it has no -z It does have %x00, though. > and it doesn't really respect the format you tell it to use. In fact the > 'commit 1234567890...' header it prints is actually hard-coded. Huh. Odd, but I think we can live with that: we can just have _git discard the hardcoded header line that git emits. All we really care about is that future git versions will continue to emit that line. I assume they will, for compatibility reasons. Cheers, Daniel