zsh-users
 help / color / mirror / code / Atom feed
From: John Cooper <john.cooper@eu.citrix.com>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-users@sunsite.dk, John Cooper <john.cooper@eu.citrix.com>
Subject: Re: Completing within colon separated paths
Date: 14 Mar 2001 16:30:07 +0000	[thread overview]
Message-ID: <m3bsr4ia9c.fsf@kontiki.cam.eu.citrix.com> (raw)
In-Reply-To: <Tc0a88d01524a47c72c@mailsweeper01.cambridgesiliconradio.com>

Peter Stephenson <pws@csr.com> writes:

 > > Is there a way to have TAB complete '/usr/local' from the X (marking cursor
 > > position) in the following:
 > > 
 > >   $ .:/home/jsc/bin:/usr/locX:/sbin:/usr/sbin:/usr/java/jdk1.3/bin
 > 
 > If you are using the new completion system, then it will work as long as
 > you are performing a parameter assignment (or it does for me).  So
 > 
 > $ PATH=/foo/bar:...
 > 
 > should perform completion correctly.  This is why it works in vared --- the
 > context is treated similarly to a parameter assignment.

OK, thanks for the explanation, and it works for me too when doing an
assignment.  But I do also sometimes want it to perform completion correctly
when completing a colon separated path on a cmd line (e.g., the -classpath
argument to java or jview).  Any way to force the same behavior in this
situation?

 > (You still need expand-or-complete-prefix --- I don't know if it's to be
 > considered a bug that the colon before is used as a word separator while the
 > one after isn't.)

I've just noticed that using `setopt completeinword' seems to allow me to
complete using TAB rather than expand-or-complete-prefix.

    --- John


  reply	other threads:[~2001-03-14 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-14 15:45 John Cooper
2001-03-14 15:53 ` Peter Stephenson
2001-03-14 16:30   ` John Cooper [this message]
2001-03-14 16:56     ` Peter Stephenson

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=m3bsr4ia9c.fsf@kontiki.cam.eu.citrix.com \
    --to=john.cooper@eu.citrix.com \
    --cc=pws@csr.com \
    --cc=zsh-users@sunsite.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).