Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Expanding quotes
- X-seq: zsh-users 18243
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxx
- Subject: Re: Expanding quotes
- Date: Tue, 17 Dec 2013 10:26:48 -0800
- In-reply-to: <l8po7s$1og$1@ger.gmane.org>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <l8po7s$1og$1@ger.gmane.org>
On Dec 17, 3:48pm, Yuri D'Elia wrote:
} Subject: Expanding quotes
}
} touch file file\' file\"
} ls *\"<TAB>
}
} results in:
}
} % ls file file\" file\'
Hmm, somewhere down in the completion internals the code that sets the
PREFIX string is re-quoting both the backslash and the single quote.
When this is re-interpolated by the expand-word code it turns into
the empty string, so you get the expansion of "*".
} % ls *[\']<TAB>
}
} doesn't expand
Same problem, except you get the expansion of *[] which is an invalid
pattern and hence nothing.
There's a basic conflict in the completion system in that it can't "know"
if you mean for the literal string backslash-quote to be completed, or if
you mean for the backslash to have its usual semantic effect on the quote.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author