From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-users@sunsite.auc.dk
Subject: Re: Updating the Xterm title with every execution?
Date: Mon, 12 Apr 1999 10:08:12 +0200 (MET DST) [thread overview]
Message-ID: <199904120808.KAA26694@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Greg Badros's message of 01 Apr 1999 17:57:57 -0800
Greg Badros wrote:
> Though why can't
> executing a setopt load a module (as invoking a function loads that
> function)?
The problem is that the option code currently uses an array with one
entry per option, making testing for set/unset options nicely small
and fast. Enhancing that is not trivial.
Side note: once we have modules autoloadable on parameters, this might
be another argument for mocing towards a associative-array based
option system.
> Similarly, I've wanted this for completion controls, too --
> scanning all my completion stuff takes forever at startup-- it'd be nice
> to have them autoloaded when I first try to complete (ignorance warning:
> I've not been following the 3.1.x discussion on completion stuff so
> maybe people are working on this or something similar).
Well, the new completion system (more precisely: the example
implementation of the new completion system) uses autoloaded functions.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-04-12 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-12 8:08 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-04-01 7:19 Sven Wischnowsky
1999-04-02 1:57 ` Greg Badros
1999-03-31 11:35 Sven Wischnowsky
1999-03-31 23:12 ` Greg Badros
1999-03-25 20:15 Ryan Tennant
1999-03-25 21:29 ` Larry P . Schrof
1999-03-25 21:40 ` Matthew Lovell
1999-03-25 21:55 ` Greg Badros
1999-03-25 22:09 ` Larry P . Schrof
1999-03-25 22:47 ` Greg Badros
1999-03-30 4:25 ` Bart Schaefer
1999-03-30 7:56 ` Andrej Borsenkow
1999-03-30 10:27 ` Greg Badros
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=199904120808.KAA26694@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-users@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).