zsh-workers
 help / color / mirror / code / Atom feed
From: James Devenish <j-devenish@users.sourceforge.net>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-workers@sunsite.dk
Subject: Re: Refactoring _bsd_pkg
Date: Fri, 3 Jan 2003 01:34:45 +0800	[thread overview]
Message-ID: <20030102173445.GC8904@gulag.guild.uwa.edu.au> (raw)
In-Reply-To: <3190.1041528082@finches.logica.co.uk>

In message <3190.1041528082@finches.logica.co.uk>
on Thu, Jan 02, 2003 at 06:21:22PM +0100, Oliver Kiddle wrote:
> > another look at it tomorrow. (And the person with the CC of my post is
> > the OpenBSD port maintainer for zsh, so he may have something useful to
> > add.)
> 
> Except I got a delivery failure for him so he may not see the whole
> conversation.

Re: David Lebel, I got no delivery errors and am corresponding with his
at the present minute. This is interesting, as according inference from
the mail Date headers, there are 13 hours of time difference between us.

In message <3190.1041528082@finches.logica.co.uk>
on Thu, Jan 02, 2003 at 06:21:22PM +0100, Oliver Kiddle wrote:
> I've had a cursory glance through it and it all looks fine to me. Can
> $(arch -s) be safely replaced by $MACHTYPE?

I will check with him, as he has more OpenBSD experience than I.

> When you've got it to a point you're happy with, let me know and it can
> then be committed.

Thanks, I will repost my suggestions tomorrow (with the guiding advice
you have about the paths).

> > pkg_add still doesn't work quite right because it always has some
> > directories (those matching the pattern /*) in the completion list,
> > even if my current directory is not /.
> 
> This is in _bsd_pkg_pkgfiles() right?

Mmm.

> This bit looks suspicious:
> 
>   paths=( "${(@)${(@s.:.)PKG_PATH}:#}" )
[...etc...]

I was not clear on the exact mode of operation of that portion, but I
will continue to try to arrive at a possible equivalent that makes
sense with respect to OpenBSD behaviour (may have to introduce another
case clause).

> > PS. I replaced '\'' with '', but maybe that's not portable? Also, I
> 
> That depends on the rcquotes option. You can only depend on those options
> listed in $_comp_options (of which rcquotes is not one). I tend to stick
> the whole line in double quotes to make it more readable.

Good plan. I will modify my patch to do that, then. As I only stumbled
across _bsd_pkg today, it seems to me to have a few oddities/
non-neatnesses that may be "legacy" matters (if you know what I mean).

Thanks.




      reply	other threads:[~2003-01-02 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030102140412.GG2863@gulag.guild.uwa.edu.au>
     [not found] ` <2419.1041518512@finches.logica.co.uk>
     [not found]   ` <20030102153706.GA7459@gulag.guild.uwa.edu.au>
2003-01-02 17:21     ` Oliver Kiddle
2003-01-02 17:34       ` James Devenish [this message]

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=20030102173445.GC8904@gulag.guild.uwa.edu.au \
    --to=j-devenish@users.sourceforge.net \
    --cc=okiddle@yahoo.co.uk \
    --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).