zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [Pkg-zsh-devel] Bug#679824: zsh: Buggy perl completion with -e [origin: vincent@vinc17.net]
Date: Thu, 03 Jul 2014 09:42:01 -0700	[thread overview]
Message-ID: <140703094201.ZM9147@torch.brasslantern.com> (raw)
In-Reply-To: <20140703171107.23afc5db@pwslap01u.europe.root.pri>

On Jul 3,  5:11pm, Peter Stephenson wrote:
}
} Probably the best compromise in general would be to have .pl, .py, .rb
} and other files completed using separate tags, so you have the easily
} configurable option of picking out the native suffix or all files.
} 
} I've a vague memory you can already tell _files to do clever things like
} that in certain contexts but I'm too lazy to check.

One can use the file-patterns style to create separate tag groups.

     The file-patterns style provides alternatives to the default tags,
     which are not used.  Its value consists of elements of the form
     `PATTERN:TAG'; each string may contain any number of such
     specifications separated by spaces.

	[...]

     For example, to make the rm command first complete only names of
     object files and then the names of all files if there is no
     matching object file:

          zstyle ':completion:*:*:rm:*' file-patterns \
              '*.o:object-files' '%p:all-files'

It is often a bit tricky to get completion to actually *omit* the files in
one of the groups rather than merely reorder them.


  reply	other threads:[~2014-07-03 16:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-28 14:20 Fwd: " Axel Beckert
2014-06-30 10:58 ` Jun T.
2014-06-30 13:02   ` Jun T.
2014-07-03 15:59     ` Jun T.
2014-07-03 16:11       ` Peter Stephenson
2014-07-03 16:42         ` Bart Schaefer [this message]
2014-07-06 21:58   ` Oliver Kiddle
2014-07-23 12:01     ` takimoto-j
2014-06-30 11:45 ` Jun T.
2014-06-30 19:09   ` 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=140703094201.ZM9147@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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).