zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@berkom.de>
To: zsh-workers@sunsite.dk
Subject: Re: _values does not quote inserted matches
Date: Wed, 24 Apr 2002 09:37:26 +0200	[thread overview]
Message-ID: <15558.24758.24690.413672@wischnow.berkom.de> (raw)
In-Reply-To: <20020423094513.GA20267@logica.com>


Oliver Kiddle wrote:

> Andrej wrote:
> > 
> > Here is updated version. It relies on recent _values fixes. The
> > completion is correct for Mandrake 8.2. If you say O.K it will go in
> > both head and 4.0.
> 
> Are the recent _values fixes going on the 4.0 branch then? I'd say that
> was questionable without first checking through _values calls for
> quoted strings. Presumably _urpmi can be adjusted for the old _values
> fairly easily so if Andrej is happy that it works on each branch, it
> gets my okay.

Well, the C-code changes (16998) have been applied to 4.0. If that's
everything this patch relies upon, it's probably ok. No doubt Andrej
has made or will make sure.

> > I'd like to use common with _rpm cache and functions to get list of
> > installed RPMs, but _rpm is one large function and I am reluctant to
> > split it (I remember somebody was against it, but forgot reasons).
> 
> I can't think of any reason why not. It is very similar to the Debian
> situation where we have an _deb_packages used by both _dpkg and _apt.
> Maybe the reasons against splitting _rpm before was based on rpm being
> the only command to complete rpm packages.

I think we only were against splitting it up so that we have one
function file per sub-command. Factoring out the completion of RPM
names is alright, I think.

> Bart wrote:
> > Somebody other than me (Peter?  Oliver?  Sven?) should give the OK.
> 
> Well I haven't been able to test the _values calling part as it gets
> its arguments by parsing urpmi.cfg which I don't have.
> 
> Looking over the rest it looks fine. The one thing I see that I would
> do differently is to have a single tags loop in _urpmi_rpms instead
> of the three consecutive _wanted calls. It also adds source and
> binary rpms separately which means that directories get added twice.
> I think it'd be better to add them together - a user can always
> separate them with a file-patterns style.

Right. My only other comment is that the indentation style is
completely different from our normal one in the completion functions.


Bye
  Sven

-- 
Sven Wischnowsky                          wischnow@berkom.de


  reply	other threads:[~2002-04-24  7:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 20:38 Borsenkow Andrej
2002-04-13 23:26 ` Bart Schaefer
2002-04-16  6:11   ` Borsenkow Andrej
2002-04-16  7:54   ` Sven Wischnowsky
2002-04-16 10:08     ` Borsenkow Andrej
2002-04-16 16:07       ` Bart Schaefer
2002-04-17  7:26         ` PATCH: " Sven Wischnowsky
2002-04-19  8:37         ` Borsenkow Andrej
2002-04-19 16:54           ` Bart Schaefer
2002-04-23  9:45             ` Oliver Kiddle
2002-04-24  7:37               ` Sven Wischnowsky [this message]
2002-05-06  7:04               ` PATCH: _urpmi update Borsenkow Andrej

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=15558.24758.24690.413672@wischnow.berkom.de \
    --to=wischnow@berkom.de \
    --cc=zsh-workers@sunsite.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).