From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: compset -q oddities
Date: Wed, 14 Sep 2016 07:59:46 -0700 [thread overview]
Message-ID: <160914075946.ZM28998@torch.brasslantern.com> (raw)
In-Reply-To: <20160914061252.GA22452@fujitsu.shahaf.local2>
On Sep 14, 6:12am, Daniel Shahaf wrote:
} Subject: Re: compset -q oddities
}
} Why should "f \\\~\\\~\\\~<TAB>" fail?
}
} Essentially, 'compset -q' "looks through" one level of quoting, and
} whatever is happening in the "ssh \git.code<TAB>" case looks through the
} second level of quoting.
}
} Makes sense?
Yes, except that in \g the backslash really is redundant, whereas with
\~ the intent might be to compare a literal tilde to an expansion tilde
(which is different still from a globbing tilde).
} Bart Schaefer wrote on Tue, Sep 13, 2016 at 22:20:29 -0700:
} > Also now that I think of it, there's only one match with that compadd,
} > so it should have appended a trailing space and the second tab should
} > have been in an entirely new (also empty) word.
}
} That's a bit tricky. I think it should append an escaped space, e.g.,
} "sh -c touc<TAB>" should append <h> <Backslash> <Space>.
No, that's *exactly* the kind of DWIM-ing that we abandoned. If the user
wants the space quoted, then he should start with "sh -c 'touc<TAB>".
next prev parent reply other threads:[~2016-09-14 15:06 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
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 [this message]
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=160914075946.ZM28998@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).