From: Adam Spiers <adam@spiers.net>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: completion for perl
Date: Mon, 13 Mar 2000 17:10:31 +0000 [thread overview]
Message-ID: <20000313171031.A2532@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <200003131057.LAA17005@beta.informatik.hu-berlin.de>; from wischnow@informatik.hu-berlin.de on Mon, Mar 13, 2000 at 11:57:05AM +0100
Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote:
>
> Adam Spiers wrote:
>
> > Whilst struggling with the mess which is _perl_config_vars below, it
> > struck me how an equivalent of compset -P which matched the /whole/ of
> > PREFIX rather than just the beginning would have come in handy.
>
> Err... `compset -P "*"' does that, but it leaves you with an empty
> $PREFIX, of course, which is probably not what one wants.
Sorry; I didn't explain myself clearly at all. I would like to be
able to do a compset -P type of operation using a pattern which is
anchored to both the start /and/ end of PREFIX, rather than just the
start, which is what currently always happens. Then again, I suppose
this can be implemented easily manually, e.g.:
if [[ "$PREFIX" == *: ]]; then
IPREFIX="$IPREFIX$PREFIX"
PREFIX=''
fi
> > Also, as you can see from the compstate[quoting] line below, I
> > tried to get completion working for
> >
> > $ perl -V:'<TAB>
> >
> > and
> >
> > $ perl -V:"<TAB>
> >
> > so that it would insert a single space after each configuration
> > variable completed while within quotes, rather than a quoted single
> > space, but I didn't fully understand how compset -q works, and
> > couldn't stop it from eating up the opening quote. Help! :-)
>
> The problem is that we check the quoting stuff at the very beginning
> of the completion code -- and detect only quotes at the beginning of
> the word. So what we could get to work is completion of
>
> $ perl '-V:<TAB>
>
> but not with the quote after the colon. That's done with first calling
> `compset -q', then the `compset -P'. Getting quotes in words to work
> is to hard to make me try it (all kinds of nasty interactions with the
> lexer). But maybe calling first `compset -P' and then `compset -q'
> should have the same effect as the other way round... I currently
> don't remember why it behaves the way it does.
So is there currently no solution? I tried using things like
compset -P '*"'
but they never matched, presumably because of the lexer interactions
you mention.
next prev parent reply other threads:[~2000-03-13 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 10:57 Sven Wischnowsky
2000-03-13 17:10 ` Adam Spiers [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-14 8:12 Sven Wischnowsky
2000-03-12 13:28 Adam Spiers
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=20000313171031.A2532@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.dk \
/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).