zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
	<zsh-workers@sunsite.auc.dk>
Subject: RE: noglob and _match
Date: Tue, 25 Jul 2000 11:09:58 +0400	[thread overview]
Message-ID: <000f01bff607$57c7f770$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200007250650.IAA06314@beta.informatik.hu-berlin.de>

>
> Andrej Borsenkow wrote:
>
> > bor@itsrm2% noglob ls *TAB
> >
> > bor@itsrm2% noglob ls Brodsky/
> > Completing file
> > Brodsky/      addrbook.d/   dikz/         observe/      test/
> > .....
> >
> > Is it correct in this case? I suspect, the same aplies to _expand as
> > well.
>
> Why not? I mean: you explicitly requested completion, so the
> completion system *must* think that you know what you're doing.
>

In this case I want to list all files that start with `*' :-))) I expect
from completion to list *real* arguments. It is the same as listing
shell functions as possible command completion after sudo. Yes, I
requested completion - but I never requested to ignore noglob. Exaclty,
because I used it, completion system *must* think I know what I'm doing.

> And it's pretty damn useful, I'd say. *Especially* with noglob (and
> even more if that noglob is hidden in an alias).
>

I think, it is a matter of personal preference ... what about - first
try with noglob respected, second not (something in the line with
fignore or ingnored-patterns). With two different tags for both? That is
probably not so easy I'm afraid.

-andrej


  reply	other threads:[~2000-07-25  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-25  6:50 Sven Wischnowsky
2000-07-25  7:09 ` Andrej Borsenkow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-25  7:23 Sven Wischnowsky
2000-07-25  6:01 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='000f01bff607$57c7f770$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=wischnow@informatik.hu-berlin.de \
    --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).