zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.dk
Subject: Re: Moving completion functions
Date: Sun, 18 Mar 2001 02:39:31 +0000	[thread overview]
Message-ID: <1010318023932.ZM11668@candle.brasslantern.com> (raw)
In-Reply-To: <200103161020.LAA28826@beta.informatik.hu-berlin.de>

On Mar 16, 11:20am, Sven Wischnowsky wrote:
} Subject: Re: Moving completion functions
}
} - _use_lo should get a better name, yes. Hm, I don't like mixing the
}   underscore-style we use with hyphens in function names, and anyway I
}   prefer _parse_help (or _options_from__help?)

Let me jump back a bit and point out that it's not really correct to say
that _use_lo is a "utility" -- _arguments is the utility, and _use_lo
calls it; nobody would call _use_lo from some other function.

So I think _use_lo actually belongs in Unix/Command/, where the convention
is to use names that describe the command for which the function completes,
rather than names that describe what the function completes, or how.

Hence I think _use_lo should move to Unix/Command/_gnu_generic ...  I'd
say _gnu_style, except for other "style" connotations.

} > For this reason, I think a Network directory is a good idea because it
} > is quite possible to have a computer which is not connected to the
} > network so all the networking related stuff are of no use. The X
} > division is I think useful. 
} 
} If we remove the second level on installation, this should be a
} first-level directory like X, though.  And there's even stuff to fill
} a Network/Type directory.

This is OK, but ...

} > Graphic and Sound is a more complex issue
} > because you might care about programs which manipulate sound files or
} > images but not have the ability to play or display them.
} 
} Yes, similar foe Network if it's a first level directory.  There are
} network commands that need X and ones that don't.

I'd put anything that actually needs X under X first.

The biggest problem with doing so is X programs that are nothing more
than front-ends for text-based tools, when the text one is not installed.
Presumably it does little harm to have a few completion functions for X
commands that don't exist, but if there are actually dependencies among
the completion functions, errors could result if a completion for one of
those X commands happens to be attempted.

-- 
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   


  reply	other threads:[~2001-03-18  2:42 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-16 10:20 Sven Wischnowsky
2001-03-18  2:39 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-30 14:00 Sven Wischnowsky
2001-03-30 15:12 ` Bart Schaefer
2001-03-29  9:33 Sven Wischnowsky
2001-03-29 16:49 ` Bart Schaefer
2001-03-28 14:12 Sven Wischnowsky
2001-03-28 16:14 ` Bart Schaefer
2001-03-28 16:20   ` Peter Stephenson
2001-03-26 14:16 Sven Wischnowsky
2001-03-26  8:53 Sven Wischnowsky
2001-03-22 21:46 Oliver Kiddle
2001-03-22 21:50 ` Oliver Kiddle
2001-03-23  0:29 ` Bart Schaefer
2001-03-25 15:26   ` Oliver Kiddle
2001-03-25 20:39     ` Peter Stephenson
2001-03-26  4:33     ` Bart Schaefer
2001-03-22 10:40 Sven Wischnowsky
2001-03-22 11:03 ` Peter Stephenson
2001-03-22 17:04 ` Bart Schaefer
2001-03-21 11:42 Sven Wischnowsky
2001-03-20 21:32 Oliver Kiddle
2001-03-21  9:58 ` Bart Schaefer
2001-03-19  9:46 Sven Wischnowsky
2001-03-22  7:21 ` Bart Schaefer
2001-03-18 22:20 Oliver Kiddle
2001-03-19  4:36 ` Bart Schaefer
2001-03-16 17:27 Oliver Kiddle
2001-03-15 20:50 Oliver Kiddle
2001-03-16 12:09 ` Peter Stephenson
2001-03-17 23:16 ` Bart Schaefer
2001-03-15 15:46 Oliver Kiddle
2001-03-15 18:14 ` Bart Schaefer
2001-03-15 10:43 Sven Wischnowsky
2001-03-15  9:30 Sven Wischnowsky
2001-03-15 10:33 ` Peter Stephenson
2001-03-15 17:04 ` Bart Schaefer

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=1010318023932.ZM11668@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=wischnow@informatik.hu-berlin.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).