zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: Completion and global aliases
Date: Wed, 09 Jun 1999 11:01:52 +0200	[thread overview]
Message-ID: <9906090901.AA27957@ibmth.df.unipi.it> (raw)
In-Reply-To: ""Andrej Borsenkow""'s message of "Wed, 09 Jun 1999 13:17:37 DFT." <003b01beb258$eaa6aad0$21c9ca95@mow.siemens.ru>

"Andrej Borsenkow" wrote:
> As it seems, the possibilities are:
> 
>  - predefine compinit as autoloaded function if --enable-fndir is specified
>  - create a builtin that will source compinit
>  - provide COMPINIT (or eqv) parameter (read-only) to hold the full pathname
> of compinit. That is probably the least evil.

I don't see that it's that hard to tell a user `add the following to your
.zshrc', or have it in /etc/zshrc, or let them run compinstall.  Maybe the
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
than seems a good idea.

> In any case, if compinit remains sourced script, I would suggest moving it
> away from $fpath (e.g. in ${datadir}/zsh). How many users have 'autoload
> $^fpath/*(:t)' as suggested by readme? It is probably not nice having
> something else as functions in $fpath.

(Autoloading everything in $fpath could conflict with Bart's `autoload -U'
suggestion --- although I presume that first autoloading without -U, then
with, will add the NOALIASES flag.)  This complicates installation,
however, and Oliver was suggesting he'd prefer the directory structure
retained.  I haven't worked out a simple way of doing all this.

> And related - placement of dump file. Again, now, when most completion
> functions are installed in system-wide location - what is the reason to try
> put dump file in the same dir as compinit? Why not simply dump it in $HOME
> by default? I mean, that check will probably fail in 99% of all
> installations.

Yes, it may be too heavily biassed towards people developing rather than
using the system.

I don't know when I'll get a chance to look at this, I have about 50
different things to do at once, so if someone has a way of simplifying all
this so much the better.

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


  reply	other threads:[~1999-06-09  9:30 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 [this message]
1999-06-09 16:49     ` Bart Schaefer
1999-06-09 17:05       ` Andrej Borsenkow
  -- 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=9906090901.AA27957@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --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).