zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
	"Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
	<zsh-workers@sunsite.auc.dk>
Subject: RE: Completion system directories
Date: Wed, 3 May 2000 15:03:32 +0400	[thread overview]
Message-ID: <000a01bfb4ef$389d9ca0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000503103025.ZM21416@candle.brasslantern.com>

>
> Structurally I think this looks fine.  I'm occassionally
> alarmed that we
> need a hierarchy this deep, but the idea is that it condenses somewhat
> upon installation, right?  E.g. it would lose the
> {Core,Zsh,...} layer.
>

Why should we remove some levels? O.K., if somebody compiles
with --disable-function-subdirs - then there is no trace of original
hierarchy anyway. But I'd like to preserve it by the installation. It
gives more clear picture; it provides for easy update; it may also
provide for system-dependent initialisation (enable only selected
subdirs relevant for my system). I think, we should preserve full
existing hierarchy by the installation. Perl has potentially much deeper
structure without any harm.

-andrej


  reply	other threads:[~2000-05-03 11:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-03  9:14 Sven Wischnowsky
2000-05-03  9:57 ` Adam Spiers
2000-05-03 10:52   ` Bart Schaefer
2000-05-03 10:30 ` Bart Schaefer
2000-05-03 11:03   ` Andrej Borsenkow [this message]
2000-05-03 11:10   ` Peter Stephenson
2000-05-03 11:24     ` Geoff Wing
2000-05-03 16:35       ` Bart Schaefer
2000-05-03 16:51         ` Peter Stephenson
2000-05-03 11:35   ` Oliver Kiddle
2000-05-03 16:23     ` CVS merge conflicts (Re: Completion system directories) 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='000a01bfb4ef$389d9ca0$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=schaefer@candle.brasslantern.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --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).