From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Etc/BUGS: Remove fixed items, add 'compset -q' item from workers/39306.
Date: Thu, 15 Sep 2016 22:00:41 -0700 [thread overview]
Message-ID: <160915220041.ZM4454@torch.brasslantern.com> (raw)
In-Reply-To: <1473995130-21781-1-git-send-email-danielsh@fujitsu.shahaf.local2>
Thanks for looking at this.
On Sep 16, 3:05am, Daniel Shahaf wrote:
}
} ------------------------------------------------------------------------
} +'compset -q' has a byte-counting issue, described in workers/39306:
} +
} +% compdef _f f
} +% _f() { compset -q }
} +% f $'\'<TAB>
} +compcore.c:1684: expecting 'x' at offset 2 of "'x"
} +------------------------------------------------------------------------
True, but not the bug I was thinking of; that one is entirely invisible
unless the shell was configured with --enable-zsh-debug, and fixing it
would not change the end result, so it'll very seldom be seen.
The bug I meant to mention was the multiple-backslashing of tildes and
leading equal signs following "compadd -q", and consequent inability
to complete them properly. But it's hard to create a real-world
example of that.
next prev parent reply other threads:[~2016-09-16 5:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 7:30 compset -q oddities Daniel Shahaf
2016-09-12 2:14 ` Bart Schaefer
2016-09-12 23:06 ` Daniel Shahaf
2016-09-13 6:28 ` Bart Schaefer
2016-09-13 10:21 ` Peter Stephenson
2016-09-14 17:56 ` Bart Schaefer
2016-09-15 5:10 ` Daniel Shahaf
2016-09-16 0:40 ` Bart Schaefer
2016-09-16 3:05 ` [PATCH] Etc/BUGS: Remove fixed items, add 'compset -q' item from workers/39306 Daniel Shahaf
2016-09-16 5:00 ` Bart Schaefer [this message]
2016-09-14 3:22 ` compset -q oddities Daniel Shahaf
2016-09-14 5:20 ` Bart Schaefer
2016-09-14 6:12 ` Daniel Shahaf
2016-09-14 14:59 ` Bart Schaefer
2016-09-14 19:52 ` Oliver Kiddle
2016-09-15 3:08 ` Bart Schaefer
2016-09-14 8:31 ` Peter Stephenson
2016-09-14 16:04 ` 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=160915220041.ZM4454@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).