zsh-users
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Nadav Har'El" <nyh@math.technion.ac.il>
Cc: "dLux" <dlux@kapu.hu>, "ZSH users mailing list" <zsh-users@sunsite.dk>
Subject: RE: completion question
Date: Wed, 4 Jul 2001 17:27:02 +0400	[thread overview]
Message-ID: <002401c1048d$02b12c30$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <20010704160217.B8633@leeor.math.technion.ac.il>

> Maybe what is bothering him is that if you do
>
>      /u_local/
>        ^--- cursor (no space)
> and press TAB, nothing is completed. If you enter a slash,
> however, it works:
>
>     /u/_local/          (or /u_/local/)
> is completed to
>     /usr/local/
>

Ah, I see. Well, somebody else have to answer this. I guess, this is what
_prefix completer is for, but I never used it. As a quick try (assuming, you
are using new completion):

bor@itsrm2% setopt completeinword
bor@itsrm2% zstyle ':completion:*' completer _oldlist _prefix _complete
_match
bor@itsrm2% l /usTABcal
bor@itsrm2% l /usr/cal
                             ^ cursor here

It still behaves differently; zsh totally ignores suffix, while bash not.
Next TAB in above example gives you

in bash:

MW1G017@MW1G17C ~
$ ls /usr/cal
bin             include         local           share
doc             info            logs            src
etc             lib             man             ssl
i686-pc-cygwin  libexec         sbin            tmp

in zsh:

bor@itsrm2% l /usr/TT_DB/cal
Completing files
TT_DB/       add-on/      adm@         admin/       bin/         ccs/
crash@       dt@          games/       ic/          include/     lbin/
lib/         lib64s/      local/       lost+found/  mail@        menus/
net/         news@        oasys/       opt/         options@     pkg/
preserve@    pub@         sadm/        sbin/        share/       spool@
src/         sysadm/      tmp@         ucb/         ucbinclude/  ucblib/
vmsys/

(ignore list settings).

I do not know how to make them behave identically.

OTOH in zsh you do not need to go back; just say /u/bTAB and it will be
completed to /usr/bing. Much better :-)

-andrej


  reply	other threads:[~2001-07-04 13:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010704142951.B4036@dlux.hu>
2001-07-04 12:50 ` Andrej Borsenkow
2001-07-04 13:02   ` Nadav Har'El
2001-07-04 13:27     ` Andrej Borsenkow [this message]
2001-07-04 14:45     ` dLux
2001-07-04 15:43       ` Sven Wischnowsky
2001-07-04 15:47         ` Sven Wischnowsky
2001-07-05 14:31           ` 4.0.2 Nick Cross
     [not found] <20110602191951.566gmx1@mp009.gmx.net>
2011-06-06 22:33 ` Completion question meino.cramer
2011-06-07  5:12   ` Jun T.
2011-06-07  8:29   ` Peter Stephenson
2011-06-07  8:53   ` Jérémie Roquet
2004-08-31 11:02 Completion Question Sean Johnston
2004-08-31 11:51 ` Oliver Kiddle
  -- strict thread matches above, loose matches on Subject: below --
2003-02-06  1:32 completion question Le Wang
2003-02-10 11:06 ` Oliver Kiddle
2002-08-09  6:51 Completion question Byron Foster
2002-08-09  7:28 ` Sven Wischnowsky
2002-08-11  3:29   ` Byron Foster
2002-06-11 11:40 jarausch
2002-06-11 11:55 ` Sven Wischnowsky
2001-07-30  2:15 completion question Eric D. Friedman
2001-07-30  2:32 ` Bart Schaefer
2001-07-04 10:57 dLux
2001-07-04 11:10 ` Andrej Borsenkow

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='002401c1048d$02b12c30$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=dlux@kapu.hu \
    --cc=nyh@math.technion.ac.il \
    --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).