zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: [PATCH] compdescribe fix for unsorted groups (workers/34814) (was: Re: completion: git: --fixup: problem with _describe -2V and duplicate commit subjects)
Date: Sat, 23 May 2015 10:03:24 +0000	[thread overview]
Message-ID: <20150523100324.GB1889@tarsus.local2> (raw)
In-Reply-To: <20150520235158.GB2029@tarsus.local2>

Daniel Shahaf wrote on Wed, May 20, 2015 at 23:51:58 +0000:
> While looking into this, I've also found a 100% CPU consumption bug; to
> reproduce (in master):

So, another summary...

- 35127#1 (fix for _describe -2V with duplicate descriptions): no reason
  to hold it back any longer; I'll push it.

- 35227 (duplicate :descriptions message): cosmetic issue.  The example
  given in that email requires 35127#2, which I'm not going to push yet,
  and no other example is known, so this issue is not blocking.

- 35246#tail (infinite loop): pre-existing problem, not related to my
  changes (it also happens in 5.0.7, which precedes my changes).  No
  known instances "in the wild".  I'm not currently looking into it.

- 35246#head (_describe output garbled): likewise, a pre-existing
  problem with no known instances.  Enclosed a patch to record its
  existence.

- Empty matches, probably added by cd_get(), are definitely related to
  the third issue and may be related to the second and fourth as well.

Is there better way to track all these issues than X-Seq numbers?

---

diff --git a/Completion/Base/Utility/_describe b/Completion/Base/Utility/_describe
index ab72005..76ab1d9 100644
--- a/Completion/Base/Utility/_describe
+++ b/Completion/Base/Utility/_describe
@@ -1,5 +1,12 @@
 #autoload
 
+# ### Note: Calling this function twice during one completion operation, such
+# ### that in each call there exists a pair of items having the same description
+# ### as each other, and the two calls specify the same $_type, currently leads
+# ### to garbled output; see workers/35229 (May 2015) and its thread (which also
+# ### discusses at least two other issues, that may or may not be related to
+# ### this one).
+
 # This can be used to add options or values with descriptions as matches.
 
 local _opt _expl _tmpm _tmpd _mlen _noprefix


      parent reply	other threads:[~2015-05-23 10:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 22:05 completion: git: --fixup: problem with _describe -2V and duplicate commit subjects Daniel Hahler
2015-03-24  0:07 ` Daniel Hahler
2015-03-29  5:47   ` Daniel Shahaf
2015-03-30 18:21     ` Daniel Shahaf
2015-05-13 12:41       ` Daniel Hahler
2015-05-14 14:28         ` Daniel Shahaf
2015-05-13 12:44     ` Daniel Hahler
2015-05-14 14:36     ` [PATCH] compdescribe fix for unsorted groups (workers/34814) (was: Re: completion: git: --fixup: problem with _describe -2V and duplicate commit subjects) Daniel Shahaf
2015-05-16 22:54       ` Daniel Shahaf
2015-05-17  4:07         ` Bart Schaefer
2015-05-17 23:40           ` Daniel Shahaf
2015-05-18  4:00             ` Bart Schaefer
2015-05-19  1:36               ` Daniel Shahaf
2015-05-19  4:37                 ` Bart Schaefer
2015-05-19 20:41                   ` Daniel Shahaf
2015-05-19 22:03                     ` Bart Schaefer
2015-05-19 20:44       ` Daniel Shahaf
2015-05-19 21:01         ` Daniel Shahaf
2015-05-19 22:23         ` Bart Schaefer
2015-05-20 23:51           ` Daniel Shahaf
2015-05-22  5:02             ` Bart Schaefer
2015-05-23 10:03             ` Daniel Shahaf [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=20150523100324.GB1889@tarsus.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).