zsh-workers
 help / color / mirror / code / Atom feed
From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _rpm fixes
Date: Tue, 7 Sep 1999 10:10:01 +0100	[thread overview]
Message-ID: <19990907101001.A7292@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <199909070820.KAA03650@beta.informatik.hu-berlin.de>; from Sven Wischnowsky on Tue, Sep 07, 1999 at 10:20:16AM +0200

Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote:
> 
> Adam Spiers wrote:
> 
> > ...
> >
> > I also fixed -b to complete .spec files.  It 
> > was completing installed rpms before for some reason.
> 
> I don't know `rpm' very well and the documentation I have is very
> imprecise, that's why I was asking for help when I first sent the
> `Rpm/*' functions.
> 
> Is the rest of the function ok?

I haven't played with it much yet (still discovering the joys of all
the bells and whistles with the new completion system,
e.g. description_format with group_matches, which is GREAT!) but I use
rpm a fair bit so of course I'll fix any more problems I find.  At
first glance however it looks fantastic.  Pressing tab after `rpm -b'
and getting:

> rpm -b
build stage
a -- build binary and source packages
b -- build a binary package
c -- execute build stage
i -- execute install stage
l -- do a list check
p -- execute %prep stage

blew my mind!  gcc, anyone? 8-)


  reply	other threads:[~1999-09-07  9:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-07  8:20 Sven Wischnowsky
1999-09-07  9:10 ` Adam Spiers [this message]
1999-09-07 16:48   ` Adam Spiers
  -- strict thread matches above, loose matches on Subject: below --
1999-09-08 11:27 Sven Wischnowsky
1999-09-08 11:25 Sven Wischnowsky
1999-09-06 11:50 3.1.6-pws-3 Sven Wischnowsky
1999-09-06 18:11 ` _rpm fixes Adam Spiers

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=19990907101001.A7292@thelonious.new.ox.ac.uk \
    --to=adam@thelonious.new.ox.ac.uk \
    --cc=adam@spiers.net \
    --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).