zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _a2ps completion
Date: Tue, 18 Jan 2000 20:00:24 +0000	[thread overview]
Message-ID: <E12Aekd-0006NH-00.2000-01-18-19-57-16@cmailg3.svr.pol.co.uk> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Tue, 18 Jan 2000 14:17:33 +0100." <200001181317.OAA01304@beta.informatik.hu-berlin.de>

Sven Wischnowsky wrote:
> Is this a valid reason to add a `glob-pattern' (or `file-pattern')
> style that is tested in _files and used to replace a function-supplied 
> pattern if there is any or to make _files use the pattern even if he
> calling function did not use -g? Or is this a case of `if you want
> that behaviour, copy and modify the completion function'?

I vaguely thought about this (i.e. asking you to do it :-)).  The only
reason I didn't mention it was that I vaguely thought there wouldn't be
enough context information.  But this turns out to be nonsense:

% a2ps ^Xh
tags in context :complete::a2ps::argument-rest
...

should be precise enough for anyone.

In fact, my original idea was for `glob-override', which would only modify
things if you already specified -g.  But as long as it doesn't mess up
completion of anything other than ordinary files --- i.e. it shouldn't
spoil directory completions, just alter things with the tags files,
globbed-files, or all-files --- it should be OK to use a more general
facility.

Preferably it should allow you to specify the tag you want altered,
i.e. you may want to alter just globbed-files, leaving all-files doing its
thing, or for special effects you might want all-files not to live up to
its name (e.g., I want to get rm to complete discardable files like *.o by
default (globbed-files), otherwise anything else (all-files), but I've
decide I never want it to complete vmlinuz). In which case, I suppose
`file-pattern' is the better name, since it can apply to all *files tags.
You could argue it should be `selected-files' to go with `ignored-files',
but I don't think they're really similar enough for that.

I suppose I'm going to have to include Clint's patch in 9333.

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


  reply	other threads:[~2000-01-18 19:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-18 13:17 Sven Wischnowsky
2000-01-18 20:00 ` Peter Stephenson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-01-19 16:16 Sven Wischnowsky
2000-01-18 12:06 Sven Wischnowsky
2000-01-18 11:30 Sven Wischnowsky
2000-01-18 11:46 ` Zefram
2000-01-18 11:50 ` Akim Demaille
2000-01-18 11:00 Akim Demaille
2000-01-18 11:32 ` Akim Demaille
2000-01-18 10:17 Sven Wischnowsky
2000-01-18  8:08 Sven Wischnowsky
2000-01-17 15:28 Clint Adams

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=E12Aekd-0006NH-00.2000-01-18-19-57-16@cmailg3.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).