zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: completion is over thinking things.
Date: Sun, 29 Sep 2019 11:41:12 -0700	[thread overview]
Message-ID: <a356aee8-ab3e-859c-fe0e-32a8fdc3705a@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7YAD=HCxgu2Lf9H0+XRhC22B3-4YpjJVBEUkujY73qKhw@mail.gmail.com>

On 2019-09-29 9:44 a.m., Bart Schaefer wrote:
> On Sun, Sep 29, 2019 at 8:30 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>> "I don't know half of you half as well as I should like, and I like
>> less than half of you half as well as you deserve."
Bilbo.
>> zstyle ':completion:*' completer _expand _complete _files
>>
>> Note that this only makes completion fall back to _files when nothing
>> else matches; if _expand or _complete finds something, you won't get
>> file names.  If you want file names all the time, mixed in with other
>> results, you'll have to write a custom function.  The simplest such
>> function might look like:
Not to tempt the Gods, but if I changed the order:

zstyle ':completion:*' completer _files _expand _complete

... would I get files offered first?  I get the impression that that line is most of the meat of completion.

I would not recommend doing this

... Where angels fear to tread.  Praise, I'd not think of it. Normally I break things deliberately just to see how they work, and if it's out of bounds I'm going in ... but not here!

Thanks Bart and Dana.



  reply	other threads:[~2019-09-29 18:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28 17:05 Ray Andrews
2019-09-28 17:13 ` Roman Perepelitsa
2019-09-28 17:36   ` Ray Andrews
2019-09-29  4:47     ` dana
2019-09-29 15:29       ` Ray Andrews
2019-09-29 16:44         ` Bart Schaefer
2019-09-29 18:41           ` Ray Andrews [this message]
2019-09-29 19:06             ` Bart Schaefer
2019-09-29 19:35               ` Ray Andrews
2019-09-29 13:09     ` Mikael Magnusson
2019-09-29 15:11       ` Ray Andrews
2019-09-29 15:19         ` Pier Paolo Grassi
2019-09-28 17:14 ` gmail

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=a356aee8-ab3e-859c-fe0e-32a8fdc3705a@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@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).