From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: Completion system directories
Date: Wed, 3 May 2000 10:30:25 +0000 [thread overview]
Message-ID: <1000503103025.ZM21416@candle.brasslantern.com> (raw)
In-Reply-To: <200005030914.LAA24343@beta.informatik.hu-berlin.de>
On May 3, 11:14am, Sven Wischnowsky wrote:
} Subject: Completion system directories
}
} Here is my suggestion for moving functions around.
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.
} Dunno if that should be done before 3.1.7 or after it.
I have a slight preference for "after" but only a slight one. There
are advantages either way.
} - Bart didn't like `Core', right? Any suggestions?
Right. Perhaps "Kernel"? "System"?
} - Should it be `Utilities' instead of `Utils'?
Probably. Actually I think they should all be singular e.g. "Utility".
(Cf. "Util" et al.; too bad about "Functions" and "StartupFiles" [*].)
} - There must be a better name than `Types', too...
"Flavor"? "Class"?
} - Should `Unix' be `Generic' or some such?
I think "Unix" is OK. Amol D. or the Cygwin folks may have something to
say about how generic those are, after all.
} - Somehow I like the distinction between `Zsh' and `Unix', makes even
} those function be (hopefully reasonably) grouped.
I agree.
} - For some functions I wasn't completely sure where to put them...
I know ...
} Oh, and does anyone have a list of places that need changing?
The only ones I can find with a grep are:
Completion/Core/compinit
Completion/Core/compinstall
Doc/Zsh/compsys.yo
Doc/Zsh/compsys.yo
INSTALL
configure.in
} And finally: what is the easiest way to make these changes in the CVS
} repository? Is there really no simpler way than using `cvs add' and
} `cvs remove'?
There's no way using :pserver:, but since we have shell access to the
repository ...
If we can impose a moritorium on commits for a while, we can simply copy
the ,v files to new directories in the repository, and then "cvs remove"
the originals. (We could use mv rather than cp, but that messes up the
"cvs update" of people's existing checked-out sandboxes. The only way
to make checked-out copies go away cleanly is to "cvs remove"/commit.)
} So, any comments? Suggestions? Opinions?
[*] On the subject of renaming, I've never liked "StartupFiles". It
misleads people who don't read carefully into copying those files into
/etc (I recognize parts of RedHat's distributed /etc/z* in our samples).
And those samples still refer to zsh 2.7, which never even existed!!
Those files should be touched up and the directory renamed (perhaps to
"Samples").
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-05-03 10:34 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 [this message]
2000-05-03 11:03 ` Andrej Borsenkow
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=1000503103025.ZM21416@candle.brasslantern.com \
--to=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).