From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: complete rpm --{resign,addsign} in local
Date: Mon, 5 Jun 2000 15:03:04 +0000 [thread overview]
Message-ID: <1000605150304.ZM25499@candle.brasslantern.com> (raw)
In-Reply-To: <200006050854.KAA03756@beta.informatik.hu-berlin.de>
In-Reply-To: <393B7736.13C3C00B@u.genie.co.uk>
On Jun 5, 10:54am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: complete rpm --{resign,addsign} in local
}
} Bart Schaefer wrote:
}
} > On Jun 4, 5:09pm, Clint Adams wrote:
} > }
} > } zsh is still completing filenames directly after rpm -qcp or -qpc,
} > } with no space, FWIW.
} >
} > Currently _rpm uses `-p+' as the spec for the -p option. That means that
} > anything that will follow the -p (including package file name) is allowed
} > to appear in the same word, or in the next word.
}
} Hrm. So we have to make it complete option arguments in the next
} word(s) even if the option string doesn't end in the option, right?
In this case, that's correct. It's analogous to
tar fvxz foo.tar.gz
(The _approximate and _correct completers have a wonderful time with tar,
by the way.)
} What makes me cringe is the case where we have -xy and both options
} have arguments...
You mean like `tar fvcbz foo.tar.gz 1024 foo'?
I don't think it's incumbent upon _arguments to handle this without help;
that's exactly what the state machine is for. It just has to be possible
to tell _arguments that other option letters are allowed in the string of
options even after one that has a following argument, so that it can go
to the right next state.
This could be done by something like `_arguments -s+ ...' if it's too
awful to come up with still more OPTSPEC syntax (which I'm beginning to
believe that it is).
On Jun 5, 10:47am, Oliver Kiddle wrote:
} Subject: Re: PATCH: complete rpm --{resign,addsign} in local
}
} Bart Schaefer wrote:
}
} > Meanwhile, it ought to complete http URLs as well as ftp.
}
} Shouldn't we be calling _urls here instead of partially repeating it?
_rpm doesn't really repeat any of _urls. It makes no attempt to complete
whatever comes after the host name.
} It shouldn't be too hard to adapt _urls to pass any -g options to any
} _files so we could tell it here to complete .rpm files only. The only
} slightly messy part would be preventing it from completing gopher and
} file urls; any ideas?
If you leave a `compset -P ...' and `compadd ftp:// http://' in _rpm and
simply replace the call to _hosts with a call to _urls, that should be
enough to restrict the URL types, shouldn't it?
Oh, but it's not, because _urls doesn't handle IPREFIX properly. It'll
happily complete http://<TAB> into http://gopher:// ...
Of course the compadd in _rpm needs a `-S ""' added to it. Which reminds
me ... I tried changing that compadd to be:
_alternative ... 'prefixes:URL prefix:compadd \ ftp://'
to try to force a leading space onto the command line, but what got put
on the command line *included* the backslash. What's up with that? It
works to put a backslashed space in the pattern for '_files -g ...'.
} Peter: A build I set off on Saturday on AIX has failed with one of the
} usual dependency problems so don't make any releases until I've commited
Oops.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-06-05 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-05 8:54 Sven Wischnowsky
2000-06-04 19:37 ` Chmouel Boudjnah
2000-06-04 21:09 ` Clint Adams
2000-06-05 1:13 ` Bart Schaefer
2000-06-05 1:18 ` Bart Schaefer
2000-06-05 9:47 ` Oliver Kiddle
2000-06-05 15:03 ` Bart Schaefer [this message]
2000-06-06 9:56 Sven Wischnowsky
2000-06-07 8:01 Sven Wischnowsky
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=1000605150304.ZM25499@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).