From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: Bug somewhere in verbose output for completion listing
Date: Thu, 03 Oct 2013 14:32:03 +0100 [thread overview]
Message-ID: <20131003143203.256f7397@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20131003140025.227f5bc1@pwslap01u.europe.root.pri>
On Thu, 03 Oct 2013 14:00:25 +0100
Peter Stephenson <p.stephenson@samsung.com> wrote:
> If I find a moment I'll try to make it more reproducible (although
> simply attaching to a running shell might be good enough to track it
> down).
Appears to be trivial to reproduce in the obvious manner, by generating
a single long completion.
autoload -Uz compinit
compinit
_wtf2 () {
local stuff
stuff=('SpoobleOneVariantWithAVeryLongCompletionThatCouldCauseAllSortsOfMayhemAfterAllWhoKnowsWhatEvilLurksEtc:2012/11/02 Description of SpoobleOne'
'SpoobleTwo:2013/02/13 Description of SpoobleTwo')
_describe -t stuff 'Stuff to complete.' stuff
}
compdef _wtf2 wtf2
_wtf () {
local stuff
stuff=('SpoobleOne:2012/11/02 Description of SpoobleOne'
'SpoobleTwo:2013/02/13 Description of SpoobleTwo')
_describe -t stuff 'Stuff to complete.' stuff
}
compdef _wtf wtf
Complete after wtf2 as far as getting a listing (the separator is the
default "--" instead of the "#" in the previous posting). This is as
easy as typing "wtf2 ^D". It already looks a bit screwy at this point
as the comment is missing even though the separator is present. Then
whenever you get a listing after wtf you see the problem.
pws
next prev parent reply other threads:[~2013-10-03 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 13:00 Peter Stephenson
2013-10-03 13:32 ` Peter Stephenson [this message]
2013-10-03 22:54 ` Bart Schaefer
2013-10-03 14:50 ` Bart Schaefer
2013-10-03 15:09 ` Bart Schaefer
2013-10-03 16:19 ` Bart Schaefer
2013-10-03 16:20 ` Peter Stephenson
2013-10-03 16:34 ` Peter Stephenson
2013-10-04 4:01 ` 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=20131003143203.256f7397@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.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).