From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: Re: Completion and global aliases
Date: Wed, 9 Jun 1999 21:05:38 +0400 [thread overview]
Message-ID: <000e01beb29a$4bf72b70$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <990609164946.ZM32335@candle.brasslantern.com>
>
> On Jun 9, 11:01am, Peter Stephenson wrote:
> } Subject: Re: PATCH: Re: Completion and global aliases
> }
> } manual could provide a simple one-line suggestion, though, for
> anyone not
> } wanting to run compinstall --- possibly the manual could be altered to
> } contain the real location of compinit, but that will require
> more remaking
>
> I don't think remaking is a big issue, but I've always thought it
> was silly
> to have manual pages attempt to reflect local install paths.
> There's always
> somebody who shuffles things around after the fact or tries to
> share manual
> pages over NFS (or over the web!), rendering compile-time
> patching useless.
>
Yes. It is exactly for this reason I keep suggesting a *builtin* (to the
extent) way to initalize completion. I do not like the idea to rewrite rc
files every time directory layout changes for whatever reason. And if I have
single home dir, and zsh is installed in different locations on every
system - maintaining rc becomes a nightmare.
/andrej
next prev parent reply other threads:[~1999-06-09 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-09 8:53 Sven Wischnowsky
1999-06-09 9:17 ` Andrej Borsenkow
1999-06-09 9:01 ` Peter Stephenson
1999-06-09 16:49 ` Bart Schaefer
1999-06-09 17:05 ` Andrej Borsenkow [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-09 2:43 Wayne Davison
1999-06-09 6:15 ` PATCH: " Bart Schaefer
1999-06-09 7:48 ` Peter Stephenson
1999-06-09 15:40 ` 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='000e01beb29a$4bf72b70$21c9ca95@mow.siemens.ru' \
--to=borsenkow.msk@sni.de \
--cc=schaefer@candle.brasslantern.com \
--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).