zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: zsh-workers@sunsite.auc.dk
Subject: some notes on 3.1.6
Date: Thu, 19 Aug 1999 09:46:46 +0100 (BST)	[thread overview]
Message-ID: <E11HNqQ-0005YQ-00@crucigera.fysh.org> (raw)

Wow.

Those are some fairly dramatic changes in 3.1.6.  I very much like
the approximate completion.  Congratulations to all concerned.

Some problems/potential changes I note in passing:

----

When an autoloaded special parameter is not actually defined by the module
loaded, there is no error message (compare "autoload failed" when it's
a builtin).  Instead, the parameter remains in an autoloadable state.
Try, for example:

	zmodload -ap example foobar
	foobar=1
	foobar=2
	foobar=3

----

When autoloading of condition codes fails, there is a similar problem.
There is an error message ("unrecognized condition"), but the condition
code remains autoloadable.

----

Now that we have autoloadable parameters, the watch system (the watch
parameter and the log builtin) can be relegated to a loadable module
like sched.

getopts can probably go the same way.

----

We ought to have autoloadable builtin widgets (for the deltochar module).
This could be implemented in user space by defining the widget as a
user-defined widget which, when run, loads the module in question and
then calls the new definition.

----

#compdef -k tagged functions, when processed by compinit, add key bindings
to the current main keymap.  Unfortunately, all the key bindings are
appropriate for emacs, and cause real trouble if the vi key bindings
are being used.

----

zftp really ought to allow more than one concurrent open session.
One could refer to sessions by name, with a mechanism to generate unique
names; commands that don't specify which session they apply to use a
default name (either actually fixed or taken from a parameter).

----

The new parameters and condition codes in the example module are not
documented.

----

After doing a "compinit" (on a shell started with zsh -f), completion
of parameter names now adds a space suffix when it shouldn't (e.g.,
during menu completion).  AUTO_PARAM_SLASH then has no effect, and suffix
removal is partly broken; for example, after completing a parameter name
in braces, a typed close brace doesn't remove anything.

----

The documentation says that the parameter module provides a parameter
called "command".  Actually it's "commands".

----

-zefram (regular access but no spare time, for the moment)


             reply	other threads:[~1999-08-19  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-19  8:46 Zefram [this message]
1999-08-24 14:02 ` Peter Stephenson
1999-08-24 14:52   ` zftp suggestion (was Re: some notes on 3.1.6) Oliver Kiddle
1999-08-19 11:23 some notes on 3.1.6 Sven Wischnowsky
1999-08-30 11:53 ` Peter Stephenson
1999-08-31  8:37 Sven Wischnowsky

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=E11HNqQ-0005YQ-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --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).