zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Still bugs completing .files; _multi_parts
Date: Tue, 15 Feb 2000 21:58:30 +0000	[thread overview]
Message-ID: <E12Kpvo-00022q-00.2000-02-15-21-54-52@cmailg1.svr.pol.co.uk> (raw)

Firstly, I did

% less ~/.<TAB>

and got a list of files not beginning with a dot amongst those which did.


Secondly and unrelatedly, I was trying out _multi_parts for the user guide
and did (you can see where this is coming from):

_foo () {
  local groups
  groups=(news.announce.newuser
          news.groups.questions
          gnu.emacs.gnus
          comp.unix.shell
          rec.arts.sf.written
          freeserve.test) 
  _multi_parts . groups
}
compdef _foo foo

Hitting ^D, everything was fine: I get the list
  comp.        freeserve.   gnu.         news.        rec.       
as expected.  Now hitting tab, which causes menu completion and menu
selection to start up, things start to go wrong.  First, the list is
expanded to show both `news.', instead of pruning the duplicate.  Second,
the value inserted is the full whack, e.g. `comp.unix.shell'; I can't
simply cycle through the top level and select the next one down.  I'm
puzzled about this because as far as I can see the only existing call to
_multi_parts in _tar works just the same way, except with / as the
separator.  The clue seems to be that if I go straight into completion
without doing ^D things work as expected (except that I don't see a final
`.' if the part isn't the final one, as I would expect to do in the tar
case).

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>


             reply	other threads:[~2000-02-15 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-15 21:58 Peter Stephenson [this message]
2000-02-16 16:25 Sven Wischnowsky

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=E12Kpvo-00022q-00.2000-02-15-21-54-52@cmailg1.svr.pol.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --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).