From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: compinit (was: Re: #compdef -k menu-select glitch in 3.1.9)
Date: Mon, 19 Jun 2000 18:37:06 +0000 [thread overview]
Message-ID: <1000619183706.ZM24093@candle.brasslantern.com> (raw)
In-Reply-To: <200006191036.MAA23222@beta.informatik.hu-berlin.de>
On Jun 19, 12:36pm, Sven Wischnowsky wrote:
} Subject: compinit (was: Re: #compdef -k menu-select glitch in 3.1.9)
}
} > (1) Ask whether to use the completion system.
} > (2) Silently ignore all directories and files that fail.
} > (3) Silently accept all directories and files in $fpath.
}
} How's the patch below? (Not committed until I get a positive reply.)
}
} It does the tests you mentioned and makes compinit accept three new
} options. The patterns used to find `insecure' directories and files
} are:
}
} _i_wdirs=( ${^fpath}(Nf:g+w:,f:o+w:,^u0u${EUID}) )
} _i_wfiles=( ${^~fpath:/.}/^([^_]*|*~|*.zwc)(N^u0u${EUID}) )
Argh. The one problem with this is RedHat linux's penchant for creating
groups that contain exactly one user. So it's actually safe to have a
group writable directory on RedHat as long as the name of the group is
the same as the name of the user. This has caused problems for some
other security-conscious packages as well, notably procmail.
I think you should commit the patch as is, and I'll think some more about
the right way to address this. It might have to be a configure-time thing.
} The options:
}
} -i: silently ignore `insecure' directories and files
} -u: silently use `insecure' directories and files
} -C: the same as in 11440, i.e.: make compinit not try to rebuild the
} dumpfile if it exists (small optimisation for people who don't
} fiddle with new completion functions that much)
}
} This means that `ask whether...' is the default, but that's easy to
} change, of course.
No, I think that's fine.
} The patch also contains the test to avoid using the same filename more
} than once and it removes compconf.
If the former means what I think it means, then thanks very much.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2000-06-19 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 10:36 Sven Wischnowsky
2000-06-19 18:37 ` Bart Schaefer [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=1000619183706.ZM24093@candle.brasslantern.com \
--to=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).