From: Zefram <zefram@dcs.warwick.ac.uk>
To: fclim@singnet.com.sg (Fung-Chai Lim)
Cc: zsh-workers@math.gatech.edu
Subject: Re: Autoloading of compctl from dbm database file.
Date: Sun, 1 Dec 1996 14:17:52 +0000 (GMT) [thread overview]
Message-ID: <10492.199612011417@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <9612011323.AA00468@fclim.singnet.com.sg> from "Fung-Chai Lim" at Dec 1, 96 09:22:43 pm
>Having aliases and functions in the database can be useful. Remember my
>example, putting
> ZDBFILE=database
> zdb -auf
>at the top of any shell script is enough to access aliases and functions.
. ~/.zshenv
has much the same effect.
>The compctl command is a complicated beast; I don't understand most of
>the doc on it. The idea behind the global database is for a compctl guru
>to maintain it for the benefits of other users.
That's already possible. At this site, I maintain a file of compctl
commands which is sourced by many people's .zshrc. The only
differences between this file and a database would be the efficiency of
interpretation and ease of editing.
>I wonder if the *shell* will be corrupted when fetching data from a dbm
>file at a time when the file changes size.
Whether we use a database or not, the shell *must* cope with any binary
rubbish thrown at it. (Modules, due to them containing machine code,
are a necessary exception.)
-zefram
next prev parent reply other threads:[~1996-12-01 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-30 13:31 Fung-Chai Lim
1996-11-30 16:40 ` Zefram
1996-11-30 23:16 ` Bart Schaefer
1996-12-01 12:55 ` Fung-Chai Lim
1996-12-01 14:02 ` Zefram
1996-12-01 17:41 ` Bart Schaefer
1996-12-01 18:08 ` what should compctl's look like? Richard Coleman
1996-12-01 18:54 ` Zefram
1996-12-01 18:38 ` Autoloading of compctl from dbm database file Zefram
1996-12-02 13:23 ` Fung-Chai Lim
1996-12-01 13:22 ` Fung-Chai Lim
1996-12-01 14:17 ` Zefram [this message]
1996-12-01 15:38 ` Fung-Chai Lim
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=10492.199612011417@stone.dcs.warwick.ac.uk \
--to=zefram@dcs.warwick.ac.uk \
--cc=fclim@singnet.com.sg \
--cc=zsh-workers@math.gatech.edu \
/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).