zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Are completions in some way heavy?
Date: Wed, 8 Jun 2016 11:40:09 -0700	[thread overview]
Message-ID: <160608114009.ZM807@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVAvYZXv=srUPVGQa-WTXGdKpcO6CL42Ezx4bN9bDB66kQ@mail.gmail.com>
In-Reply-To: <30148.1465376630@thecus.kiddle.eu>

On Jun 8,  6:34am, Sebastian Gniazdowski wrote:
} Subject: Re: Are completions in some way heavy?
}
} On 7 June 2016 at 22:44, Bart Schaefer <schaefer@brasslantern.com> wrote:
} > Again if they are actually disturbing you, why are you invoking them
} > in the first place?
} 
} Luckily an example can be provided. I was greeping for a text. It was
} returning git objects. Wanted to disable lookup in binary files. But
} can never remember is it "with-binary-files" or something similar
} (turns out it's --binary-files, but my memory didn't play nice on
} this). So I entered grep --with<TAB>. Nothing was returned.

I see.  I don't really have any good suggestions here -- there is the
_complete_fallback idea but all it does is provide alternate guesses
for the possible argument positions, which doesn't help in this case.

It might be do-able to revert to executing run-help when there are no
completions found, but that would be wrong in a lot of cases (e.g.,
on file name not matched, displaying a manual page isn't useful).

} I might have tried grep --binary and nothing would be returned because
} turns out grep completion is very short on long options on OS X (no
} one complained?).

No complaints, no.  It appears from cursory examination that the person
who initally wrote _grep only had access to GNU grep, and _grep has had
only a few minor updates since 2002.


On Jun 8, 11:03am, Oliver Kiddle wrote:
} Subject: Re: Are completions in some way heavy?
}
} Sebastian Gniazdowski wrote:
} > So why did I try completion. To take a guess maybe. This leads to an
} > idea of how this could be done:
} >
} > - tab invokes "small man page" as it usually does after "command -<TAB>"
} > - the text can be searched - entering something greps lines in the "man page"
} > - bits of text can be navigated like in file completion when properly
} > configured - I mean cursor keys move the reverse highlight over what's
} > available
} 
} Menu selection (the zsh/complist module) has an incremental search, so
} what you describe above can already be done.

I think Sebastian wants to search through the descriptions, whereas the
complist search only examines the completions themselves.

None of this helps with the situation Sebastian described above wherein
the completion results/descriptions do not include the desired content.


  reply	other threads:[~2016-06-08 18:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 12:43 Sebastian Gniazdowski
2016-06-06 16:01 ` Bart Schaefer
2016-06-06 19:28   ` Sebastian Gniazdowski
2016-06-07 20:44     ` Bart Schaefer
2016-06-08  4:34       ` Sebastian Gniazdowski
2016-06-08  9:03         ` Oliver Kiddle
2016-06-08 18:40           ` Bart Schaefer [this message]
2016-06-10 12:22             ` Sebastian Gniazdowski
2016-06-10 17:42               ` Bart Schaefer
2016-06-11  7:15                 ` Sebastian Gniazdowski
2016-06-11 17:18                   ` Bart Schaefer
2016-06-11 17:44                     ` Sebastian Gniazdowski
     [not found]           ` <160608114009.ZM807__13786.2274809324$1465411295$gmane$org@torch.brasslantern.com>
2016-06-10 17:35             ` Daniel Shahaf
2016-06-10 19:49               ` Bart Schaefer
     [not found] ` <160606090104.ZM11947__15732.477248139$1465228961$gmane$org@torch.brasslantern.com>
2016-06-07 22:53   ` Daniel Shahaf

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=160608114009.ZM807@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).