zsh-users
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-users@sunsite.dk
Subject: Re: compinit quirk
Date: Fri, 6 Apr 2001 10:29:50 +0200 (MET DST)	[thread overview]
Message-ID: <200104060829.KAA11875@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <1010406075047.ZM11514@candle.brasslantern.com>

Bart Schaefer wrote:

> ...
> 
> Oops, I didn't read your original message closely, only Andrej's response.
> 
> Now I'm confused, too.  This was supposedly fixed by zsh-workers/12033,
> according to the conversation in zsh-workers/12368, but apparently it
> wasn't (or at least not in the way I thought).

Quoting the docs:

  For security reasons tt(compinit) also checks if the completion system
  would use files not owned by root or by the current user, or files in
  directories that are world- or group-writable or that are not owned by 
  root or by the current user.  If such files or directories are found,
  tt(compinit) will ask if the completion system should really be used.  To
  avoid these tests and make all files found be used without asking, use the
  option tt(-u), and to make tt(compinit) silently ignore all insecure files
  and directories use the option tt(-i).  This security check is skipped
  entirely when the tt(-C) option is given.

And both of `compinit -i' and `compinit -u' work for me as described.

Bye
  Sven


-- 
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


      reply	other threads:[~2001-04-06  8:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-06  5:22 Scott Smedley
2001-04-06  5:40 ` Andrej Borsenkow
2001-04-06  6:17   ` Scott Smedley
2001-04-06  6:28     ` Bart Schaefer
2001-04-06  6:50       ` Scott Smedley
2001-04-06  7:50         ` Bart Schaefer
2001-04-06  8:29           ` Sven Wischnowsky [this message]

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=200104060829.KAA11875@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-users@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).