From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh workers <zsh-workers@zsh.org>
Subject: Re: bug with completion in quotes
Date: Sun, 12 Oct 2014 18:51:25 +0100 [thread overview]
Message-ID: <20141012185125.62c73587@pws-pc.ntlworld.com> (raw)
In-Reply-To: <20141012183547.707f1818@pws-pc.ntlworld.com>
On Sun, 12 Oct 2014 18:35:47 +0100
Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> On Sun, 12 Oct 2014 00:37:09 +0200
> Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> > Compiled with --enable-zsh-debug, I get bugs listed when completing
> > inside $' style quotes whenever there's stuff after the cursor:
> >
> > <tab> appears at cursor position
> >
> > % : $'<tab>x
> > utils.c:5893: BUG: unterminated $' substitution
> > % : $'<tab>x'
> > zle_tricky.c:666: BUG: 0 <= wb <= zlemetacs <= we is not true!
> >
> > The line containing the first message was added in workers/22026 from
> > about 2006.
>
> The chief suspect is set_comp_sep()
Although that function is a permanent black stain on my soul, before I
send others on wild goose chases I don't think it can be the culprit
here since I think it's *only* used for recursive quotes. I'm now
wondering about get_comp_string() from line 1676 in zle_tricky.c,
including the grumpy comment I would guess is from me, since they usually
are, around line 1686. However, I haven't gone into the nitty gritty.
pws
next prev parent reply other threads:[~2014-10-12 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 22:37 Oliver Kiddle
2014-10-12 4:41 ` Bart Schaefer
2014-10-12 17:35 ` Peter Stephenson
2014-10-12 17:51 ` Peter Stephenson [this message]
2014-10-12 18:29 ` Bart Schaefer
2014-10-12 19:44 ` Peter Stephenson
2014-10-12 20:15 ` Peter Stephenson
2014-10-12 20:36 ` Bart Schaefer
2014-10-20 17:22 ` Peter Stephenson
2014-10-22 14:05 ` Oliver Kiddle
2014-10-22 14:28 ` Peter Stephenson
2014-10-24 8:51 ` Peter Stephenson
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=20141012185125.62c73587@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.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).