From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: compset -q oddities
Date: Mon, 12 Sep 2016 23:06:32 +0000 [thread overview]
Message-ID: <20160912230632.GA29577@fujitsu.shahaf.local2> (raw)
In-Reply-To: <160911191422.ZM21970@torch.brasslantern.com>
Bart Schaefer wrote on Sun, Sep 11, 2016 at 19:14:22 -0700:
> On Sep 11, 7:30am, Daniel Shahaf wrote:
> }
> } I managed to break a few things while composing a reply to 39265:
>
> I think mostly what you've discovered is cases where "compset" is not
> compensating for pilot error. "compset -q" does not expect to be
> called on an empty word, or on any word that can't be interpreted as
> a (possibly partial) command line;
Thanks, but I don't understand how any of those examples constitutes
a "pilot error" or an empty word.
In #1, "~~~" is a complete word; completion changed it to "~~~~~~" which
is also a complete word but wasn't a candidate completion.
In #2 and #3, the input is a prefix of a valid command line («g
$'\'foo\''» and «h "$'foo'"» respectively). #2 does not involve an
empty word; the word there is «'» (a single-byte word).
Thanks again for the explanation. I'd like to understand what the
expected behaviour here is. They triggered DPUTS calls so I assumed
they were bugs.
Cheers,
Daniel
(#2 doesn't call compadd, but behaves the same if a call to _nothing is
added to _g.)
next prev parent reply other threads:[~2016-09-12 23:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 7:30 Daniel Shahaf
2016-09-12 2:14 ` Bart Schaefer
2016-09-12 23:06 ` Daniel Shahaf [this message]
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
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=20160912230632.GA29577@fujitsu.shahaf.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).